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

To create infrastructure in Yandex Cloud using Terraform, you need: Prepare the cloud for work: in Yandex Cloud. payment account. that there are enough funds to create nine VMs. Install and configure Yandex Cloud CLI: Yandex Cloud CLI. profile service account using the CLI. SA key in JSON format for connecting Terraform to the cloud using the CLI: `yc iam key create --service-account-name <acc name> --output <file name> --folder-id <cloud folder id>`. An SA key will be generated, and secret information will be output to the terminal: ``` access_key: id: ajenhnhaqgd3vp... serviceaccountid: aje90em65r6922... created_at: "2024-03-05T20:10:50.0150..." key_id: YCAJElaLsa0z3snzH4E... secret: YCPKNJDVhRZgyywl4hQwVdcSRC... ``` Copy `access_key.id` and `secret`. The values of these fields will be needed later when working with AWS CLI. AWS CLI. Set up the AWS CLI environment: Run the `aws configure` command and sequentially enter the previously saved `access_key.id` and `secret`. For the region value, use `ru-central1`: ``` aws configure AWS Access Key ID [None]: AKIAIOSFODNN AWS Secret Access Key [None]: wJalr/*/bPxRfiCYEX Default region name [None]: ru-central1 Default output format [None]: ``` The files `~/.aws/credentials` and `~/.aws/config` will be created. Edit `~/.aws/credentials` and `~/.aws/config` as follows: Add `[Yadefreg]` to `~/.aws/config` before `region = ru-central1-a`. Add `[Yandex]` before the secret information about connection keys. Yandex Cloud Terraform provider. Download this repository with the command `git clone https://github.com/ydb-platform/ydb-terraform.git`. Go to the `yandex_cloud` directory in the downloaded repository and make changes to the following variables in the `variables.tf` file: `key_path` path to the SA key generated using the CLI. `cloud_id` cloud ID. You can get a list of available clouds with the command `yc resource-manager cloud list`. `profile` profile name from the file `~/.aws/config`. `folder_id` Cloud folder ID. Can be obtained with the command `yc resource-manager folder list`. Now, being in the `yandex_cloud` subdirectory, you can run the following sequence of commands to install the provider, initialize modules, and create the infrastructure: `terraform init` installing the provider and initializing modules. `terraform plan` creating a plan for future infrastructure. `terraform init` create resources in the cloud. Next, use the commands `terraform plan`, `terraform init`, and `terraform destroy` (destruction of the created infrastructure) to apply further changes as necessary.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: yelp.md

title: "Yelp" icon: /images/logos/powered-by/yelp.png hasLink: "https://www.youtube.com/watch?v=EnUOqVxsJjY" <!-- 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: secureCodeBox (Provisioning / Security & Compliance)
File: 03_system_scope_and_context.md

title: "System Scope and Context" sidebar_label: "System Scope and Context" sidebar_position: 3 secureCodeBox is an orchestration platform managing scans with various security tools and processing the results. The aim of this project is to make automated vulnerability scanning easy and efficient. The diagrams below illustrate the external factors and the context in which secureCodeBox is used. secureCodeBox only manages the scan execution. The scanning functionality itself is considered out of scope and relies on third-party security scanners. The following diagram shows thesecureCodeBox as blackbox system and all other systems and actors depending on secureCodeBox or secureCodeBox depends on. The arrows in the diagram indicate the direction of the dependency: The system which "points with the arrow" to another system means that it depends on that other system and can't fully operate without this system. The following table describes the systems secureCodeBox interacts with. The description is deliberately brief. The details of the used APIs are documented in the . | System | Description | |:--|:--| | secureCodeBox | This is the main system we discuss in this documentation. | | Container Runtime | secureCodeBox depends on a container runtime (e.g. , etc.) to build the container images. | | DockerHub | secureCodeBox depends on the public services from to push/pull container images. | | Kubernetes | is the main foundation of the secureCodeBox. We heavily rely on the API and Custom Resources. | | Helm | secureCodeBox uses to build, publish and install the containers via charts in . | | S3 | secureCodeBox depends on an compliant backend to store its persistent data. | | 3rd Party Tool | (optional) secureCodeBox can import findings into other tools. | | Scanner Tools | secureCodeBox depends on tools. | | CI/CD | Continuous Integration (CI) and Continuous Deployment (CD) systems which may initialize a scan. | The following table describes the roles interacting with secureCodeBox. | Role | Description | |:-|:-| | Operator | The role which operates the secureCodeBox installation. (Do not confuse with Kubernetes operator pattern, which we implement for the engine.) | | Tester | The role which utilizes secureCodeBox to perform security tests. | | Developer | The role which develops the secureCodeBox. |
Project: KICS (Provisioning / Security & Compliance)
File: 28545147-2fc6-42d5-a1f9-cf226658e591.md

title: SNS Topic Not Encrypted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 28545147-2fc6-42d5-a1f9-cf226658e591 Query name: SNS Topic Not Encrypted Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: SNS (Simple Notification Service) Topic should be encrypted<br> ```tf title="Positive test num. 1 - tf file" hl_lines="3" resource "awssnstopic" "user_updates" { name = "user-updates-topic" kmsmasterkey_id = "" } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="5" provider "aws" { region = "us-east-1" } resource "awssnstopic" "test" { name = "snsnotecnrypted" } ``` ```tf title="Negative test num. 1 - tf file" provider "aws2" { region = "us-east-1" } resource "awssnstopic" "test2" { name = "sns_ecnrypted" kmsmasterkey_id = "alias/MyAlias" } ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_upgrade.md

title: kbcli cluster upgrade Upgrade the cluster version. ``` kbcli cluster upgrade NAME [flags] ``` ``` kbcli cluster upgrade mycluster --cluster-version=ac-mysql-8.0.30 ``` ``` --auto-approve Skip interactive approval before upgrading the cluster --cluster-version string Reference cluster version (required) --dry-run string[="unchanged"] Must be "client", or "server". If with client strategy, only print the object that would be sent, and no data is actually sent. If with server strategy, submit the server-side request, but no data is persistent. (default "none") -h, --help help for upgrade --name string OpsRequest name. if not specified, it will be randomly generated -o, --output format Prints the output in the specified format. Allowed values: JSON and YAML (default yaml) --ttlSecondsAfterSucceed int Time to live after the OpsRequest succeed ``` ``` --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/.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 --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 --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 ``` - Cluster command.
Project: Koperator (App Definition and Development / Streaming & Messaging)
File: FEATURE_REQUEST.md

name: Feature Request about: Suggest a feature for this project title: '' labels: '' assignees: '' Please describe the problem to be addressed by the proposed feature. Please describe what you envision the solution to this problem would look like. Please briefly describe which alternatives, if any, have been considered, including merits of alternate approaches and tradeoffs being made. Please provide any other information that may be relevant.
Project: KICS (Provisioning / Security & Compliance)
File: e4610872-0b1c-4fb7-ab57-d81c0afdb291.md

title: Nifcloud Computing Undefined Description To Security Group Rule hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e4610872-0b1c-4fb7-ab57-d81c0afdb291 Query name: Nifcloud Computing Undefined Description To Security Group Rule Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: Missing description for security group rule<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "nifcloudsecuritygroup_rule" "positive" { securitygroupnames = ["http"] type = "IN" from_port = 80 to_port = 80 protocol = "TCP" cidrip = nifcloudprivatelan.main.cidrblock } ``` ```tf title="Negative test num. 1 - tf file" resource "nifcloudsecuritygroup_rule" "negative" { securitygroupnames = ["http"] type = "IN" description = "HTTP from VPC" from_port = 80 to_port = 80 protocol = "TCP" cidrip = nifcloudprivatelan.main.cidrblock } ```
Project: ArangoDB (App Definition and Development / Database)
File: assume_exception_rvalue.md

+++ title = "`exceptiontype &&assumeexception() && noexcept`" description = "Narrow contract rvalue reference observer of the stored exception. Constexpr propagating, never throws." categories = ["observers"] weight = 782 +++ Narrow contract rvalue reference observer of the stored exception. `NoValuePolicy::narrowexceptioncheck()` is first invoked, then the reference to the exception is returned. As a valid default constructed exception is always present, no undefined behaviour occurs unless `NoValuePolicy::narrowexceptioncheck()` does that. Note that if `exception_type` is `void`, only a `const` overload returning `void` is present. Requires: Always available. Complexity: Depends on `NoValuePolicy::narrowexceptioncheck()`. Guarantees: An exception is never thrown.
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: opa-wasm-rust.md

title: OPA Wasm Rust Crate software: rust inventors: matrix labels: category: wasm type: poweredbyopa tutorials: https://github.com/matrix-org/rust-opa-wasm#try-it-out https://docs.rs/opa/latest/opa/wasm/index.html code: https://github.com/matrix-org/rust-opa-wasm docs_features: wasm-integration: note: 'This project implements the OPA Wasm module interface in Rust. ' A crate to use OPA policies compiled to WASM.
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_azure.md

Manage a YugabyteDB Anywhere Azure provider Manage an Azure provider in YugabyteDB Anywhere ``` yba provider azure [flags] ``` ``` -n, --name string [Optional] The name of the provider for the action. Required for create, delete, describe, update. -h, --help help for azure ``` ``` -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 - Create an Azure YugabyteDB Anywhere provider - Delete an Azure YugabyteDB Anywhere provider - Describe an Azure YugabyteDB Anywhere provider - List Azure YugabyteDB Anywhere providers - Update an Azure YugabyteDB Anywhere provider
Project: ShardingSphere (App Definition and Development / Database)
File: 2pc-xa-transaction.en.md

+++ title = "XA Transaction" weight = 1 +++ `XAShardingSphereTransactionManager` is XA transaction manager of Apache ShardingSphere. Its main responsibility is manage and adapt multiple data sources, and sent corresponding transactions to concrete XA transaction manager. When receiving `set autoCommit=0` from client, `XAShardingSphereTransactionManager` will use XA transaction managers to start overall XA transactions, which is marked by XID. After `XAShardingSphereTransactionManager` register the corresponding XAResource to the current XA transaction, transaction manager will send `XAResource.start` command to databases. After databases received `XAResource.end` command, all SQL operator will mark as XA transaction. For example: ``` XAResource1.start ## execute in the enlist phase statement.execute("sql1"); statement.execute("sql2"); XAResource1.end ## execute in the commit phase ``` `sql1` and `sql2` in example will be marked as XA transaction. After `XAShardingSphereTransactionManager` receives the commit command in the access, it will delegate it to the actual XA manager. It will collect all the registered XAResource in the thread, before sending `XAResource.end` to mark the boundary for the XA transaction. Then it will send prepare command one by one to collect votes from XAResource. If all the XAResource feedback is OK, it will send commit command to finally finish it; If there is any No XAResource feedback, it will send rollback command to roll back. After sending the commit command, all XAResource exceptions will be submitted again according to the recovery log to ensure the atomicity and high consistency. For example: ``` XAResource1.prepare ## ack: yes XAResource2.prepare ## ack: yes XAResource1.commit XAResource2.commit XAResource1.prepare ## ack: yes XAResource2.prepare ## ack: no XAResource1.rollback XAResource2.rollback ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: Wayfair.md

title: "Wayfair" icon: /images/logos/powered-by/Wayfair.png hasLink: "https://www.youtube.com/watch?v=ugyaBNdunDE&list=PL4dEBWmGSIU9OkXQU2OAXmITPLhiMSPRp&index=43" <!-- 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: Meshery (Provisioning / Automation & Configuration)
File: docker.md

layout: default title: Docker permalink: installation/docker type: installation category: docker redirect_from: installation/platforms/docker display-title: "false" language: en list: include image: /assets/img/platforms/docker.svg abstract: Install Meshery on Docker {% include installation/installation_prerequisites.html %} Follow these installation steps to use Docker and Docker Compose to run Meshery. Users often choose this installation approach in order to run Meshery on their local machine. If you need to install docker, see and if you need to install docker-compose, see . Start Meshery by executing: <!-- <pre class="codeblock-pre" style="padding: 0; font-size:0px;"><div class="codeblock" style="display: block;"> <div class="clipboardjs" style="padding: 0"> <span style="font-size:0;">curl -L https://meshery.io/install | PLATFORM=docker bash -</span> </div> <div class="window-buttons"></div> <div id="termynal1" style="width:100%; height:150px; max-width:100%;" data-termynal=""> <span data-ty="input">curl -L https://meshery.io/install | PLATFORM=docker bash -</span> <span data-ty="progress"></span> <span data-ty="">Successfully installed Meshery</span> </div> </div> </pre> <script src="/assets/js/terminal.js" data-termynal-container="#termynal1"></script> --> {% capture code_content %}mesheryctl system start{% endcapture %} {% include code.html code=code_content %} Optionally, you can verify the health of your Meshery deployment, using <a href='/reference/mesheryctl/system/check'>mesheryctl system check</a>. You're ready to use Meshery! Open your browser and navigate to the Meshery UI. {% include_cached installation/accessing-meshery-ui.md %} {% include related-discussions.html tag="meshery" %}
Project: Bouncy Castle (Provisioning / Security & Compliance)
File: SECURITY.md

If you think that you have found a security vulnerability, please report it to this email address: Describe the issue including all details, for example: Short summary of the problem Steps to reproduce Affected API versions Logs if available The Bouncy Castle team will send a response indicating the next steps in handling your report. You may be asked to provide additional information or guidance. If the issue is confirmed as a vulnerability, we will open a Security Advisory and acknowledge your contributions as part of it. Optionally, you can have your name and contact information listed in as well. Please note we endeavor to issue patched releases that deal with security issues as soon as they are made known to us, ideally prior to issuing a Security Advisory where otherwise possible. In some cases, particularly if it relates to a FIPS release, delays due to external processes may delay the issuing of a Security Advisory.
Project: YugabyteDB (App Definition and Development / Database)
File: yba_storage-config_s3.md

Manage a YugabyteDB Anywhere S3 storage configuration Manage a S3 storage configuration in YugabyteDB Anywhere ``` yba storage-config s3 [flags] ``` ``` -n, --name string [Optional] The name of the storage configuration for the operation. Required for create, delete, describe, update. -h, --help help for s3 ``` ``` -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 storage configurations - Create an S3 YugabyteDB Anywhere storage configuration - Delete a S3 YugabyteDB Anywhere storage configuration - Describe a S3 YugabyteDB Anywhere storage configuration - List S3 YugabyteDB Anywhere storage-configurations - Update an S3 YugabyteDB Anywhere storage configuration
Project: FOSSA (Provisioning / Security & Compliance)
File: composer.md

When developing in PHP, is commonly used to manage dependencies. | Strategy | Direct Deps | Transitive Deps | Edges | Classifies Dev Dependencies | Container Scanning | | - | | | | | | | composer.lock | :whitecheckmark: | :whitecheckmark: | :whitecheckmark: | :whitecheckmark: | :whitecheckmark: | Find a file named `composer.lock`. Parse `composer.lock` to identify direct and transitive dependencies. Execute `composer init` to create a new project or create `composer.json` manually: Example composer.json: ```json { "name": "fossa/php-project", "description": "example php project", "require": { "michelf/php-markdown": "^1.9" }, "require-dev": { "webmozart/assert": "^1.10" }, "authors": [ { "name": "Megh", "email": "megh@fossa.com" } ] } ``` Execute `composer update` to install and pin dependencies - this will create (or modify) the `composer.lock` file. Execute `fossa analyze -o` on the project to print analyzed dependency graphing (this will not upload any analysis to any endpoint) You can explicitly specify an analysis target in `.fossa.yml` file. The example below will exclude all analysis targets except for the composer. ```yaml version: 3 targets: only: type: composer ```