cwielenb/CNCF-Dataset huggingface dataset:
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_gcp_describe.md

Describe a GCP YugabyteDB Anywhere provider Describe a GCP provider in YugabyteDB Anywhere ``` yba provider gcp describe [flags] ``` ``` -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") -n, --name string [Optional] The name of the provider for the action. Required for create, delete, describe, update. -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 a YugabyteDB Anywhere GCP provider
Project: KICS (Provisioning / Security & Compliance)
File: 8d03993b-8384-419b-a681-d1f55149397c.md

title: EC2 Instance Using Default Security Group hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8d03993b-8384-419b-a681-d1f55149397c Query name: EC2 Instance Using Default Security Group Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: EC2 instances should not use default security group(s)<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" name: example amazon.aws.ec2: key_name: mykey instance_type: t2.micro image: ami-123456 wait: yes group: default count: 3 vpcsubnetid: subnet-29e63245 assignpublicip: yes ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="8" name: example2 amazon.aws.ec2: key_name: mykey instance_type: t2.micro image: ami-123456 wait: yes group: default count: 3 vpcsubnetid: subnet-29e63245 assignpublicip: yes ``` ```yaml title="Negative test num. 1 - yaml file" name: example2 amazon.aws.ec2: key_name: mykey instance_type: t2.micro image: ami-123456 wait: yes group: my_sg count: 3 vpcsubnetid: subnet-29e63245 assignpublicip: yes ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.10.24.md

RabbitMQ `3.10.24` is a maintenance release in the `3.10.x` . This series . Please refer to the upgrade section from if upgrading from a version prior to 3.10.0. This release requires Erlang 24.3 and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang versions older than 24.3 have reached . This release of RabbitMQ or later versions. Nodes will fail to start on older Erlang releases. Erlang 25.3 is recommended: it offers much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation. Release notes can be found on GitHub at . Classic queues v1 (CQv1) that had a backlog of messages stored by 3.9 and earlier versions could run into an exception during queue index recovery after an upgrade to 3.10.x or any later series. CQv2 and queues without a backlog were not affected. Contributed by @gomoripeti (CloudAMQP). GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.10.24.tar.xz` instead of the source tarball produced by GitHub.
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-token.md

layout: default title: mesheryctl-system-token permalink: reference/mesheryctl/system/token redirect_from: reference/mesheryctl/system/token/ type: reference display-title: "false" language: en command: system subcommand: token Manage Meshery user tokens Manipulate user tokens and their context assignments in your meshconfig <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system token [flags] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for token </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -c, --context string (optional) temporarily change the current context. -v, --verbose verbose output -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: secureCodeBox (Provisioning / Security & Compliance)
File: question.md

name: " Question" about: "If you have specific questions about the project, please post them here." labels: question <!-- Thank you for supporting our project Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. Also, please, have a look at our FAQs and existing questions before opening a new question. --> <!-- Include details about your question. -->
Project: RethinkDB (App Definition and Development / Database)
File: CONTRIBUTING.md

We're happy you want to contribute! You can help us in different ways: with suggestions for improvements Fork this repository and submit a pull request Improve the (separate repository) To submit a pull request, fork the and then clone your fork: git clone git@github.com:<your-name>/rethinkdb.git Make your suggested changes, `git push` and then [submit a pull request][4]. Note that before we can accept your pull requests, you need to sign our . The code for the admin UI is now in a separate branch, . It is used to generate the file `src/gen/web_assets.cc`, which contains the static content served by RethinkDB's admin UI. Development instructions are in that repo. Some useful resources to get started: from source Overview of in the server source directory Introduction to the for the RethinkDB server
Project: kiosk (Provisioning / Automation & Configuration)
File: CONTRIBUTING.md

Kubernetes projects require that you sign a Contributor License Agreement (CLA) before we can accept your pull requests. Please see https://git.k8s.io/community/CLA.md for more info Submit an issue describing your proposed change to the repo in question. The will respond to your issue promptly. If your proposed change is accepted, and you haven't already done so, sign a Contributor License Agreement (see details above). Fork the desired repo, develop and test your code changes. Submit a pull request. Run the command `make test` to test the changes locally. es for contribution, put them here ahead of the general k8s resources --> Kubernetes projects require that you sign a Contributor License Agreement (CLA) before we can accept your pull requests - Main contributor documentation, or you can just jump directly to the - Common resources for existing developers - We have a diverse set of mentorship programs available that are always looking for volunteers! <! Custom Information - if you're copying this template for the first time you can add custom content here, for example: - Replace `kubernetes-users` with your slack channel string, this will send users directly to your channel. -->
Project: ArangoDB (App Definition and Development / Database)
File: implicit_failure_make_exception_ptr_copy_constructor.md

+++ title = "`basicresult(const failuretype<T> &)`" description = "Implicit error-from-failure-type-sugar copy constructor. Available if `predicate::enablemakeexceptionptrcompatible_conversion<void, T, void>` is true, or `T` is `void`. Constexpr, triviality and noexcept propagating." categories = ["constructors", "implicit-constructors", "tagged-constructors"] weight = 533 +++ Implicit error-from-failure-type-sugar copy constructor used to disambiguate the construction of the error type. Note that if `T = void`, `errortype` will be default constructed. Calls {{% api "void onresultcopyconstruction(T *, U &&) noexcept" %}} with `this` and `const failure_type<T> &`. Requires: `predicate::enablemakeexceptionptrcompatible_conversion<void, T, void>` is true, or `T` is `void`. Complexity: Same as for the `errortype` constructor which accepts `T`, or the `errortype` default constructor if `T` is `void`. Constexpr, triviality and noexcept of underlying operations is propagated.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: benchsci.md

title: "BenchSci" icon: /images/logos/powered-by/benchsci.png hasLink: "https://2021.beamsummit.org/sessions/lessons-learned-dataflow-ml-batch-inference/" <!-- 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: KICS (Provisioning / Security & Compliance)
File: 19c9e2a0-fc33-4264-bba1-e3682661e8f7.md

title: Stackdriver Logging Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 19c9e2a0-fc33-4264-bba1-e3682661e8f7 Query name: Stackdriver Logging Disabled Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Kubernetes Engine Clusters must have Stackdriver Logging enabled, which means the attribute 'logging_service' must be defined and different from 'none'<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="32 3" name: create a cluster1 google.cloud.gcpcontainercluster: name: my-cluster1 initialnodecount: 2 master_auth: username: cluster_admin password: my-secret-password node_config: machine_type: n1-standard-4 disksizegb: 500 location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present name: create a cluster2 google.cloud.gcpcontainercluster: name: my-cluster2 initialnodecount: 2 master_auth: username: cluster_admin password: my-secret-password node_config: machine_type: n1-standard-4 disksizegb: 500 location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present logging_service: none ``` ```yaml title="Negative test num. 1 - yaml file" name: create a cluster google.cloud.gcpcontainercluster: name: my-cluster initialnodecount: 2 master_auth: username: cluster_admin password: my-secret-password node_config: machine_type: n1-standard-4 disksizegb: 500 location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: /tmp/auth.pem state: present logging_service: logging.googleapis.com ```
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: v1.17.0.md

id: v1.17.0 title: v1.17.0 description: Backstage Release v1.17.0 These are the release notes for the v1.17.0 release of . A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for the hard work in getting this release developed and done. For this release we had another look at the new backend system, in particular how well it fits together with the concept of plugin installation without code modification, and we identified a number of breaking changes that we wanted to make. We have removed the ability to define options for plugins and modules, and force them to be optional for services. Options have been moved either to static configuration or extension points, and modules now also have the ability to register extension points. Service factories are now considered `BackendFeature`s and are installed via `backend.add(...)` rather than via the `services` option, which has been removed. The configuration service has also been renamed to `rootConfig` in order to match other root-scoped services and make space for a potential plugin-scoped configuration service in the future. The shared environments concept has been removed. We are still interested in having some way to define reusable presets in the new system, but shared environments were too limited. We expect these to be the last broad breaking changes to the new backend system, and are likely to start encouraging use of it in the next release. The Catalog has been instrumented with some simple OpenTelemetry Spans so you can now dig into the processing loop and see it in action using tracing. Contributed by in You can now define an `each` iterable in the `steps` for a template, which will run a given action for each entry in the iterable. Contributed by in The shape of the proxy plugin configuration has been changed in order to make space for additional keys. Rather than defining the proxy endpoints directly under `proxy`, they should now be defined at `proxy.endpoints` instead. You can now use OpenAPI specs to generate typed routers for your backend plugins with request validation using `createOpenApiRouter()`. Theres been some movement to support this for some of the plugins in the monorepo like `todo`, `search` and `catalog`. Contributed by in Allows ingestion of GKE Clusters as Resources into the Catalog. Contributed by in This release does not contain any security fixes. We recommend that you keep your Backstage project up to date with this latest release. For more guidance on how to upgrade, check out the documentation for . Below you can find a list of links and references to help you learn about and start using this new release. , , and Backstage's for discussions and support Backstage , , and Sign up for our if you want to be informed about what is happening in the world of Backstage.
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: 1.6.md

We cannot wait for you to try the new features: Helm Panel redesigned so you can see at a glance how your Helm Charts are structured. Choose and order which values files will be used in your Helm Previews. Handling of restricted access to clusters. Configure the Kubernetes schema version. We added usage analytics that will help us to improve the product. Pin your favorite templates. Sealed Secrets are now supported. Use right-click to open context menus. And some more!
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: kubernetes-provisioning.md

title: Kubernetes Provisioning software: kubernetes labels: category: containers layer: orchestration inventors: goldmansachs videos: title: Kubernetes Policy Enforcement Using OPA at Goldman Sachs speakers: name: Miguel Uzcategui organization: goldmansachs name: Tim Hinrichs organization: styra venue: Kubecon San Diego 2019 link: https://www.youtube.com/watch?v=lYHr_UaHsYQ&list=PLj6h78yzYM2NDs-iu8WU5fMxINxHXlien&index=140&t=0s Kubernetes automates deployment, scaling, and management of containerized applications. OPA decides which resources need to be created on k8s in response to a namespace being created.
Project: KICS (Provisioning / Security & Compliance)
File: 970ed7a2-0aca-4425-acf1-0453c9ecbca1.md

title: Group With Privilege Escalation By Actions 'iam:AddUserToGroup' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 970ed7a2-0aca-4425-acf1-0453c9ecbca1 Query name: Group With Privilege Escalation By Actions 'iam:AddUserToGroup' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Group with privilege escalation by actions 'iam:AddUserToGroup' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamgroup" "cosmic" { name = "cosmic" } resource "awsiamgrouppolicy" "testinline_policy" { name = "testinlinepolicy" group = awsiamgroup.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:AddUserToGroup", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: inter-step-buffer.md

A `Pipeline` contains multiple vertices that ingest data from sources, process data, and forward processed data to sinks. Vertices are not connected directly, but through Inter-Step Buffers. Inter-Step Buffer can be implemented by a variety of data buffering technologies. Those technologies should support: Durability Offsets Transactions for Exactly-Once forwarding Concurrent reading Ability to explicitly acknowledge each data or offset Claim pending messages (read but not acknowledge) Ability to trim data (buffer size control) Fast (high throughput low latency) Ability to query buffer information Currently, there are 2 Inter-Step Buffer implementations:
Project: YDB (App Definition and Development / Database)
File: repo-tree.md

```text 3-nodes-mirror-3-dc / 9-nodes-mirror-3-dc / 8-nodes-block-4-2 ansible.cfg # An Ansible configuration file containing settings for connecting to servers and project structure options. It is essential for customizing Ansible's behavior and specifying default settings. ansiblevaultpassword_file # A file containing the password for decrypting encrypted data with Ansible Vault, such as sensitive variables or configuration details. This is crucial for securely managing secrets like the root user password. creds # A directory for environment variables that specify the username and password for YDB, facilitating secure access to the database. files config.yaml # A YDB configuration file, which contains settings for the database instances. inventory # A directory containing inventory files, which list and organize the servers Ansible will manage. 50-inventory.yaml # The main inventory file, specifying the hosts and groups for Ansible tasks. 99-inventory-vault.yaml # An encrypted inventory file storing sensitive information, such as the root user's password for YDB, using Ansible Vault. setup_playbook.yaml # A playbook file that initiates the installation and configuration roles for setting up YDB on the cluster. README.md # A markdown file providing a description of the repository, including how to use it, prerequisites, and any other relevant information. requirements.txt # A file listing Python package dependencies required for the virtual environment, ensuring all necessary tools and libraries are installed. requirements.yaml # Specifies the Ansible collections needed, pointing to the latest versions or specific versions required for the project. TLS #A directory intended for storing TLS (Transport Layer Security) certificates and keys for secure communication. ydb-ca-nodes.txt # Contains a list of Fully Qualified Domain Names (FQDNs) of the servers for which TLS certificates will be generated, ensuring secure connections to each node. ydb-ca-update.sh # A script for generating TLS certificates from the ydb-ca-nodes.txt list, automating the process of securing communication within the cluster. ```
Project: KICS (Provisioning / Security & Compliance)
File: d58c6f24-3763-4269-9f5b-86b2569a003b.md

title: Google Container Node Pool Auto Repair Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d58c6f24-3763-4269-9f5b-86b2569a003b Query name: Google Container Node Pool Auto Repair Disabled Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Google Container Node Pool Auto Repair should be enabled. This service periodically checks for failing nodes and repairs them to ensure a smooth running state.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="26 29 13" name: create a node pool google.cloud.gcpcontainernode_pool: name: my-pool initialnodecount: 4 cluster: "{{ cluster }}" location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present management: auto_repair: no name: create a node pool2 google.cloud.gcpcontainernode_pool: name: my-pool initialnodecount: 4 cluster: "{{ cluster }}" location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present management: auto_repair: false name: create a node pool3 google.cloud.gcpcontainernode_pool: name: my-pool initialnodecount: 4 cluster: "{{ cluster }}" location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: create a node pool google.cloud.gcpcontainernode_pool: name: my-pool initialnodecount: 4 cluster: '{{ cluster }}' location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: /tmp/auth.pem state: present management: auto_repair: yes name: create a node pool google.cloud.gcpcontainernode_pool: name: my-pool initialnodecount: 4 cluster: '{{ cluster }}' location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: /tmp/auth.pem state: present management: auto_repair: true ```