cwielenb/CNCF-Dataset huggingface dataset:
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: continuous_integration.md

+++ title = "Chef Habitat and Continuous Integration" description = "Chef Habitat and Continuous Integration" gh_repo = "habitat" [menu] [menu.habitat] title = "Continuous Integration" identifier = "habitat/packages/habitat-and-continuous-integration" parent = "habitat/packages" weight = 200 +++ Examples: , , and Continuous integration allows you to build, test, and deploy your code by using CLI tools and plugins. Chef Habitat includes the which allows you to do interactive builds on your developer workstation, or non-interactive builds with your continuous integration server. Your continuous integration server can also call the Chef Habitat CLI to promote your Chef Habitat packages to different channels, enabling your applications to update themselves. Chef Habitat is not a continuous integration server and can make builds and promotion processes done by your continuous integration server easier. The provides a clean room build environment for your application build. In effect, builds that occur on a developer's workstation, or on a continuous integration server, will build in the same manner. Developers no longer need to worry about entire classes of "it works on my box" problems. Build engineers no longer need to create unique and difficult to maintain worker nodes for continuous integration servers. Instead, the Chef Habitat plan.sh file contains all the information needed to build the entire application, from dependency management, runtime environment binaries, packaging, and application lifecycle hooks. When using the , your continuous integration server can focus more on what it is good at doing, instead of worrying about managing custom plugins and their potential conflicts. Your continuous integration server can promote a Chef Habitat package (a .hart file) to a channel by calling the . This promotion method allows you to deploy a new version of your application in a pull-based manner by using the Chef Habitat Supervisor. Because this promotion process can be invoked non-interactively through the , you can manage your deployments using your existing tooling. If you choose, you can also do this promotion process manually. More complex application environments can also invoke the promotion process using a scheduling tool or provisioning tool to help manage infrastructure resources in addition to promoting Chef Habitat packages.
Project: Harbor (Provisioning / Container Registry)
File: 7-10-Filter.md

Test 7-10 - Filter ======= To verify the filer in replication rule can work as expected. User guide This test requires that at least two Harbor instances are running and available. Create a new replication rule whose triggering condition is set to manual and tag filer is set to release-\. Push an image whose tag is release-1.0. Push an image whose tag is dev-1.0. Login UI with admin user. Select the rule and click `REPLICATE` button. In step 4, one or two jobs should be started. The image in step 1 should be replicated to the remote registry and the image in step 2 should not be replicated to remote registry. None
Project: YugabyteDB (App Definition and Development / Database)
File: do.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="359" height="50" viewbox="0 0 359 50"><path class="connector" d="M0 22h15m38 0h30m87 0h10m87 0h20m-219 0q5 0 5 5v8q0 5 5 5h194q5 0 5-5v-8q0-5 5-5m5 0h10m47 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="38" height="25" rx="7"/><text class="text" x="25" y="22">DO</text><rect class="literal" x="83" y="5" width="87" height="25" rx="7"/><text class="text" x="93" y="22">LANGUAGE</text><a xlink:href="../../../syntaxresources/grammardiagrams#lang-name"><rect class="rule" x="180" y="5" width="87" height="25"/><text class="text" x="190" y="22">langname</text></a><a xlink:href="../../../syntaxresources/grammar_diagrams#code"><rect class="rule" x="297" y="5" width="47" height="25"/><text class="text" x="307" y="22">code</text></a><polygon points="355,29 359,29 359,15 355,15" style="fill:black;stroke-width:0"/></svg>
Project: Ansible (Provisioning / Automation & Configuration)
File: pr_duplicate.md

Hi! Thanks very much for your submission to Ansible. It means a lot to us that you've taken time to contribute. It looks like the work from this pull request is a duplicate of the following PR(s): INSERT PR(S) HERE Based on this, we are going to close this PR in favor of the above as a consolidated location to keep track of the issue. However, we're absolutely always up for discussion. In the future, sometimes starting a discussion on the development list prior to implementing a feature can make getting things included a little easier, but it's not always necessary. Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time. If you or anyone else has any further questions, please let us know by using any of the communication methods listed in the page below: <https://docs.ansible.com/ansible/latest/community/communication.html> Thank you once again for this and your interest in Ansible!
Project: Beam (App Definition and Development / Streaming & Messaging)
File: scio.md

title: "Scio" icon: /images/logos/powered-by/scio.png hasNav: true hasLink: "https://www.youtube.com/watch?v=cGvaQp_h5ek&list=PL4dEBWmGSIU9OkXQU2OAXmITPLhiMSPRp&index=55" cardDescription: "Scio is a Scala API for Apache Beam and Google Cloud Dataflow inspired by Apache Spark and Scalding." <!-- 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. --> Scio is a Scala API for Apache Beam and Google Cloud Dataflow inspired by Apache Spark and Scalding.
Project: KICS (Provisioning / Security & Compliance)
File: 91f16d09-689e-4926-aca7-155157f634ed.md

title: ECS Service Without Running Tasks hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 91f16d09-689e-4926-aca7-155157f634ed Query name: ECS Service Without Running Tasks Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Availability URL: ECS Service should have at least 1 task running<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsecsservice" "positive1" { name = "positive1" cluster = awsecscluster.example.id desired_count = 0 } ``` ```tf title="Negative test num. 1 - tf file" resource "awsecsservice" "negative1" { name = "negative1" cluster = awsecscluster.example.id deploymentmaximumpercent = 200 deploymentminimumhealthy_percent = 100 } resource "awsecsservice" "kmecsservice" { name = "kmecsservice_${var.environment}" cluster = awsecscluster.kmecscluster.id taskdefinition = awsecstaskdefinition.kmecstask.arn desired_count = 1 launch_type = "FARGATE" load_balancer { targetgrouparn = var.elbtargetgroup_arn container_name = "km-frontend" container_port = 80 } network_configuration { assignpublicip = true subnets = var.private_subnet securitygroups = [ var.elbsg ] } tags = merge(var.default_tags, { }) } ```
Project: StarRocks (App Definition and Development / Database)
File: divide.md

displayed_sidebar: "English" Return the quotient of x divide y. If y is 0, return null. ```Haskell divide(x, y) ``` `x`: The supported types are DOUBLE, FLOAT, LARGEINT, BIGINT, INT, SMALLINT, TINYINT, DECIMALV2, DECIMAL32, DECIMAL64, DECIMAL128. `y`: The supported types are the same as `x`. Returns a value of the DOUBLE data type. If you specify a non-numeric value, this function returns `NULL`. ```Plain Text mysql> select divide(3, 2); +--+ | divide(3, 2) | +--+ | 1.5 | +--+ 1 row in set (0.00 sec) ```
Project: Meshery (Provisioning / Automation & Configuration)
File: aad-pod-identity.md

layout: integration title: Azure Active Directory (AAD) subtitle: Collaborative and visual infrastructure as code for Azure Active Directory (AAD) image: /assets/img/integrations/aad-pod-identity/icons/color/aad-pod-identity-color.svg permalink: extensibility/integrations/aad-pod-identity docURL: https://docs.meshery.io/extensibility/integrations/aad-pod-identity description: integrations-category: Provisioning integrations-subcategory: Security & Compliance registrant: Artifact Hub components: name: azure-assigned-identity colorIcon: assets/img/integrations/aad-pod-identity/components/azure-assigned-identity/icons/color/azure-assigned-identity-color.svg whiteIcon: assets/img/integrations/aad-pod-identity/components/azure-assigned-identity/icons/white/azure-assigned-identity-white.svg description: name: azure-identity colorIcon: assets/img/integrations/aad-pod-identity/components/azure-identity/icons/color/azure-identity-color.svg whiteIcon: assets/img/integrations/aad-pod-identity/components/azure-identity/icons/white/azure-identity-white.svg description: name: azure-identity-binding colorIcon: assets/img/integrations/aad-pod-identity/components/azure-identity-binding/icons/color/azure-identity-binding-color.svg whiteIcon: assets/img/integrations/aad-pod-identity/components/azure-identity-binding/icons/white/azure-identity-binding-white.svg description: name: azure-pod-identity-exception colorIcon: assets/img/integrations/aad-pod-identity/components/azure-pod-identity-exception/icons/color/azure-pod-identity-exception-color.svg whiteIcon: assets/img/integrations/aad-pod-identity/components/azure-pod-identity-exception/icons/white/azure-pod-identity-exception-white.svg description: featureList: [ "Use Azure Active Directory pod-managed identities in Azure Kubernetes Service.", "A maximum of 200 pod-managed identities are allowed for a cluster.", "Pod-managed identities are available on Linux node pools only." ] howItWorks: "Federate with any external identity provider" howItWorksDetails: "Azure AD workload identity authentication method replaces pod-managed identity, which integrates with the Kubernetes native capabilities to federate with any external identity providers on behalf of the application." language: en list: include type: extensibility category: integrations
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: BENCHMARK.md

```bash go test -bench XXX -run XXX -benchtime 30s ``` ``` goos: linux goarch: amd64 pkg: github.com/go-openapi/swag cpu: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz BenchmarkToXXXName/ToGoName-4 862623 44101 ns/op 10450 B/op 732 allocs/op BenchmarkToXXXName/ToVarName-4 853656 40728 ns/op 10468 B/op 734 allocs/op BenchmarkToXXXName/ToFileName-4 1268312 27813 ns/op 9785 B/op 617 allocs/op BenchmarkToXXXName/ToCommandName-4 1276322 27903 ns/op 9785 B/op 617 allocs/op BenchmarkToXXXName/ToHumanNameLower-4 895334 40354 ns/op 10472 B/op 731 allocs/op BenchmarkToXXXName/ToHumanNameTitle-4 882441 40678 ns/op 10566 B/op 749 allocs/op ``` ~ x10 performance improvement and ~ /100 memory allocations. ``` goos: linux goarch: amd64 pkg: github.com/go-openapi/swag cpu: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz BenchmarkToXXXName/ToGoName-4 9595830 3991 ns/op 42 B/op 5 allocs/op BenchmarkToXXXName/ToVarName-4 9194276 3984 ns/op 62 B/op 7 allocs/op BenchmarkToXXXName/ToFileName-4 17002711 2123 ns/op 147 B/op 7 allocs/op BenchmarkToXXXName/ToCommandName-4 16772926 2111 ns/op 147 B/op 7 allocs/op BenchmarkToXXXName/ToHumanNameLower-4 9788331 3749 ns/op 92 B/op 6 allocs/op BenchmarkToXXXName/ToHumanNameTitle-4 9188260 3941 ns/op 104 B/op 6 allocs/op ``` ``` goos: linux goarch: amd64 pkg: github.com/go-openapi/swag cpu: AMD Ryzen 7 5800X 8-Core Processor BenchmarkToXXXName/ToGoName-16 18527378 1972 ns/op 42 B/op 5 allocs/op BenchmarkToXXXName/ToVarName-16 15552692 2093 ns/op 62 B/op 7 allocs/op BenchmarkToXXXName/ToFileName-16 32161176 1117 ns/op 147 B/op 7 allocs/op BenchmarkToXXXName/ToCommandName-16 32256634 1137 ns/op 147 B/op 7 allocs/op BenchmarkToXXXName/ToHumanNameLower-16 18599661 1946 ns/op 92 B/op 6 allocs/op BenchmarkToXXXName/ToHumanNameTitle-16 17581353 2054 ns/op 105 B/op 6 allocs/op ```
Project: KICS (Provisioning / Security & Compliance)
File: b28bcd2f-c309-490e-ab7c-35fc4023eb26.md

title: Google Compute SSL Policy Weak Cipher In Use hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b28bcd2f-c309-490e-ab7c-35fc4023eb26 Query name: Google Compute SSL Policy Weak Cipher In Use Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: This query confirms if Google Compute SSL Policy Weak Chyper Suits is Enabled, to do so we need to check if TLS is TLS12, because other version have Weak Chypers<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="16 2" name: create a SSL policy google.cloud.gcpcomputessl_policy: name: test_object profile: CUSTOM custom_features: TLSECDHEECDSAWITHAES256GCM_SHA384 TLSECDHERSAWITHAES256GCM_SHA384 project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present name: create a SSL policy2 google.cloud.gcpcomputessl_policy: name: test_object2 profile: CUSTOM mintlsversion: TLS11 custom_features: TLSECDHEECDSAWITHAES256GCM_SHA384 TLSECDHERSAWITHAES256GCM_SHA384 project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: create a SSL policy google.cloud.gcpcomputessl_policy: name: test_object profile: CUSTOM mintlsversion: TLS12 custom_features: TLSECDHEECDSAWITHAES256GCM_SHA384 TLSECDHERSAWITHAES256GCM_SHA384 project: test_project auth_kind: serviceaccount serviceaccountfile: /tmp/auth.pem state: present ```
Project: Trivy (Provisioning / Security & Compliance)
File: trivy_plugin_info.md

Show information about the specified plugin ``` trivy plugin info PLUGIN_NAME ``` ``` -h, --help help for info ``` ``` --cache-dir string cache directory (default "/path/to/cache") -c, --config string config path (default "trivy.yaml") -d, --debug debug mode --generate-default-config write the default config to trivy-default.yaml --insecure allow insecure server connections -q, --quiet suppress progress bar and log output --timeout duration timeout (default 5m0s) -v, --version show version ``` - Manage plugins
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: v0.19.0.md

title: v0.19.0 weight: 999981000 Input variable names containing special words IP, HTTP, and URL were incorrectly converted to contiguous lowercase snake case. fixes this issue, and the Ansible operator now correctly wraps special words in underscores and lower-cases them within snake-cased variable names. For example: ``` egressIPs --> egress_ips URLsegressIPsEgressHTTPs --> urlsegressipsegress_https ``` Nothing needs to be changed in an existing project to fix this issue. See for more details. See the that walks through an example of how to migrate a Go based operator project from the old layout to the v0.19.0 layout. Migrating to v0.19.0 before v1.0.0 is practical if you plan to migrate your project between one minor version at a time. If you wish to migrate directly from the old layout to the latest v1.0.0+ layout, see the . See for more details. For Helm-based operators to be more aligned with Helm, the `UpdateSuccessful` condition reason was renamed to `UpgradeSuccessful` for the `ReleaseFailed` condition. Note that this is NOT a breaking change for Helm-based operators themselves. However, any script or code that is depending on this condition reason must be updated to use `UpgradeSuccessful` instead of `UpdateSuccessful`. See for more details. For Helm-based operators to be more aligned with Helm, the `UpdateError` condition reason was renamed to `UpgradeError` for the `ReleaseFailed` condition. Note that this is NOT a breaking change for Helm-based operators themselves. However, any script or code that is depending on this condition reason must be updated to use `UpgradeError` instead of `UpdateError`. See for more details.
Project: Open Policy Administration Layer (OPAL) (Provisioning / Security & Compliance)
File: pull_request_template.md

<!-- If your PR fixes an open issue, use `Closes #999` to link your PR with the issue. #999 stands for the issue number you are fixing --> <!-- Remove this section if not applicable --> <!-- Example: Closes #31 --> <!-- List all the proposed changes in your PR --> <!-- Mark all the applicable boxes. To mark the box as done follow the following conventions --> <!-- [x] - Correct; marked as done [X] - Correct; marked as done [ ] - Not correct; marked as not done --> [x] I sign off on contributing this submission to open-source [ ] My code follows the code style of this project. [ ] My change requires changes to the documentation. [ ] I have updated the documentation accordingly. [ ] All new and existing tests passed. [ ] This PR does not contain plagiarized content. [ ] The title of my pull request is a short description of the requested changes. <!-- Add all the screenshots which support your changes --> <!-- Add notes to reviewers if applicable -->
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: DesignDocTemplate.md

| Version | Date | Changelog | | - | - | -| | 1.0.0 | 2022.x.x | initial version | | x.x.x | x.x.x | | | Reviewer | Required/Optional Reviewer | Approved?| Date | - | - | -| -| | x.x.x | Required | Approved | | | x.x.x | Required | Approved | | egkubeblocksv0-XXdesign, vMajor follows the product's version number eg The document has been approved by required approvers Design details are appropriately documented Test plan is in place User-facing documentation have been uploaded to github Supporting documentatione.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes Requirement1: Requirement2: Requirement3: Requirement1: Requirement2: Requirement3: Story1 Story2 eg Scalabilitycapacityperformance Prerequisite testing updates Unit tests Integration tests e2e tests fault injection tests
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-data-sources-troubleshooting.md

layout: global title: Troubleshooting displayTitle: Troubleshooting license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You 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. The JDBC driver class must be visible to the primordial class loader on the client session and on all executors. This is because Java's DriverManager class does a security check that results in it ignoring all drivers not visible to the primordial class loader when one goes to open a connection. One convenient way to do this is to modify compute_classpath.sh on all worker nodes to include your driver JARs. Some databases, such as H2, convert all names to upper case. You'll need to use upper case to refer to those names in Spark SQL. Users can specify vendor-specific JDBC connection properties in the data source options to do special treatment. For example, `spark.read.format("jdbc").option("url", oracleJdbcUrl).option("oracle.jdbc.mapDateToTimestamp", "false")`. `oracle.jdbc.mapDateToTimestamp` defaults to true, users often need to disable this flag to avoid Oracle date being resolved as timestamp.
Project: KICS (Provisioning / Security & Compliance)
File: e6f61c37-106b-449f-a5bb-81bfcaceb8b4.md

title: Google Compute Network Using Firewall Rule that Allows Port Range hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e6f61c37-106b-449f-a5bb-81bfcaceb8b4 Query name: Google Compute Network Using Firewall Rule that Allows Port Range Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: Google Compute Network should not use a firewall rule that allows port range<br> ```tf title="Positive test num. 1 - tf file" hl_lines="17" resource "googlecomputefirewall" "positive1" { name = "test-firewall" network = googlecomputenetwork.positive1.name allow { protocol = "icmp" } allow { protocol = "tcp" ports = ["80", "8080", "1000-2000"] } source_tags = ["web"] } resource "googlecomputenetwork" "positive1" { name = "test-network" } ``` ```tf title="Negative test num. 1 - tf file" resource "googlecomputefirewall" "negative1" { name = "test-firewall" network = googlecomputenetwork.negative1.name allow { protocol = "icmp" } allow { protocol = "tcp" ports = ["80", "8080"] } source_tags = ["web"] } resource "googlecomputenetwork" "negative1" { name = "test-network" } ```
Project: BigchainDB (App Definition and Development / Database)
File: CONTRIBUTING.md

<! Copyright 2020 Interplanetary Database Association e.V., BigchainDB and IPDB software contributors. SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0) Code is Apache-2.0 and docs are CC-BY-4.0 > There are many ways you can contribute to the BigchainDB project, some very easy and others more involved. All of that is documented elsewhere: go to the ". Note: GitHub automatically links to this file (`.github/CONTRIBUTING.md`) when a contributor creates a new issue or pull request, so you shouldn't delete it. Just use it to point people to full and proper help elsewhere.
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: bug_report.md

name: Bug Report about: Report a bug in KubeVirt title: '' labels: kind/bug assignees: '' <!-- Make sure that you visit our User Guide at https://kubevirt.io/user-guide. --> What happened: A clear and concise description of what the bug is. What you expected to happen: A clear and concise description of what you expected to happen. How to reproduce it (as minimally and precisely as possible): Steps to reproduce the behavior. Additional context: Add any other context about the problem here. Environment: KubeVirt version (use `virtctl version`): N/A Kubernetes version (use `kubectl version`): N/A VM or VMI specifications: N/A Cloud provider or hardware configuration: N/A OS (e.g. from /etc/os-release): N/A Kernel (e.g. `uname -a`): N/A Install tools: N/A Others: N/A
Project: Harbor (Provisioning / Container Registry)
File: 9-13-LDAP-user-pull-signed-images.md

Test 9-13 User pull signed images(LDAP mode) ======= To verify whether user can pull signed images with content trust enabled. User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against an LDAP or AD server. A Linux host with Docker CLI(Docker client)installed. A non-admin user that has at least one project as project admin. Same as Test 9-03 except that users are from LDAP/AD. Same as Test 9-03. None