cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: updating-dependencies.md

Run `make deps-update` to simply update the golang dependencies to their latest states. If specific changes are needed, first manipulate our main . Dependencies for are located in a separate . Changing in the staging area will be inherited by the main go.mod when running `make deps-update`. To update k8s dependencies please follow We can build our own base images for various architectures with bazel without the need of machines of that architecture. Out test container base images is defined at this . If you need to add new RPMs into the test base image, you can simply add the RPM package to and run `make rpm-deps` afterwards. `make rpm-deps` can periodically be run to just update to the latest RPM packages. The resolved RPMs are then added to the and the `rpmtree` targets in are updated. Finally no longer needed RPM definitions are removed from the WORKSPACE. The updated `rpmtree` dependencies are the base for the test image containers. To update the RPM repositories in use, change . This is an example entry for Fedora 32 on `aarch64`: ```yaml arch: aarch64 metalink: https://mirrors.fedoraproject.org/metalink?repo=fedora-32&arch=aarch64 name: 32-aarch64-primary-repo ``` Here the corresponding entry for `x86_64`: ```yaml arch: x86_64 metalink: https://mirrors.fedoraproject.org/metalink?repo=fedora-32&arch=x86_64 name: 32-x86_64-primary-repo ``` Arbitrary RPM repos can be used too. Demonstrated here by referencing a Fedora COPR repo: ```yaml arch: x86_64 baseurl: https://download.copr.fedorainfracloud.org/results/@kubevirt/libvirt-6.6.0-8.el8/fedora-32-x86_64/ name: kubevirt/libvirt-copr-x86_64 ``` More information can be found at . Works the same way like for the RPM test dependencies. `bazeldnf` does some initial checks based on sha256. Notably the metalink, repomd.xml and the packages XML are verified. These checks happen whenever `make rpm-deps` is run. However, since we have no guarantee to still have the same RPMs available on subsequent runs, it is hard to check based on this the validity of the content in CI. RPM repos use therefore GPG signing to verify the origin of the content. Therefore, local and CI verification based on gpg keys can be performend by executing the `make verify-rpm-deps` command. Create architecture specific entries in and . Adjust the select clauses on all container entries to choose the right target architecture and the right base image. Add architecture specific entries to For x86_64 libvirt-devel dependencies exist for linking and unit-testing. Updating or adding such targets for other architectures is only necessary if the unit tests are supposed to be executed on the target platform. Otherwise it is sufficient to only create images for the target-platform with libvirt dependencies installed.
Project: kpt (Provisioning / Automation & Configuration)
File: PULL_REQUEST_TEMPLATE.md

<!-- Thanks for sending a pull request! Here are some tips for you: In your PR, please ensure that you include the following information: a description of the change the motivation for the change what issue it fixes, if any, in GitHub syntax (e.g. Fixes #XYZ) Both the description and motivation may reference other issues and PRs, but should be mostly understandable without following the links (e.g. when reading the git commit log). If you are updating the documentation, please do it in separate PRs from code changes and the commit message should start with `Docs:`. PLEASE REMOVE THIS COMMENT BLOCK BEFORE SUBMITTING THE PR (the bits between the arrows) -->
Project: LinuxKit (Provisioning / Automation & Configuration)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC
Project: KICS (Provisioning / Security & Compliance)
File: 6425c98b-ca4e-41fe-896a-c78772c131f8.md

title: PostgreSQL Server Infrastructure Encryption Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6425c98b-ca4e-41fe-896a-c78772c131f8 Query name: PostgreSQL Server Infrastructure Encryption Disabled Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Encryption URL: PostgreSQL Server Infrastructure Encryption should be enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="21" resource "azurermpostgresqlserver" "positive1" { name = "example-psqlserver" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name administrator_login = "psqladminun" administratorloginpassword = "H@Sh1CoR3!" skuname = "GPGen5_4" version = "9.6" storage_mb = 640000 backupretentiondays = 7 georedundantbackup_enabled = true autogrowenabled = true publicnetworkaccess_enabled = false sslenforcementenabled = true sslminimaltlsversionenforced = "TLS1_2" infrastructureencryptionenabled = false } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "azurermpostgresqlserver" "positive2" { name = "example-psqlserver" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name administrator_login = "psqladminun" administratorloginpassword = "H@Sh1CoR3!" skuname = "GPGen5_4" version = "9.6" storage_mb = 640000 backupretentiondays = 7 georedundantbackup_enabled = true autogrowenabled = true publicnetworkaccess_enabled = false sslenforcementenabled = true sslminimaltlsversionenforced = "TLS1_2" } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermpostgresqlserver" "negative" { name = "example-psqlserver" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name administrator_login = "psqladminun" administratorloginpassword = "H@Sh1CoR3!" skuname = "GPGen5_4" version = "9.6" storage_mb = 640000 backupretentiondays = 7 georedundantbackup_enabled = true autogrowenabled = true publicnetworkaccess_enabled = false sslenforcementenabled = true sslminimaltlsversionenforced = "TLS1_2" infrastructureencryptionenabled = true } ```
Project: Checkov (Provisioning / Security & Compliance)
File: Jenkins.md

layout: default published: true title: Jenkins nav_order: 1 Below is a simple example integration with Jenkins using the Checkov container image. This will result in build failures whenever developers create and modify infrastructure as code with misconfigurations. To prevent developer frustration from failed builds, we recommend training and encouraging usage of Checkov's inline suppressions. Create new Jenkins Pipeline or integrate into an existing one. Add new a stage into the pipeline definition using a `pipeline script` ```groovy pipeline { agent any stages { stage('Checkout') { steps { git branch: 'master', url: 'https://github.com/bridgecrewio/terragoat' stash includes: '/*', name: 'terragoat' } } stage('Checkov') { steps { script { docker.image('bridgecrew/checkov:latest').inside("--entrypoint=''") { unstash 'terragoat' try { sh 'checkov -d . --use-enforcement-rules -o cli -o junitxml --output-file-path console,results.xml --repo-id example/terragoat --branch master' junit skipPublishingChecks: true, testResults: 'results.xml' } catch (err) { junit skipPublishingChecks: true, testResults: 'results.xml' throw err } } } } } } options { preserveStashes() timestamps() } } ``` Alternatively, add the following script to install and run Checkov without an image: ```groovy sh "pipenv run pip install checkov" sh "pipenv run checkov -d . --use-enforcement-rules -o cli -o junitxml --output-file-path console,results.xml --repo-id example/terragoat --branch master" ``` Example Run `Build Now` View build dashboard View job status Review test result
Project: FoundationDB (App Definition and Development / Database)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at fdb-conduct@group.apple.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at
Project: Weaviate (App Definition and Development / Database)
File: CONTRIBUTING.md

We really appreciate that you are willing to spend some time and effort to make Weaviate better for everyone! We have a detailed as a part of our documentation. If you are new, we recommend reading through the after reading this overview. We use the `good-first-issue` labels on issues that we think are great to get started. Typically, they are issues that are isolated to a specific area of Weaviate, e.g. only the API layer or only a specific package. To contribute to Weaviate Core you should have at least basic Golang skills. It is also tremendously helpful if you have successfully used Weaviate before, so that you have a rough understanding of the effects of changes etc. Any PR must include tests. We understand that not everyone is very familiar with testing strategies, and how we have setup our tests. This should be a great start. If you have completed a change, but are struggling with the test, you can also open a Draft PR and ask someone from our team for help. The Weaviate team consists of some of the nicest people on this planet. If something is unclear or you'd like a second opinion, please don't hesitate to ask. We are glad that you want to help us, so naturally we will also do our best to help you on this journey Please note that the Weaviate team uses Linux and Mac (darwin/arm64) machines exclusively. Development on Windows may lead to unexpected issues. Here are some guides to get started in no time: Please tag your commit(s) with the appropriate GH issue that your change refers to, e.g. `gh-9001 reduce memory allocations of ACME widget`. Please also include something in your PR description to indicate which issue it will close, e.g. `fixes #9001` or `closes #9001`. If you open an external pull request our CI pipeline will get started. This external run will not have access to secrets. This prevents people from submitting a malicious PR to steal secrets. As a result the CI run will be slightly different from an internal one. For example, it will not automatically push a Docker image. If your PR is merged, a container with your changes will be built from the trunk. Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. ](CODEOFCONDUCT.md) Contributions to Weaviate must be accompanied by a Contributor License Agreement. You (or your employer) retain the copyright to your contribution; this simply gives us permission to use and redistribute your contributions as part of Weaviate. Go to to read the current agreement. The process works as follows: You contribute by opening a . If you have not contributed before, our bot will ask to agree with the CLA
Project: YugabyteDB (App Definition and Development / Database)
File: drop_role.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="435" height="80" viewbox="0 0 435 80"><path class="connector" d="M0 52h15m53 0h10m52 0h30m32 0h10m64 0h20m-141 0q5 0 5 5v8q0 5 5 5h116q5 0 5-5v-8q0-5 5-5m5 0h30m-5 0q-5 0-5-5v-20q0-5 5-5h35m24 0h35q5 0 5 5v20q0 5-5 5m-5 0h35"/><polygon points="0,59 5,52 0,45" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="35" width="53" height="25" rx="7"/><text class="text" x="25" y="52">DROP</text><rect class="literal" x="78" y="35" width="52" height="25" rx="7"/><text class="text" x="88" y="52">ROLE</text><rect class="literal" x="160" y="35" width="32" height="25" rx="7"/><text class="text" x="170" y="52">IF</text><rect class="literal" x="202" y="35" width="64" height="25" rx="7"/><text class="text" x="212" y="52">EXISTS</text><rect class="literal" x="346" y="5" width="24" height="25" rx="7"/><text class="text" x="356" y="22">,</text><a xlink:href="../../../syntaxresources/grammardiagrams#role-name"><rect class="rule" x="316" y="35" width="84" height="25"/><text class="text" x="326" y="52">role_name</text></a><polygon points="431,59 435,59 435,45 431,45" style="fill:black;stroke-width:0"/></svg>
Project: StarRocks (App Definition and Development / Database)
File: case_when.md

displayed_sidebar: "English" CASE is a conditional expression. It returns the result in the THEN clause if a condition in the WHEN clause evaluates to true. If none of the conditions evaluate to true, it returns the result in the optional ELSE clause. If ELSE is not present, NULL is returned. The CASE expression comes in two forms: Simple CASE ```SQL CASE expression WHEN expression1 THEN result1 [WHEN expression2 THEN result2] ... [WHEN expressionN THEN resultN] [ELSE result] END ``` For this syntax, `expression` is compared to each expression in the WHEN clause. If an equal expression is found, the result in the THEN clause is returned. If no equal expression is found, the result in the ELSE clause is returned if ELSE is present. Searched CASE ```SQL CASE WHEN condition1 THEN result1 [WHEN condition2 THEN result2] ... [WHEN conditionN THEN resultN] [ELSE result] END ``` For this syntax, each condition in the WHEN clause is evaluated until one is true and the corresponding result in the THEN clause is returned. If no condition evaluates to true, the result in the ELSE clause is returned, if ELSE is present. The first CASE equals the second one as follows: ```SQL CASE WHEN expression = expression1 THEN result1 [WHEN expression = expression2 THEN result2] ... [WHEN expression = expressionN THEN resultN] [ELSE result] END ``` `expressionN`: the expression to compare. Multiple expressions must be compatible in data types. `conditionN`: the condition that can evaluate to a BOOLEAN value. `resultN` must be compatible in data types. The return value is of the common type of all types in the THEN clause. Suppose table `test_case` has the following data: ```SQL CREATE TABLE test_case( name STRING, gender INT, ) DISTRIBUTED BY HASH(name); INSERT INTO test_case VALUES ("Andy",1), ("Jules",0), ("Angel",-1), ("Sam",null); SELECT * FROM test_case; +-+--+ | name | gender | +-+--+ | Angel | -1 | | Andy | 1 | | Sam | NULL | | Jules | 0 | +-+--+-+ ``` ELSE is specified and the result in ELSE is returned if no equal expression is found. ```plain mysql> select gender, case gender when 1 then 'male' when 0 then 'female' else 'error' end gender_str from test_case; +--++ | gender | gender_str | +--++ | NULL | error | | 0 | female | | 1 | male | | -1 | error | +--++ ``` ELSE is not specified and NULL is returned if no condition evaluates to true. ```plain select gender, case gender when 1 then 'male' when 0 then 'female' end gender_str from test_case; +--++ | gender | gender_str | +--++ | 1 | male | | -1 | NULL | | NULL | NULL | | 0 | female | +--++ ``` ```plain mysql> select gender, case when gender = 1 then 'male' when gender = 0 then 'female' end gender_str from test_case; +--++ | gender | gender_str | +--++ | NULL | NULL | | -1 | NULL | | 1 | male | | 0 | female | +--++ ``` case when, case, case_when, case...when
Project: FOSSA (Provisioning / Security & Compliance)
File: code-related.md

name: Code related about: Questions or suggestions related to the code or architecture of `fossa-cli` itself. title: "[CODE] " labels: '' assignees: '' <!-- Code related issues are those that are asking questions or making suggestions about the code or architecture of the CLI. Conceptually, these issues are related to pull requests, in that the subject of the issue is some section of the `fossa-cli` code base. The question or commentary itself is free form; feel free to word this however you'd like! -->
Project: ArangoDB (App Definition and Development / Database)
File: spare_storage.md

+++ title = "`uint16t sparestorage(const basicresult|basicoutcome *) noexcept`" description = "Returns the sixteen bits of spare storage in the specified result or outcome." +++ Returns the sixteen bits of spare storage in the specified result or outcome. You can set these bits using {{% api "void setsparestorage(basicresult|basicoutcome *, uint16_t) noexcept" %}}. Overridable: Not overridable. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::hooks` Header: `<boost/outcome/basic_result.hpp>`
Project: ThreatMapper (Provisioning / Security & Compliance)
File: s3.md

title: S3 Archive selected resources to your AWS S3 bucket into selected folder [format of the file will be .json] Type your S3 bucket name (bucket should be created before this) Set S3 folder name that will be created inside the bucket if not present Provide your access key and secret access key provided by amazon Select region Choose resources Click Add button
Project: VMClarity (Provisioning / Security & Compliance)
File: test_e2e.md

- - ``` DOCKER_REGISTRY=<your docker registry> make push-docker ``` Ensure you have an SSH key pair uploaded to AWS Ec2 Go to CloudFormation -> Create Stack -> Upload template. Upload the VMClarity.cfn Follow the wizard through to the end Set the `VMClarity Backend Container Image` and `VMClarity Scanner Container Image` parameters in the wizard to use custom images (from step 1.) for deployment. Change the Asset Scan Delete Policy to `OnSuccess` or `Never` if debugging scanner VMs is required. Wait for install to complete Get the IP address from the CloudFormation stack's Output Tab `ssh ubuntu@<ip address>` Check the VMClarity Logs ``` sudo journalctl -u vmclarity ``` Copy the example into the ubuntu user's home directory ``` scp scanConfig.json ubuntu@<ip address>:~/scanConfig.json ``` Edit the scanConfig.json a. Give the scan config a unique name b. Enable the different scan families you want: ``` "scanFamiliesConfig": { "sbom": { "enabled": true }, "vulnerabilities": { "enabled": true }, "exploits": { "enabled": true } }, ``` c. Configure the scope of the test By Region, VPC or Security group: ``` "scope": "contains(assetInfo.location, '<name of region>/<name of vpc>') and contains(assetInfo.securityGroups, '{\"id\":\"<name of sec group>\"}')" ``` By tag: ``` "scope": "contains(assetInfo.tags, '{\"key\":\"<key>\",\"value\":\"<value>\"}')" ``` All: ``` "scope": "" ``` d. Set operationTime to the time you want the scan to run. As long as the time is in the future it can be within seconds. While ssh'd into the VMClarity server run ``` curl -X POST http://localhost:8080/api/scanConfigs -H 'Content-Type: application/json' -d @scanConfig.json ``` Check VMClarity logs to ensure that everything is performing as expected ``` sudo journalctl -u vmclarity ``` Monitor the asset scans Get scans: ``` curl -X GET http://localhost:8080/api/scans ``` After the operationTime in the scan config created above there should be a new scan object created in Pending. Once discovery has been performed, the scan's assetIDs list should be populated will all the assets to be scanned by this scan. The scan will then create all the "assetScans" for tracking the scan process for each asset. When that is completed the scan will move to "InProgress". Get asset scans: ``` curl -X GET http://localhost:8080/api/assetScans ```
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: backups.md

Lagoon makes use of the to provide backup functionality for both database data as well as containers' persistent storage volumes. This operator utilizes to catalog these backups, which is typically connected to an AWS S3 bucket to provide secure, off-site storage for the generated backups. Backups of databases and containers' persistent storage volumes happens nightly within production environments by default. If a different backup schedule for production backups is required, this can be specified at a project level via setting the "Backup Schedule" variables in the project's file. Production environment backups will be held according to the following schedule by default: Daily: 7 Weekly: 6 Monthly: 1 Hourly: 0 If a different retention period for production backups is required, this can be specified at a project level via setting the "Backup Retention" variables in the project's file. Backups of development environments are attempted nightly and are strictly a best effort service. Backups stored in Restic will be tracked within Lagoon, and can be recovered via the "Backup" tab for each environment in the Lagoon UI. Lagoon supports custom backup and restore locations via the use of the "" and/or "" variables stored in the Lagoon API for each project. !!! danger Proceed with caution: Setting these variables will override backup/restore storage locations that may be configured at a cluster level. Any misconfiguration will cause backup/restore failures.
Project: KubeMQ (App Definition and Development / Streaming & Messaging)
File: kubemq_queries_attach.md

Queries attach to 'queries' channels command Queries attach command allows to display 'queries' channel content for debugging proposes ``` kubemq queries attach [flags] ``` ``` kubemq queries attach * kubemq queries attach some-query kubemq queries attach some-queries1 some-queries2 kubemq queries attach some-queries -i some* kubemq queries attach some-queries -e not-some* ``` ``` -e, --exclude stringArray set (regex) strings to exclude -h, --help help for attach -i, --include stringArray set (regex) strings to include ``` - Execute Kubemq 'queries'