cwielenb/CNCF-Dataset huggingface dataset:
Project: zot (Provisioning / Container Registry)
File: PULL_REQUEST_TEMPLATE.md

<!-- Thanks for sending a pull request! Here are some tips for you: Ensure you have added the unit tests for your changes. Ensure you have included output of manual testing done in the Testing section. Ensure number of lines of code for new or existing methods are within the reasonable limit. --> What type of PR is this? <!-- Add one of the following: bug cleanup documentation feature --> Which issue does this PR fix: What does this PR do / Why do we need it: If an issue # is not available please add repro steps and logs showing the issue: Testing done on this change: <!-- output of manual testing/integration tests results and also attach logs showing the fix being resolved --> Automation added to e2e: <!-- Test case added to lib/integration.sh If no, create an issue with enhancement/testing label --> Will this break upgrades or downgrades? Does this PR introduce any user-facing change?: <!-- If yes, a release note update is required: Enter your extended release note in the block below. If the PR requires additional actions from users switching to the new release, include the string "action required". --> ```release-note ``` By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: how-do-refinements-relate.md

type: runners title: "How do refinements relate?" layout: "capability-template" <!-- 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. --> <!-- Summary table --> {{< documentation/capability-matrix-big cap-data="capability-matrix" cap-view="full" cap-index=5 >}}
Project: YugabyteDB (App Definition and Development / Database)
File: yba_universe_upgrade.md

Upgrade a YugabyteDB Anywhere universe Upgrade a universe in YugabyteDB Anywhere ``` yba universe upgrade [flags] ``` ``` -f, --force [Optional] Bypass the prompt for non-interactive usage. -n, --name string [Required] The name of the universe to be ugraded. -s, --skip-validations [Optional] Skip validations before running the CLI command. -h, --help help for upgrade ``` ``` -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 universes - Gflags upgrade for a YugabyteDB Anywhere Universe - Software upgrade for a YugabyteDB Anywhere Universe
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: ansible-operator-testing.md

Status: implemented Ansible-based operators can be tested with Molecule. Please see the testing documentation: . All operators should fit into the e2e testing framework used by operator-sdk, including Ansible Operator. Add support for the `test {local|cluster}` e2e testing subcommand with Ansible Operators Integrate with existing Ansible test frameworks to provide a uniform experience across the Ansible ecosystem Maintain the existing interface for the `test` subcommands Create a new testing framework for Ansible that plays nicely with operators Allow Ansible users to write non-Ansible tests Update scaffolding to (optionally?) include initialization Set up a molecule scenario for the e2e environment (may have different behavior between `local` and `cluster` scenarios) Create a for molecule that: In the `test local` case handles the creation of the necessary resources (namespace, CRDs, roles, rolebindings, operator deployment) in the Kubernetes cluster In the `test cluster` case does nothing Add a custom entrypoint for testing that will spin up the operator and then run the proper molecule scenario, which can be included in the Ansible Operator image when it is built with the `--enable-tests` option Update the `test local` subcommand so that when it is run in the context of an Ansible Operator, it will trigger a molecule run of the proper scenario Update the `test cluster` subcommand so that when it is run in the context of an Ansible Operator, a deployment of the operator with the custom testing entrypoint is created. The behavior here should approximate the Golang operator equivalent, in terms of reporting/termination Should test scaffolding be optional, or should we always initialize tests? Can we easily get access to the `deploy/` resources from our molecule test? How do we distribute the custom molecule driver? Should `test local` and `test cluster` be two different molecule scenarios? `test local` can run molecule at the permissions required to create CRDs, roles, SAs, etc What if it isn't? Maybe we should do a best effort here, and not crash the run if we hit permissions issues. `test cluster` will be run at normal operator permissions, and will require that the prerequisites be satisfied before invocation
Project: Kapitan (Provisioning / Automation & Configuration)
File: ADOPTERS.md

If you're using Kapitan in your organization, please let us know by adding to this list on the file. <div class="grid cards" markdown> {: style="height:100px"}](https://airfund.io) {: style="height:100px"}](https://www.isomorphiclabs.com) {: style="height:100px"}](https://www.morganstanley.com/) {: style="height:100px"}](https://www.nexenio.com) {: style="height:100px"}](https://www.noon.com/) {: style="height:100px"}](https://phaidra.ai) {: style="height:100px"}](https://www.softwareag.com/) {: style="height:100px"}](https://skyscanner.net/) {: style="height:100px"}](https://www.synthace.com/) {: style="height:100px"}](https://www.ringcentral.com/) {: style="height:100px"}](https://www.ubisoft.com/) {: style="height:100px"}](https://www.vshn.ch) {: style="height:100px"}](https://www.flower.ai) </div>
Project: Cloud Custodian (Provisioning / Automation & Configuration)
File: notes.md

ctx with reporter and selection summary index ~ composition provider tag flow policy from zip / url variable support exit code ref resolution syntax exploration ref resolve function / auto dispatch from value filter graph functions instead of resolver? variable count node provider tags /flow cloud provider resource map ( tf provider to custodian) data sources related filters- default tag flow hosting providers / env policy zip policy zip s3 include / exclude policies list available checks ms templates cfn provider want to be able to execute across multiple policies, auto expland undo lazy loading / resource loading :/ reflexive match as default dict though
Project: KICS (Provisioning / Security & Compliance)
File: 5089d055-53ff-421b-9482-a5267bdce629.md

title: Redis Publicly Accessible hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 5089d055-53ff-421b-9482-a5267bdce629 Query name: Redis Publicly Accessible Platform: Terraform Severity: <span style="color:#ff0000">Critical</span> Category: Networking and Firewall URL: Firewall rule allowing unrestricted access to Redis from other Azure sources<br> ```tf title="Positive test num. 1 - tf file" hl_lines="22" resource "azurermrediscache" "positive1" { name = "redis${random_id.server.hex}" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name capacity = 1 family = "P" sku_name = "Premium" enablenonssl_port = false redis_configuration { maxclients = 256 maxmemory_reserved = 2 maxmemory_delta = 2 maxmemory_policy = "allkeys-lru" } } resource "azurermredisfirewall_rule" "positive2" { name = "someIPrange" rediscachename = azurermrediscache.example.name resourcegroupname = azurermresourcegroup.example.name start_ip = "1.2.3.4" end_ip = "2.3.4.5" } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermrediscache" "negative1" { name = "redis${random_id.server.hex}" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name capacity = 1 family = "P" sku_name = "Premium" enablenonssl_port = false redis_configuration { maxclients = 256 maxmemory_reserved = 2 maxmemory_delta = 2 maxmemory_policy = "allkeys-lru" } } resource "azurermredisfirewall_rule" "negative2" { name = "someIPrange" rediscachename = azurermrediscache.example.name resourcegroupname = azurermresourcegroup.example.name start_ip = "10.2.3.4" end_ip = "10.3.4.5" } ```
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: replace.md

Replace transform plugin Examines string value in a given field and replaces substring of the string value that matches the given string literal or regexes with the given replacement. | name | type | required | default value | |||-|| | replace_field | string | yes | | | pattern | string | yes | - | | replacement | string | yes | - | | is_regex | boolean | no | false | | replace_first | boolean | no | false | The field you want to replace The old string that will be replaced The new string for replace Use regex for string match Whether replace the first match string. Only used when `is_regex = true`. Transform plugin common parameters, please refer to for details The data read from source is a table like this: | name | age | card | |-|--|| | Joy Ding | 20 | 123 | | May Ding | 20 | 123 | | Kin Dom | 20 | 123 | | Joy Dom | 20 | 123 | We want to replace the char ` ` to `_` at the `name` field. Then we can add a `Replace` Transform like this: ``` transform { Replace { sourcetablename = "fake" resulttablename = "fake1" replace_field = "name" pattern = " " replacement = "_" is_regex = true } } ``` Then the data in result table `fake1` will update to | name | age | card | |-|--|| | Joy_Ding | 20 | 123 | | May_Ding | 20 | 123 | | Kin_Dom | 20 | 123 | | Joy_Dom | 20 | 123 | ``` env { job.mode = "BATCH" } source { FakeSource { resulttablename = "fake" row.num = 100 schema = { fields { id = "int" name = "string" } } } } transform { Replace { sourcetablename = "fake" resulttablename = "fake1" replace_field = "name" pattern = ".+" replacement = "b" is_regex = true } } sink { Console { sourcetablename = "fake1" } } ``` Add Replace Transform Connector
Project: KICS (Provisioning / Security & Compliance)
File: b72d0026-f649-4c91-a9ea-15d8f681ac09.md

title: Stack Notifications Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b72d0026-f649-4c91-a9ea-15d8f681ac09 Query name: Stack Notifications Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: AWS CloudFormation should have stack notifications enabled to be notified when an event occurs<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awscloudformationstack" "positive1" { name = "networking-stack" parameters = { VPCCidr = "10.0.0.0/16" } } ``` ```tf title="Negative test num. 1 - tf file" resource "awscloudformationstack" "negative1" { name = "networking-stack" parameters = { VPCCidr = "10.0.0.0/16" } notification_arns = ["a","b"] } ```
Project: KubeMQ (App Definition and Development / Streaming & Messaging)
File: kubemq_queues_peek.md

Queues peek a messages from a queue channel command Queues peek command allows to peek one or many messages from a queue channel without removing them from the queue ``` kubemq queues peek [flags] ``` ``` kubemq queue peek some-channel kubemq queue peek some-channel -m 3 -w 5 ``` ``` -h, --help help for peek -m, --messages int set how many messages we want to peek from queue (default 1) -w, --wait int set how many seconds to wait for peeking queue messages (default 2) ``` - Execute Kubemq 'queues' commands
Project: KICS (Provisioning / Security & Compliance)
File: d0cc8694-fcad-43ff-ac86-32331d7e867f.md

title: S3 Bucket Allows Public ACL hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d0cc8694-fcad-43ff-ac86-32331d7e867f Query name: S3 Bucket Allows Public ACL Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: S3 bucket allows public ACL<br> ```tf title="Positive test num. 1 - tf file" hl_lines="8 18" resource "awss3bucket" "positive1" { bucket = "example" } resource "awss3bucketpublicaccess_block" "positive2" { bucket = awss3bucket.example.id blockpublicacls = false blockpublicpolicy = true ignorepublicacls = false } // comment // comment // comment // comment // comment resource "awss3bucketpublicaccess_block" "positive3" { bucket = awss3bucket.example.id blockpublicpolicy = true ignorepublicacls = false } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="8" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" restrictpublicbuckets = true blockpublicacls = false versioning = { enabled = true } policy = <<POLICY { "Version": "2012-10-17", "Id": "MYBUCKETPOLICY", "Statement": [ { "Sid": "IPAllow", "Effect": "Deny", "Action": "s3:*", "Resource": "arn:aws:s3:::mytftest_bucket/*", "Condition": { "IpAddress": {"aws:SourceIp": "8.8.8.8/32"} } } ] } POLICY } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="1" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" restrictpublicbuckets = true versioning = { enabled = true } policy = <<POLICY { "Version": "2012-10-17", "Id": "MYBUCKETPOLICY", "Statement": [ { "Sid": "IPAllow", "Effect": "Deny", "Action": "s3:*", "Resource": "arn:aws:s3:::mytftest_bucket/*", "Condition": { "IpAddress": {"aws:SourceIp": "8.8.8.8/32"} } } ] } POLICY } ``` ```tf title="Negative test num. 1 - tf file" resource "awss3bucket" "negative1" { bucket = "example" } resource "awss3bucketpublicaccess_block" "negative2" { bucket = awss3bucket.example.id blockpublicacls = true blockpublicpolicy = true ignorepublicacls = false } ``` ```tf title="Negative test num. 2 - tf file" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" restrictpublicbuckets = true blockpublicacls = true versioning = { enabled = true } policy = <<POLICY { "Version": "2012-10-17", "Id": "MYBUCKETPOLICY", "Statement": [ { "Sid": "IPAllow", "Effect": "Deny", "Action": "s3:*", "Resource": "arn:aws:s3:::mytftest_bucket/*", "Condition": { "IpAddress": {"aws:SourceIp": "8.8.8.8/32"} } } ] } POLICY } ```
Project: KICS (Provisioning / Security & Compliance)
File: common-queries.md

This page contains all queries from Common. | Query |Severity|Category|More info| ||--|--|--| |Passwords And Secrets<br/><sup><sub>a88baa34-e2ad-44ea-ad6f-8cac87bc7c71</sub></sup>|<span style="color:#bb2124">High</span>|Secret Management|<a href="../common-queries/a88baa34-e2ad-44ea-ad6f-8cac87bc7c71" target="_blank">Query details</a><br><a href="https://docs.kics.io/latest/secrets/">Documentation</a><br/>|
Project: DragonflyDB (App Definition and Development / Database)
File: differences.md

String sizes are limited to 256MB. Indices (say in GETRANGE and SETRANGE commands) should be signed 32 bit integers in range [-2147483647, 2147483648]. SORT does not take any locale into account. Expirations are limited to 8 years. For commands with millisecond precision like PEXPIRE or PSETEX, expirations greater than 2^28ms are quietly rounded to the nearest second losing precision of less than 0.001%. We use lua 5.4.4 that has been released in 2022. That means we also support .
Project: Beam (App Definition and Development / Streaming & Messaging)
File: deepmind.md

title: "DeepMind" icon: /images/logos/powered-by/deepmind.png hasLink: "https://www.deepmind.com/" <!-- 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: Beam (App Definition and Development / Streaming & Messaging)
File: 20_io_biguery.md

Prompt: Is BigQuery supported in Apache Beam? Response: Yes, Apache Beam supports BigQuery. is a serverless and cost-effective enterprise data warehouse offered by . Apache Beam provides a BigQueryIO connector to read and write data from and to BigQuery. The BigQueryIO connector supports both batch and streaming pipelines. The following Apache Beam SDKs support the BigQueryIO connector: (native and through ) (through X Language) To read data from BigQuery, use the `ReadFromBigQuery` function. Apache Beam can read data directly from a BigQuery table or using an SQL query. The default mode is to return table rows read from a BigQuery source as dictionaries. Built-in `TableRow` objects can also be returned. Here is an example of Apache Beam pipeline code for reading from BigQuery: ```python from apache_beam.io.gcp.bigquery import ReadFromBigQuery with beam.Pipeline(options=options) as p: lines_table = p | 'Read' >> ReadFromBigQuery(table=table) lines_query = p | 'Read' >> ReadFromBigQuery(query="SELECT * FROM table") ``` Here is an example of Apache Beam pipeline code for writing to BigQuery: ```python from apache_beam.io.gcp.bigquery import WriteToBigQuery with beam.Pipeline(options=options) as p: p | 'Write' >> beam.io.WriteToBigQuery( table, schema=TABLE_SCHEMA, createdisposition=beam.io.BigQueryDisposition.CREATEIF_NEEDED, writedisposition=beam.io.BigQueryDisposition.WRITEAPPEND) ``` To get started with BigQuery and Apache Beam, see the examples in the GitHub repository. For Python read examples, see the example. For Python write examples, see the example.
Project: ArangoDB (App Definition and Development / Database)
File: result_operator_in.md

+++ title = "`std::istream &operator>>(std::istream &, basic_result<T, E, NoValuePolicy> &)`" description = "Deserialises a `basic_result` from a `std::istream`." +++ Deserialises a `basic_result` from a `std::istream`. Serialisation format is: ``` <unsigned int flags><space><valuetype if set and not void><errortype if set and not void> ``` Overridable: Not overridable. Requires: That `operator>>` is a valid expression for `std::istream` and `T` and `E`. Namespace: `BOOSTOUTCOMEV2_NAMESPACE` Header: `<boost/outcome/iostream_support.hpp>` (must be explicitly included manually).
Project: YugabyteDB (App Definition and Development / Database)
File: comment_on.grammar.md

```output.ebnf comment_on ::= COMMENT ON { ACCESS METHOD accessmethodname | AGGREGATE aggregatename ( aggregatesignature ) | CAST ( sourcetype AS targettype ) | COLLATION object_name | COLUMN relationname . columnname | CONSTRAINT constraintname ON tablename | CONSTRAINT constraintname ON DOMAIN domainname | CONVERSION object_name | DATABASE object_name | DOMAIN object_name | EXTENSION object_name | EVENT TRIGGER object_name | FOREIGN DATA WRAPPER object_name | FOREIGN TABLE object_name | FUNCTION subprogramname ( [ subprogramsignature ] ) | INDEX object_name | LARGE OBJECT largeobjectoid | MATERIALIZED VIEW object_name | OPERATOR operatorname ( operatorsignature ) | OPERATOR CLASS objectname USING indexmethod | OPERATOR FAMILY objectname USING indexmethod | POLICY policyname ON tablename | [ PROCEDURAL ] LANGUAGE object_name | PROCEDURE subprogram_name ( [ subprogram_signature ] ) | PUBLICATION object_name | ROLE object_name | ROUTINE subprogramname ( [ subprogramsignature ] ) | RULE rulename ON tablename | SCHEMA object_name | SEQUENCE object_name | SERVER object_name | STATISTICS object_name | SUBSCRIPTION object_name | TABLE object_name | TABLESPACE object_name | TEXT SEARCH CONFIGURATION object_name | TEXT SEARCH DICTIONARY object_name | TEXT SEARCH PARSER object_name | TEXT SEARCH TEMPLATE object_name | TRIGGER triggername ON tablename | TYPE object_name | VIEW object_name } IS { '<Text Literal>' | NULL } ```
Project: KICS (Provisioning / Security & Compliance)
File: 42f4b905-3736-4213-bfe9-c0660518cda8.md

title: EKS Cluster Has Public Access hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 42f4b905-3736-4213-bfe9-c0660518cda8 Query name: EKS Cluster Has Public Access Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Amazon EKS public endpoint shoud be set to false<br> ```tf title="Positive test num. 1 - tf file" hl_lines="7" resource "awsekscluster" "positive1" { name = "example" rolearn = awsiam_role.example.arn vpc_config { subnetids = [awssubnet.example1.id, aws_subnet.example2.id] endpointpublicaccess = true } depends_on = [ awsiamrolepolicyattachment.example-AmazonEKSClusterPolicy, ] } output "endpoint" { value = awsekscluster.example.endpoint } output "kubeconfig-certificate-authority-data" { value = awsekscluster.example.certificate_authority[0].data } ``` ```tf title="Negative test num. 1 - tf file" resource "awsekscluster" "negative1" { name = "example" rolearn = awsiam_role.example.arn vpc_config { subnetids = [awssubnet.example1.id, aws_subnet.example2.id] endpointpublicaccess = false } depends_on = [ awsiamrolepolicyattachment.example-AmazonEKSClusterPolicy, ] } output "endpoint" { value = awsekscluster.example.endpoint } output "kubeconfig-certificate-authority-data" { value = awsekscluster.example.certificate_authority[0].data } ```
Project: secureCodeBox (Provisioning / Security & Compliance)
File: index.md

title: "Testing Concept" sidebar_label: "Introduction" sidebar_position: 1 To ensure the functionality of our project, we make use of automated tests in our Continuous Integration (CI) pipeline. This allows us to have feedback on whether newly implemented and old functionalities are operating correctly. It's also important that this feedback is fast to not delay our operations. That is why, a good balance between unit tests and integration tests has to be struck. For that, we refer to the Martin Fowler that presents the fundamentals on creating a good testing pyramid. In a testing pyramid, tests that require more CPU time are at the top of the pyramid and are few. The opposite happens the lower you go in the pyramid. This is the testing pyramid for the SecureCodeBox: We have unit tests for the different SCB modules (e.g. Operator, Hook, Scanner ...). These tests are meant to be fast. For our integration test, we run a complete SCB scan in a Kind Cluster and we evaluate the resulted findings. The following articles describe how each module implements its unit and integration tests: We use Make as a basis for our testing framework. The Makefiles expect additional software to be installed: git, node + npm, docker, kind, kubectl, helm and .