cwielenb/CNCF-Dataset huggingface dataset:
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: v1.8.0-next.1-changelog.md

5921b5ce49: - The GitLab Project ID for the `publish:gitlab:merge-request` action is now passed through the query parameter `project` in the `repoUrl`. It still allows people to not use the `projectid` and use the `repoUrl` with the `owner` and `repo` query parameters instead. This makes it easier to publish to repositories instead of writing the full path to the project. Bumped create-app version. 62f284e394: - Adjusted the asset parser to accept case sensitive Fixed fetching data that was using the deprecated function 605f269f0d: Updated Playlist plugin docs: Updated `playlist` plugin README to include note about installing backend plugin and added images for the various features Updated `playlist-backend` plugin README to remove `IdentityClient` import in example as it is not used and made minor change to headings 605f269f0d: Updated Playlist plugin docs: Updated `playlist` plugin README to include note about installing backend plugin and added images for the various features Updated `playlist-backend` plugin README to remove `IdentityClient` import in example as it is not used and made minor change to headings Updated dependencies @backstage/plugin-scaffolder-backend@1.8.0-next.1 Updated dependencies @backstage/plugin-scaffolder-backend@1.8.0-next.1 Updated dependencies @backstage/plugin-scaffolder-backend@1.8.0-next.1 9e4d8e6198: Fix logic bug that broke techdocs-cli-embedded-app Updated dependencies @backstage/plugin-techdocs@1.4.0-next.1 Updated dependencies @backstage/plugin-techdocs@1.4.0-next.1 @backstage/plugin-playlist@0.1.2-next.1 @backstage/plugin-techdocs-module-addons-contrib@1.0.6-next.0 Updated dependencies @backstage/plugin-scaffolder-backend@1.8.0-next.1 @backstage/plugin-playlist-backend@0.2.1-next.1 @backstage/plugin-azure-devops-backend@0.3.17-next.1 example-app@0.2.77-next.1 @backstage/plugin-scaffolder-backend-module-rails@0.4.6-next.1 Updated dependencies @backstage/plugin-scaffolder-backend@1.8.0-next.1 Updated dependencies @backstage/plugin-techdocs@1.4.0-next.1
Project: YugabyteDB (App Definition and Development / Database)
File: 01-inner-join.md

title: "INNER JOIN" In this exercise we will query the employees table using an INNER JOIN with the orders table. ``` SELECT DISTINCT employees.employee_id, employees.last_name, employees.first_name, employees.title FROM employees INNER JOIN orders ON employees.employeeid = orders.employeeid; ``` The query should return 9 rows. In this exercise we will query the employees table by using an INNER JOIN with the orders table and order the results by product\id_ in a descending order. ``` SELECT DISTINCT products.product_id, products.product_name, orderdetails.unitprice FROM products INNER JOIN orderdetails ON products.productid = orderdetails.productid ORDER BY products.product_id DESC; ``` The query should return 156 rows. In this exercise we will query the products table by using an INNER JOIN with the order\details table where the product\id equals 2. ``` SELECT DISTINCT products.product_id, products.product_name, orderdetails.orderid FROM products INNER JOIN orderdetails ON products.productid = orderdetails.productid WHERE products.product_id = 2; ``` The query should return 44 rows. In this exercise we will query the orders table by using an INNER JOIN with the customers and employeestable. ``` SELECT customers.company_name, employees.first_name, orders.order_id FROM orders INNER JOIN customers ON customers.customerid = orders.customerid INNER JOIN employees ON employees.employeeid = orders.employeeid; ``` The query should return 830 rows.
Project: KICS (Provisioning / Security & Compliance)
File: a3aa0087-8228-4e7e-b202-dc9036972d02.md

title: Neptune Cluster With IAM Database Authentication Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a3aa0087-8228-4e7e-b202-dc9036972d02 Query name: Neptune Cluster With IAM Database Authentication Disabled Platform: CloudFormation Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: Neptune Cluster should have IAM Database Authentication enabled<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="12 7" AWSTemplateFormatVersion: 2010-09-09 Description: A sample template Resources: NeptuneDBCluster: Type: AWS::Neptune::DBCluster Properties: IamAuthEnabled: false StorageEncrypted: true NeptuneDBCluster2: Type: AWS::Neptune::DBCluster Properties: IamAuthEnabled: false StorageEncrypted: true ``` ```json title="Positive test num. 2 - json file" hl_lines="8 15" { "AWSTemplateFormatVersion": "2010-09-09T00:00:00Z", "Description": "A sample template", "Resources": { "NeptuneDBCluster": { "Type": "AWS::Neptune::DBCluster", "Properties": { "IamAuthEnabled": false, "StorageEncrypted": true } }, "NeptuneDBCluster2": { "Type": "AWS::Neptune::DBCluster", "Properties": { "IamAuthEnabled": false, "StorageEncrypted": true } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: 2010-09-09 Description: A sample template Resources: NeptuneDBCluster3: Type: AWS::Neptune::DBCluster Properties: IamAuthEnabled: true StorageEncrypted: true ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09T00:00:00Z", "Description": "A sample template", "Resources": { "NeptuneDBCluster3": { "Type": "AWS::Neptune::DBCluster", "Properties": { "IamAuthEnabled": true, "StorageEncrypted": true } } } } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.4.3.md

layout: release date: 2020-8-22 tag: v0.4.3 Features Use Open Service Mesh in place of osm Duration field use dropdown + text in performance preference Added tooltips for navigation menu items while in minimised state Added community calendar button Documentation Doc pages fixed Updated README.md Added first timers' and welcome guide link Added "Open Service Mesh" to navigation menu in Meshery docs Bug fixes smi-conformance - added Colons to front matter Missing bottom row added
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.10.0.md

Simplest FSM of Mutex Instructions of MQTT by @seanli33056 in https://github.com/Edgenesis/shifu/pull/408 <BugFix>fix env name by @Vacant2333 in https://github.com/Edgenesis/shifu/pull/449 <BugFix>fix the flaky test in mqtt by @hdy8200 in https://github.com/Edgenesis/shifu/pull/450 add "shifuctl install" to shifuctl by @saiyan86 in https://github.com/Edgenesis/shifu/pull/442 Rebase v0.9.0 by @hdy8200 in https://github.com/Edgenesis/shifu/pull/453 Newest readme by @rachelzhang0922 in https://github.com/Edgenesis/shifu/pull/455 add costomize port in camera by @hdy8200 in https://github.com/Edgenesis/shifu/pull/457 Bump golang.org/x/crypto from 0.4.0 to 0.5.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/446 Bump golang.org/x/net from 0.4.0 to 0.5.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/447 Bump github.com/onsi/ginkgo/v2 from 2.6.1 to 2.7.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/454 Bump github.com/taosdata/driver-go/v3 from 3.0.4 to 3.1.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/460 Bump github.com/gopcua/opcua from 0.3.8 to 0.3.9 by @dependabot in https://github.com/Edgenesis/shifu/pull/461 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.9.0...v0.10.0
Project: ClickHouse (App Definition and Development / Database)
File: VENDOR.md

As we have multiple projects we use a workspace to manage them (it's way simpler and leads to less issues). In order to vendor all the dependencies we need to store both the registry and the packages themselves. Note that this includes the exact `std` dependencies for the rustc version used in CI (currently nightly-2024-04-01), so you need to install `rustup component add rust-src` for the specific version. First step: (Re)-generate the Cargo.lock file (run under `workspace/`). ```bash cargo generate-lockfile ``` Generate the local registry: Note that we use both commands to vendor both registry and crates. No idea why both are necessary. First we need to install the tool if you don't already have it: ```bash cargo install --version 0.2.6 cargo-local-registry ``` Now add the local packages: ```bash export CHTOPDIR=$(git rev-parse --show-toplevel) export RUSTC_ROOT=$(rustc --print=sysroot) cd "$CHTOPDIR"/rust/workspace cargo local-registry --git --sync Cargo.lock "$CHTOPDIR"/contrib/rust_vendor cp "$RUSTCROOT"/lib/rustlib/src/rust/Cargo.lock "$RUSTCROOT"/lib/rustlib/src/rust/library/std/ cargo local-registry --no-delete --git --sync "$RUSTCROOT"/lib/rustlib/src/rust/library/std/Cargo.lock "$CHTOPDIR"/contrib/rustvendor cp "$RUSTCROOT"/lib/rustlib/src/rust/Cargo.lock "$RUSTCROOT"/lib/rustlib/src/rust/library/test/ cargo local-registry --no-delete --git --sync "$RUSTCROOT"/lib/rustlib/src/rust/library/test/Cargo.lock "$CHTOPDIR"/contrib/rustvendor cargo vendor --no-delete --locked "$CHTOPDIR"/contrib/rust_vendor cd "$RUSTC_ROOT"/lib/rustlib/src/rust/library/std/ cargo vendor --no-delete "$CHTOPDIR"/contrib/rust_vendor cd "$RUSTC_ROOT"/lib/rustlib/src/rust/library/test/ cargo vendor --no-delete "$CHTOPDIR"/contrib/rust_vendor rm -rf "$CHTOPDIR"/contrib/rustvendor/winapi* "$CHTOPDIR"/contrib/rustvendor/windows* rm "$RUSTCROOT"/lib/rustlib/src/rust/library/std/Cargo.lock "$RUSTCROOT"/lib/rustlib/src/rust/library/test/Cargo.lock cd "$CHTOPDIR"/rust/workspace ``` The `rustc --print=sysroot` part includes `std` dependencies, required to build with sanitizer flags. It must be kept in sync with the rustc version used in CI.
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.0.5.md

N/A Created design doc for refactor deviceShifu by @BtXin in https://github.com/Edgenesis/shifu/pull/190 Refactored the common part of each deviceShifu to a deviceShifuBase by @BtXin in https://github.com/Edgenesis/shifu/pull/191 deviceShifu TelemetryService by @tomqin93 in https://github.com/Edgenesis/shifu/pull/189 update readme by @saiyan86 in https://github.com/Edgenesis/shifu/pull/197 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.0.4...v0.0.5
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: debugging.md

```bash cluster-up/kubectl.sh version ``` will try to connect to the apiserver. To investigate the logs of a pod, you can view the logs via `cluster-up/kubectl.sh logs`. To view the logs of `virt-api`, type ```bash cluster-up/kubectl.sh logs virt-api -f ``` Sometimes a container in a pod is crashlooping because of an application error inside it. In this case, you normally can't see any logs, because the container is already gone, and so are the logs. To get the logs from the last run attempt, the `--previous` flag can be used. To view the logs of the container `virt-api` in the pod `virt-api` from the previous run, type ```bash cluster-up/kubectl.sh logs virt-api -f -c virt-api -p ``` Note that you always have to select a container inside a pod for fetching old logs with the `--previous` flag. Both, Kubernetes and KubeVirt are creating events, which can be viewed via ```bash cluster-up/kubectl.sh get events --all-namespaces --watch ``` This way it is pretty easy to detect if a Pod or a VMI got started. It can be very valuable to enter a container and do some investigations there, to see what is going wrong. In this case the kubectl `exec` command can be used. To enter `virt-api` with an interactive shell, type ```bash cluster-up/kubectl.sh exec virt-api -c virt-api -i -t -- sh ``` After all you might not see errors in the logs provided by Kubernetes. In that case you can take a look at the logs of the `kubelet` on the host where the issue is appearing. Depending on the error it is getting logged to either the system logs or to the kubelet logs, you can use the following commands to view them: ```bash journalctl journalctl -u kubelet ``` - This shows the basic principle on how remote debugging can be done. Add delve to the container Start delve on a specific port ( `dlv attach <pid> --headless --listen=0.0.0.0:1234`) Use kube-proxy to forward the port to your machine
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 07_basic_runners.md

Prompt: What is a Runner in Apache Beam? Response: Apache Beam runners are the execution engines that run the pipelines. They translate or adapt the pipeline into a form that can be executed on a massively parallel big data processing system, such as Apache Flink, Apache Spark, Google Cloud Dataflow, and more. Choosing a runner is an important step in the pipeline development process. The runner you choose determines where and how your pipeline runs. For more information about available runners and their capabilities, see the . To specify a runner, when you execute the pipeline, use the `--runner` flag. For example, to run the WordCount pipeline on Google Cloud Dataflow, you would run the following command: ```python python -m apache_beam.examples.wordcount \ --region DATAFLOW_REGION \ --input gs://dataflow-samples/shakespeare/kinglear.txt \ --output gs://STORAGE_BUCKET/results/outputs \ --runner DataflowRunner \ --project PROJECT_ID \ --templocation gs://STORAGEBUCKET/tmp/ ``` For more details about the WordCount example, see the . The executes the pipeline on your local machine. It is helpful for testing and debugging purposes. For instructions about how to configure your development environment and runner, see the quickstarts for , , and .
Project: secureCodeBox (Provisioning / Security & Compliance)
File: adr_0000.md

title: "ADR-0000: TITLE" sidebar_label: "ADR-0000" <!-- Use one of the ADR status parameter based on status Please add a cross reference link to the new ADR on 'superseded' ADR. e.g.: {adrsuposedby} <<ADR-0000>> --> | <!-- --> | <!-- --> | |-|--| | Status: | PROPOSED or ACCEPTED or REJECTED or DEPRECATED or SUPERSEDES | | Date: | YYYY-MM-DD | | Author(s): | John Doe , jane Doe | What is the issue that were seeing that is motivating this decision or change. What is the change that were actually proposing or doing. What becomes easier or more difficult to do because of this change.
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: v1.16.0.md

title: v1.16.0 weight: 998984000 Add into the `config/manager/manager.yaml` the following limits which are now scaffolded by default: ```yaml ... limits: cpu: 500m memory: 768Mi requests: cpu: 10m memory: 256Mi ``` IMPORTANT: Having resource limits is a best-practice and these values are reasonable defaults, but Operator authors should optimize these values based on their project's requirements. See for more details. Update `requirements.yml` to point to 0.3.1 of operator_sdk.util instead of 0.2.0 See for more details. Add the following annotation into the file `config/manager/manager.yaml` ```yaml ... template: metadata: annotations: kubectl.kubernetes.io/default-container: manager ... ``` See for more details. Add PHONY target to all Makefile targets. For example, refer to the `Makefile` in `operator-sdk/testdata` directory of tagged by the release containing this change. See for more details. Update the Makefile with the following changes. 1) Above `##@ Deployment` add the following: ``` ... ifndef ignore-not-found ignore-not-found = false endif ... ``` 2) Replace: ```sh kubectl delete -f - ``` With: ```sh kubectl delete --ignore-not-found=$(ignore-not-found) -f - ``` NOTE You can also compare your `Makefile` with the one tagged by this release, in `operator-sdk/testdata` of the project. See for more details.
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_connect_memcached.md

title: Kubectl-Dba Connect Memcached menu: docs_{{ .version }}: identifier: kubectl-dba-connect-memcached name: Kubectl-Dba Connect Memcached parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Connect to a telnet shell to run command against a memcached database Use this cmd to exec into a memcached object's primary pod. ``` kubectl-dba connect memcached [flags] ``` ``` -h, --help help for memcached ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "/home/runner/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --default-seccomp-profile-type string Default seccomp profile --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --password string Password for basic authentication to the API server --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use --username string Username for basic authentication to the API server ``` - Connect to a database.
Project: KICS (Provisioning / Security & Compliance)
File: 5d9e3164-9265-470c-9a10-57ae454ac0c7.md

title: CloudTrail Log Files Not Encrypted With KMS hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 5d9e3164-9265-470c-9a10-57ae454ac0c7 Query name: CloudTrail Log Files Not Encrypted With KMS Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Encryption URL: Logs delivered by CloudTrail should be encrypted using KMS to increase security of your CloudTrail<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "aws_cloudtrail" "positive1" { name = "npositive_1" s3bucketname = "bucketlog_1" } ``` ```tf title="Negative test num. 1 - tf file" resource "aws_cloudtrail" "negative1" { name = "negative1" s3bucketname = "bucketlog1" kmskeyid = "arn:aws:kms:us-east-2:123456789012:key/12345678-1234-1234-1234-123456789012" } ```
Project: StarRocks (App Definition and Development / Database)
File: EXECUTE_AS.md

displayed_sidebar: "English" After you obtain the privilege to impersonate a user (IMPERSONATE), you can use the EXECUTE AS statement to switch the execution context of the current session to the user. This command is supported from v2.4. ```SQL EXECUTE AS user WITH NO REVERT ``` `user`: The user must already exist. The current login user (who calls the EXECUTE AS statement) must be granted the privilege to impersonate another user. For more information, see . The EXECUTE AS statement must contain the WITH NO REVERT clause, which means the execution context of the current session cannot be switched back to the original login user before the current session ends. Switch the execution context of the current session to the user `test2`. ```SQL EXECUTE AS test2 WITH NO REVERT; ``` After the switch succeeds, you can run the `select current_user()` command to obtain the current user. ```SQL select current_user(); +--+ | CURRENT_USER() | +--+ | 'default_cluster:test2'@'%' | +--+ ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.10.5.md

RabbitMQ `3.10.5` is a maintenance release in the `3.10.x` release series. Please refer to the upgrade section from if upgrading from a version prior to 3.10.0. This release requires at least Erlang 23.2, and supports Erlang 24 and 25. has more details on Erlang version requirements for RabbitMQ. Release notes can be found on GitHub at . Quorum queue could run into an exception when dead lettering a message under certain conditions. GitHub issue: RabbitMQ Debian package now lists Erlang 25.0 as supported. None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.10.5.tar.xz` instead of the source tarball produced by GitHub.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.0.17-en.md

Support HAProxy protocol for HTTP API. Allow the placeholder to be anywhere in the topic for `authz` rules. e.g: `{allow, {username, "who"}, publish, ["t/foo${username}boo/${clientid}xxx"]}.` Add `start` operation to bridges API to allow manual reconnect after failure. Stop building -alpine docker image because it's size is larger than the regular one based on debian slim Expose the stats `liveconnections.count` and `liveconnections.max` to Prometheus. Disable disksup (part of os_mon) in releases by default, no warnings are issued when a disk error occurs. Improve bridge performance Fix the exclusive topics aren't removed when the session has already been cleaned. Return `400` if a broken plugin package is uploaded from HTTP API, also cleanup if plugin is not accepted. Fix MQTT bridge fails to verify TLS wildcard server certificate. Fix the issue with the bridge resource buffer where it might become stuck if enough async queries fill the inflight window full before failing with retryable errors. Fix REPORT_CB/2 CRASH error logs when errors happen during boot-up or shutdown. Report some egress MQTT bridge errors as recoverable, and thus retryable. Add back `reconnect_interval` as deprecated field for MQTT bridge. The field was removed from v5.0.16/e5.0.0 by mistake, caused new version unable to start on old config. Now it's added back as deprecated (config value is ignored if provided). Propagate errors from operations (`start|stop|restart`) on bridges API if called for all nodes. Disallow subscribing with QoS 2 for ingress MQTT bridges. Allow user to configure `clean_start` option for ingress MQTT bridges, however.