cwielenb/CNCF-Dataset huggingface dataset:
Project: Gradle Build Tool (App Definition and Development / Application Definition & Image Build)
File: 0001-use-architectural-decision-records.md

2023-12-01 In a distributed team with many subteams, the best solution to communicate decisions is to use a format accessible by everyone in charge of development. We use Specification and Discovery documents stored in Google Drive, but they present some downsides: They are rarely updated after creation and initial review, and then become hard to follow, especially after important decisions are made They are not synced with the code to reflect the eventual solution that is committed Google Docs is not a "code-oriented" tool, like asciidoc can be Review in Google Docs is not as simple as a PR code review in GitHub The Build Tool Team has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow. The main logic with ADRs is to describe (architectural) decisions made: To provide best practices and solutions we (as the build tool* team) want to promote. To avoid asking the same thing multiple times during code review. To explain rejected solutions*, for now, and future development, in case they are proposed again. ADRs can be written by any team. Like code, they should be reviewed by any other relevant teams. The goal is not to own a decision, but to share it with other teams, and improve the build tool together. The format for ADR should follow this template: ```markdown 20YY-MM-DD Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. [PROPOSED, ACCEPTED, REJECTED, DEPRECATED, REPLACED] X Y Z ``` ACCEPTED We start to use Architectural Decision Records We use the proposed template from this ADR We locate `.md` files in the folder `/architecture-standards` We highly encourage usage of ADR to communicate decisions We use links to ADRs in Specifications, Discoveries and Pull-Requests* to simplify communication
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 15_advanced_xlang.md

Prompt: What is a multi-language pipeline in Apache Beam? Response: Apache Beam lets you combine transforms written in any supported SDK language (currently, and ) and use them in one multi-language pipeline. For example, a multi-language pipeline might read from a Python source, process the data using a Java transform, and write the data to a Python sink. For example, you can use the and from the Java SDK in Python pipelines. To learn how to create a multi-language pipeline, see the quickstart examples for and . Depending on the SDK language of the pipeline, you can use a high-level SDK wrapper class or a low-level transform class to access a cross-language transform. For more information, see . To develop a cross-language transform, you need to define a Uniform Resource Name(URN) for registering the transform with an expansion service. For more information, see .
Project: external-secrets (Provisioning / Security & Compliance)
File: eso-demos.md

A list of demos given by people going through simple setups with ESO. Feel free to let us know if you have a demo that you want to include here! Viktor Farvik shows us how to use ESO with GCP provider and explores a simple workflow with the project. ](https://www.youtube.com/watch?v=SyRZe5YVCVk) Kim Schlesinger and Daniel Hix show us how to install and use both projects, comparing their features and limitations in different situations. ](https://www.youtube.com/watch?v=EW25WpErCmA) This was an old demo going through an old version of ESO. Most of it is still valid, but beware of CRD and breaking change differences. ](https://www.youtube.com/watch?v=L6tn1YdMkF8) Balkrishna Pandey shows us here how to use ClusterSecretStore and how to integrate ESO with Hashicorp Vault on Openshift. ](https://www.youtube.com/watch?v=N7njTq6TSx8) Lukonde Mwila demonstrates how ESO works and how to fetch secrets from AWS Secrets Manager into your Kubernetes cluster. ](https://www.youtube.com/watch?v=FD8zzHPbhoY) Charl Klein gives an overview of the external secrets project, and a walkthrough of getting ESO up and running with Azure Key Vault ](https://www.youtube.com/watch?v=phohsHfl55A)
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_create_extension.md

title: CREATE EXTENSION statement [YSQL] headerTitle: CREATE EXTENSION linkTitle: CREATE EXTENSION summary: Load an extension into a database description: Use the CREATE EXTENSION statement to load an extension into a database. menu: v2.18: identifier: ddlcreateextension parent: statements type: docs Use the `CREATE EXTENSION` statement to load an extension into a database. {{%ebnf%}} create_extension {{%/ebnf%}} `SCHEMA`, `VERSION`, and `CASCADE` may be reordered. ```plpgsql CREATE SCHEMA myschema; CREATE EXTENSION pgcrypto WITH SCHEMA myschema VERSION '1.3'; ``` ```output CREATE EXTENSION ``` ```plpgsql CREATE EXTENSION IF NOT EXISTS earthdistance CASCADE; ``` ```output NOTICE: installing required extension "cube" CREATE EXTENSION ```
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.16.4.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | distcp fail copying to /user/\<username\>/\<newtarget\> (with permission on) | Blocker | . | Koji Noguchi | Raghu Angadi | | | Incorrect permission checking on mv | Blocker | . | Koji Noguchi | Tsz Wo Nicholas Sze | | | distcp leaves empty blocks afte successful execution | Blocker | util | Christian Kunz | Tsz Wo Nicholas Sze | | | [HOD] logcondense fails if DFS has files that are not log files, but match a certain pattern | Blocker | contrib/hod | Hemanth Yamijala | Hemanth Yamijala |
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_users.md

+++ title = "google_users resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "google_users" identifier = "inspec/resources/gcp/googleusers.md googleusers resource" parent = "inspec/resources/gcp" +++ Use the `google_users` InSpec audit resource to test properties of all, or a filtered group of, GCP users. A `googleusers` resource block collects GCP users for the specified customer. As documented , this defaults to the `mycustomer` alias to represent your account's `customerId`. describe googleusers(customer: 'mycustomer') do it { should exist } end The `domain` argument can optionally be provided to get fields from only one domain. Either the customer or the domain parameter must be provided. describe googleusers(domain: 'mydomain.com') do it { should exist } end Use this InSpec resource to enumerate IDs then test in-depth using `google_user`. googleusers(customer: 'mycustomer').userids.each do |userid| describe googleuser(userkey: user_id) do it { should exist } it { shouldnot besuspended } end end The following examples show how to use this InSpec audit resource. describe googleusers(customer: 'mycustomer') do its('count') { should be <= 100} end describe googleusers(customer: 'mycustomer') do its('user_names') { should include "Monsieur Happy" } end googleusers(customer: 'mycustomer').where(userfullname: /Batman/).userids.each do |userid| describe googleuser(userkey: user_id) do it { should exist } end end This resource supports the following filter criteria: `userid`; `userfullname` and `useremail`. Any of these may be used with `where`, as a block or as a method. `userids` - an array of googleuser identifier integers `userfullnames` - an array of google_user full name strings `useremails`- an array of googleuser primary email address strings Ensure the G Suite Admin SDK is enabled and you have sufficient privileges to list users.
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.6.1.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | libhdfs returns success even when writing to a file fails | Major | . | Christian Kunz | Arun C Murthy | | | TextInputformat .isSplittable() fails with NullPointerException with hadoop 0.6.1 | Major | . | Sanjay Dahiya | Owen O'Malley | | | classloader problem for clients | Major | io | Christian Kunz | Owen O'Malley | | | datanode lock message causes NullPointerException | Major | . | Owen O'Malley | Milind Bhandarkar | | | SequenceFile fails task with NullPointerException in codec initialization | Blocker | . | Sanjay Dahiya | Owen O'Malley |
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.72.md

layout: release date: 2023-04-04 tag: v0.6.72 [Dependency] Upgrade MeshKit v0.6.37 @leecalcote (#7474) update endpoint @MUzairS15 (#7473) Modify prettification logic for end-user fields @Revolyssup (#7463) Updated `mesheryctl` version output @acald-creator (#7467) Redirect to Extension page when user is already signed up @Abhishek-kumar09 (#7475) Bump react-share from 4.4.0 to 4.4.1 in /ui @dependabot (#7448) [Add] Security and Compliance Icon @ritiksaxena124 (#7462) Bump github.com/opencontainers/runc from 1.1.4 to 1.1.5 @dependabot (#7415) Bump react-share from 4.4.0 to 4.4.1 in /ui @dependabot (#7448) Bump github.com/layer5io/meshkit from 0.6.33 to 0.6.35 @dependabot (#7450) removed jumbled information from summary @vishalvivekm (#7470) [Docs] Improve REST API Docs Legibility @senali-d (#7368) Fix if condition example @goldfishdolphin (#7457) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @MUzairS15, @Revolyssup, @acald-creator, @adithyaakrishna, @dependabot, @goldfishdolphin, @leecalcote, @ritiksaxena124, @senali-d, @vishalvivekm, MUzairS15 and l5io
Project: YugabyteDB (App Definition and Development / Database)
File: jsonb-strip-nulls.md

title: jsonbstripnulls() and jsonstripnulls() headerTitle: jsonbstripnulls and jsonstripnulls linkTitle: jsonbstripnulls() description: Find all key-value pairs in the hierarchy of the supplied JSON compound value and return a JSON value where each null pair has been removed. menu: v2.18: identifier: jsonb-strip-nulls parent: json-functions-operators weight: 220 type: docs Purpose: Find all key-value pairs at any depth in the hierarchy of the supplied JSON compound value (such a pair can occur only as an element of an object), and return a JSON value where each pair whose value is the JSON null has been removed. Signature For the `jsonb` variant: ``` input value: jsonb return value: jsonb ``` Notes: By definition, these functions leave null values within arrays untouched. ```plpgsql do $body$ declare j constant jsonb := '{ "a": 17, "b": null, "c": {"x": null, "y": "dog"}, "d": [42, null, "cat"] }'; strippedj constant jsonb := jsonbstrip_nulls(j); expectedstrippedj constant jsonb := '{ "a": 17, "c": {"y": "dog"}, "d": [42, null, "cat"] }'; begin assert strippedj = expectedstripped_j, 'unexpected'; end; $body$; ```
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.9.2.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | task cleanup messages can get lost, causing task trackers to keep tasks forever | Major | . | Owen O'Malley | Arun C Murthy | | | turn off speculative execution by default | Major | . | Owen O'Malley | Owen O'Malley | | | deadlock issue in taskstracker. | Major | . | Mahadev konar | Mahadev konar |
Project: Beam (App Definition and Development / Streaming & Messaging)
File: oracle.md

title: "Oracle" icon: /images/logos/powered-by/oracle.png hasLink: "https://www.progress.com/tutorials/cloud-and-hybrid/etl-on-premises-oracle-data-to-google-bigquery-using-google-cloud-dataflow" <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_describe.md

Describe a YugabyteDB Anywhere provider Describe a provider in YugabyteDB Anywhere ``` yba provider describe [flags] ``` ``` -n, --name string [Required] The name of the provider to get details. -c, --code string [Optional] Code of the provider. Allowed values: aws, gcp, azu, onprem, kubernetes. -h, --help help for describe ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage YugabyteDB Anywhere providers
Project: ClickHouse (App Definition and Development / Database)
File: v21.1.2.15-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Explicitly set uid / gid of clickhouse user & group to the fixed values (101) in clickhouse-server images. (). Backported in : `SELECT count() FROM table` now can be executed if only one any column can be selected from the `table`. This PR fixes . (). Backported in : Fix index analysis of binary functions with constant argument which leads to wrong query results. This fixes . (). Backported in : Fixed `Attempt to read after eof` error when trying to `CAST` `NULL` from `Nullable(String)` to `Nullable(Decimal(P, S))`. Now function `CAST` returns `NULL` when it cannot parse decimal from nullable string. Fixes . (). Backported in : Fix issue with `bitmapOrCardinality` that may lead to nullptr dereference. This closes . (). Backported in : Attach partition should reset the mutation. . (). Backported in : Fix bug when mutation with some escaped text (like `ALTER ... UPDATE e = CAST('foo', 'Enum8(\'foo\' = 1')` serialized incorrectly. Fixes . (). Backported in : Fix error `Task was not found in task queue` (possible only for remote queries, with `asyncsocketfor_remote = 1`). (). Backported in : Fix incorrect behavior when `ALTER TABLE ... DROP PART 'part_name'` query removes all deduplication blocks for the whole partition. Fixes . (). Backported in : Fixed very rare deadlock at shutdown. (). Backported in : Fix possible exception `QueryPipeline stream: different number of columns` caused by merging of query plan's `Expression` steps. Fixes . (). Backported in : Disable `optimizemovefunctionsoutof_any` because optimization is not always correct. This closes . This closes . (). Backported in : Join tries to materialize const columns, but our code waits for them in other places. (). Backported in : Fix inserting of `LowCardinality` column to table with `TinyLog` engine. Fixes . (). Backported in : Fix possible error `Expected single dictionary argument for function` if use function `ignore` with `LowCardinality` argument. Fixes . (). Backported in : Make sure `groupUniqArray` returns correct type for argument of Enum type. This closes . (). Backported in : Restrict `MODIFY TTL` queries for `MergeTree` tables created in old syntax. Previously the query succeeded, but actually it had no effect. (). Backported in : Simplify the implementation of `tupleHammingDistance`. Support for tuples of any equal length. Fixes . (). Backported in : Fix startup bug when clickhouse was not able to read compression codec from `LowCardinality(Nullable(...))` and throws exception `Attempt to read after EOF`. Fixes . (). Backported in : Fix bug in merge tree data writer which can lead to marks with bigger size than fixed granularity size. Fixes . (). Backported in : Fix infinite reading from file in `ORC` format (was introduced in ). Fixes . (). Backported in : - Split RemoteQueryExecutorReadContext into module part - Fix leaking of pipe fd for `asyncsocketfor_remote`. ().
Project: Pulsar (App Definition and Development / Streaming & Messaging)
File: pip-301.md

The following z-nodes store the load and quota data about loadbalance. And the CRUD about them are handled by `localMetadataStore`, not `configurationMetadataStore`. `/loadbalance/bundle-data` `/loadbalance/broker-time-average` `/loadbalance/resource-quota` Currently, the access about the above z-nodes are distributed everywhere. It's very easy to call the the wrong `configurationMetadataStore` to handle them, e.g.: Refactor the access code about balance/load data Introduce `LoadBalanceResources` to unify the CRUD about balance/load data. None Introduce `LoadBalanceResources` which has three inner class: `BundleDataResources` `BrokerTimeAverageResources` `QuotaResources` ```java public class LoadBalanceResources { public static final String BUNDLEDATABASE_PATH = "/loadbalance/bundle-data"; public static final String BROKERTIMEAVERAGEBASEPATH = "/loadbalance/broker-time-average"; public static final String RESOURCEQUOTABASE_PATH = "/loadbalance/resource-quota"; private final BundleDataResources bundleDataResources; public LoadBalanceResources(MetadataStore store, int operationTimeoutSec) { bundleDataResources = new BundleDataResources(store, operationTimeoutSec); } public static class BundleDataResources extends BaseResources<BundleData> { public BundleDataResources(MetadataStore store, int operationTimeoutSec) { super(store, BundleData.class, operationTimeoutSec); } // ... } public static class BrokerTimeAverageResources extends BaseResources<TimeAverageBrokerData> { public BrokerTimeAverageResources(MetadataStore store, int operationTimeoutSec) { super(store, TimeAverageBrokerData.class, operationTimeoutSec); } // ... } public static class QuotaResources extends BaseResources<ResourceQuota> { public QuotaResources(MetadataStore store, int operationTimeoutSec) { super(store, ResourceQuota.class, operationTimeoutSec); } // ... } } ``` None None None Mailing List discussion thread: https://lists.apache.org/thread/7ngw9dc62tj2c4c5484dgsnlwgtstpbj Mailing List voting thread: https://lists.apache.org/thread/26dc8r6hnp7owdsq1hpzb48g8vlfrtxt
Project: KICS (Provisioning / Security & Compliance)
File: 4b82202a-b18e-4891-a1eb-a0989850bbb3.md

title: BOM - GCP PST hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 4b82202a-b18e-4891-a1eb-a0989850bbb3 Query name: BOM - GCP PST Platform: Terraform Severity: <span style="color:#CCCCCC">Trace</span> Category: Bill Of Materials URL: A list of Pub/Sub Topic resources found. Cloud Pub/Sub is designed to provide reliable, many-to-many, asynchronous messaging between applications. Publisher applications can send messages to a 'topic' and other applications can subscribe to that topic to receive the messages.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="34 44 54 39" resource "googlepubsubtopiciambinding" "binding" { project = googlepubsubtopic.example.project topic = googlepubsubtopic.example1.name role = "roles/viewer" members = [ "user:jane@example.com", ] } resource "googlepubsubtopiciammember" "member" { project = googlepubsubtopic.example.project topic = googlepubsubtopic.example2.name role = "roles/viewer" member = "user:jane@example.com" } resource "googlepubsubtopiciambinding" "binding_public" { project = googlepubsubtopic.example.project topic = googlepubsubtopic.example3.name role = "roles/pubsub.publisher" members = [ "allUsers", "allAuthenticatedUsers" ] } resource "googlepubsubtopiciammember" "member_public" { project = googlepubsubtopic.example.project topic = googlepubsubtopic.example4.name role = "roles/pubsub.publisher" member = "allUsers" } resource "googlepubsubtopic" "example1" { name = "example-topic" kmskeyname = googlekmscryptokey.cryptokey.id } resource "googlepubsubtopic" "example2" { name = "example-topic" kmskeyname = googlekmscryptokey.cryptokey.id } resource "googlepubsubtopic" "example3" { name = "example-topic" labels = { foo = "bar" } messageretentionduration = "86600s" } resource "googlepubsubtopic" "example4" { name = "example-topic" labels = { foo = "bar" } messageretentionduration = "86600s" } ``` ```tf title="Negative test num. 1 - tf file" resource "googlebigquerydataset" "negative1" { datasetid = "exampledataset" friendly_name = "test" description = "This is a test description" location = "EU" defaulttableexpiration_ms = 3600000 labels = { env = "default" } access { role = "OWNER" userbyemail = googleserviceaccount.bqowner.email } access { role = "READER" domain = "hashicorp.com" } } ```
Project: KICS (Provisioning / Security & Compliance)
File: 9356962e-4a4f-4d06-ac59-dc8008775eaa.md

title: Not Proper Email Account In Use hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9356962e-4a4f-4d06-ac59-dc8008775eaa Query name: Not Proper Email Account In Use Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: Gmail accounts are being used instead of corporate credentials<br> ```tf title="Positive test num. 1 - tf file" hl_lines="6" resource "googleprojectiam_binding" "positive1" { project = "your-project-id" role = "roles/editor" members = [ "user:jane@gmail.com", ] } ``` ```tf title="Negative test num. 1 - tf file" resource "googleprojectiam_binding" "negative1" { project = "your-project-id" role = "roles/editor" members = [ "user:jane@example.com", ] } ```
Project: YugabyteDB (App Definition and Development / Database)
File: alter_user,alter_role_option,role_specification,alter_user_rename,alter_user_config,config_setting.grammar.md

```output.ebnf alteruser ::= ALTER USER rolespecification [ [ WITH ] alterroleoption [ , ... ] ] alterroleoption ::= SUPERUSER | NOSUPERUSER | CREATEDB | NOCREATEDB | CREATEROLE | NOCREATEROLE | INHERIT | NOINHERIT | LOGIN | NOLOGIN | CONNECTION LIMIT connlimit | [ ENCRYPTED ] PASSWORD ' password ' | PASSWORD NULL | VALID UNTIL ' timestamp ' rolespecification ::= rolename | CURRENTUSER | SESSIONUSER alteruserrename ::= ALTER USER rolename RENAME TO newrole_name alteruserconfig ::= ALTER USER { role_specification | ALL } [ IN DATABASE databasename ] configsetting configsetting ::= SET configparam { TO | = } { config_value | DEFAULT } | SET config_param FROM CURRENT | RESET config_param | RESET ALL ```