cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 1d6e16f1-5d8a-4379-bfb3-2dadd38ed5a7.md

title: Lambda Permission Principal Is Wildcard hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 1d6e16f1-5d8a-4379-bfb3-2dadd38ed5a7 Query name: Lambda Permission Principal Is Wildcard Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Lambda Permission Principal should not contain a wildcard.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="9" AWSTemplateFormatVersion: "2010-09-09" Description: Creates RDS Cluster Resources: s3Permission: Type: AWS::Lambda::Permission Properties: FunctionName: !GetAtt function.Arn Action: lambda:InvokeFunction Principal: '*' SourceAccount: !Ref 'AWS::AccountId' SourceArn: !GetAtt bucket.Arn ``` ```json title="Positive test num. 2 - json file" hl_lines="10" { "Resources": { "s3Permission": { "Type": "AWS::Lambda::Permission", "Properties": { "SourceAccount": "AWS::AccountId", "SourceArn": "bucket.Arn", "FunctionName": "function.Arn", "Action": "lambda:InvokeFunction", "Principal": "*" } } }, "AWSTemplateFormatVersion": "2010-09-09", "Description": "Creates RDS Cluster" } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: "2010-09-09" Description: Creates RDS Cluster Resources: s3Permission: Type: AWS::Lambda::Permission Properties: FunctionName: !GetAtt function.Arn Action: lambda:InvokeFunction Principal: s3.amazonaws.com SourceAccount: !Ref 'AWS::AccountId' SourceArn: !GetAtt bucket.Arn ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Description": "Creates RDS Cluster", "Resources": { "s3Permission": { "Type": "AWS::Lambda::Permission", "Properties": { "FunctionName": "function.Arn", "Action": "lambda:InvokeFunction", "Principal": "s3.amazonaws.com", "SourceAccount": "AWS::AccountId", "SourceArn": "bucket.Arn" } } } } ```
Project: ShardingSphere (App Definition and Development / Database)
File: show-traffic-rule.en.md

+++ title = "SHOW TRAFFIC RULE" weight = 6 +++ The `SHOW TRAFFIC RULE` syntax is used to query specified dual routing rule. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowTrafficRule ::= 'SHOW' 'TRAFFIC' ('RULES' | 'RULE' ruleName)? ruleName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When `ruleName` not specified, the default is show all traffic rules | Column | Description | ||| | name | traffic rule name | | labels | compute node labels | | algorithm_type | traffic algorithm type | | algorithm_props | traffic algorithn properties | | loadbalancertype | load balancer type | | loadbalancerprops | load balancer properties | Query specified traffic rule ```sql SHOW TRAFFIC RULE sqlmatchtraffic; ``` ```sql mysql> SHOW TRAFFIC RULE sqlmatchtraffic; +-+--+-+--+--++ | name | labels | algorithmtype | algorithmprops | loadbalancertype | loadbalancerprops | +-+--+-+--+--++ | sqlmatchtraffic | OLTP | SQLMATCH | sql=SELECT * FROM torder WHERE orderid = 1; UPDATE torder SET order_id = 5; | RANDOM | | +-+--+-+--+--++ 1 row in set (0.00 sec) ``` Query all traffic rules ```sql SHOW TRAFFIC RULES; ``` ```sql mysql> SHOW TRAFFIC RULES; +-+--+-+--+--++ | name | labels | algorithmtype | algorithmprops | loadbalancertype | loadbalancerprops | +-+--+-+--+--++ | sqlmatchtraffic | OLTP | SQLMATCH | sql=SELECT * FROM torder WHERE orderid = 1; UPDATE torder SET order_id = 5; | RANDOM | | +-+--+-+--+--++ 1 row in set (0.04 sec) ``` `SHOW`, `TRAFFIC`, `RULE`, `RULES`
Project: CloudARK KubePlus (App Definition and Development / Application Definition & Image Build)
File: MAINTAINERS.md

KubePlus Maintainers ===================== You can become a KubePlus maintainer once you demonstrate sufficient understanding of the project and the code base. Best way to achieve maintainer status is to work on some aspects of KubePlus and get your PRs merged in the master branch. Current list of Maintainers Devdatta Kulkarni
Project: Druid (App Definition and Development / Database)
File: single-server.md

id: single-server title: "Single server deployment" <!-- ~ 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. --> Druid includes a launch script, `bin/start-druid` that automatically sets various memory-related parameters based on available processors and memory. It accepts optional arguments such as list of services, total memory, and a config directory to override default JVM arguments and service-specific runtime properties. By default, the services started by `bin/start-druid`: use all processors can use up to 80% memory on the system apply the configuration files in `conf/druid/auto` for all other settings. For details about possible arguments, run `bin/start-druid --help`. Druid includes a set of reference configurations and launch scripts for single-machine deployments. These start scripts are deprecated in favor of the `bin/start-druid` script documented above. These configuration bundles are located in `conf/druid/single-server/`. | Configuration |Sizing|Launch command|Configuration directory| |--|--|-|| | `nano-quickstart` |1 CPU, 4GiB RAM|`bin/start-nano-quickstart`|`conf/druid/single-server/nano-quickstart`| | `micro-quickstart` |4 CPU, 16GiB RAM|`bin/start-micro-quickstart`|`conf/druid/single-server/micro-quickstart`| | `small` |8 CPU, 64GiB RAM (~i3.2xlarge)|`bin/start-small`|`conf/druid/single-server/small`| | `medium` |16 CPU, 128GiB RAM (~i3.4xlarge)|`bin/start-medium`|`conf/druid/single-server/medium`| | `large` |32 CPU, 256GiB RAM (~i3.8xlarge)|`bin/start-large`|`conf/druid/single-server/large`| | `xlarge` |64 CPU, 512GiB RAM (~i3.16xlarge)|`bin/start-xlarge`|`conf/druid/single-server/xlarge`| The `micro-quickstart` is sized for small machines like laptops and is intended for quick evaluation use-cases. The `nano-quickstart` is an even smaller configuration, targeting a machine with 1 CPU and 4GiB memory. It is meant for limited evaluations in resource constrained environments, such as small Docker containers. The other configurations are intended for general use single-machine deployments. They are sized for hardware roughly based on Amazon's i3 series of EC2 instances. The startup scripts for these example configurations run a single ZK instance along with the Druid services. You can choose to deploy ZK separately as well.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.2.1.en.md

The bcrypt work factor is limited to the range 5-10, because higher values consume too much CPU resources. Bcrypt library is updated to allow parallel hash evaluation. Improve some error reasons when parsing invalid packets. Added support for defining templates for MQTT 5.0 publish properties and user properties in Republish rule action. Examples and documentation for /api/v5/publish bad request response have been fixed. Previously the documentation example said that the bad request response could return a list in the body which was not actually the case. Upgrade Erlang/OTP to 25.3.2-2 Erlang/OTP 25.3.2-2 excludes sensitive data from mnesia_hook log message. Don't download a trace log file if it is empty. After this fix, GET `/api/v5/trace/clientempty/download` returns 404 `{"code":"NOT_FOUND","message":"Trace is empty"}` If no events matching the trace condition occurred. Improved error message for rule engine schema registry when schema name exceeds permissible length. Fixed issue where authorization cache cleaning cli was not working properly for specific client ID. Fix cluster partition autoheal functionality. Implement autohealing for the clusters that split into multiple partitions. Fixed an issue where an ill-defined built-in rule action config could be interpreted as a custom user function. Fixed an issue where the core node could get stuck in the `mria_schema:bootstrap/0` state, preventing new nodes from joining the cluster.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: fix-12657.en.md

The rule engine SQL-based language previously did not allow putting any expressions as array elements in array literals (only constants and variable references were allowed). This has now been fixed so that one can use any expressions as array elements. The following is now permitted, for example: ``` select [21 + 21, abs(-abs(-2)), [1 + 1], 4] as my_array from "t/#" ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_global_forwarding_rules.md

+++ title = "googlecomputeglobalforwardingrules resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputeglobalforwardingrules" identifier = "inspec/resources/gcp/googlecomputeglobalforwardingrules.md googlecomputeglobalforwardingrules resource" parent = "inspec/resources/gcp" +++ A `googlecomputeglobalforwardingrules` is used to test a Google GlobalForwardingRule resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputeglobalforwardingrules(project: 'chef-gcp-inspec') do its('count') { should be >= 1 } its('port_ranges') { should include '80-80' } end ``` Properties that can be accessed from the `googlecomputeglobalforwardingrules` resource: See the resource for more information. `creation_timestamps` : an array of `googlecomputeglobalforwardingrule` creation_timestamp `descriptions` : an array of `googlecomputeglobalforwardingrule` description `ids` : an array of `googlecomputeglobalforwardingrule` id `ip_addresses` : an array of `googlecomputeglobalforwardingrule` ip_address `ip_protocols` : an array of `googlecomputeglobalforwardingrule` ip_protocol `ip_versions` : an array of `googlecomputeglobalforwardingrule` ip_version `labels` : (Beta only) an array of `googlecomputeglobalforwardingrule` labels `label_fingerprints` : (Beta only) an array of `googlecomputeglobalforwardingrule` label_fingerprint `loadbalancingschemes` : an array of `googlecomputeglobalforwardingrule` loadbalancingscheme `metadata_filters` : an array of `googlecomputeglobalforwardingrule` metadata_filters `names` : an array of `googlecomputeglobalforwardingrule` name `networks` : an array of `googlecomputeglobalforwardingrule` network `port_ranges` : an array of `googlecomputeglobalforwardingrule` port_range `targets` : an array of `googlecomputeglobalforwardingrule` target This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: Meshery (Provisioning / Automation & Configuration)
File: linkerd-past-results.md

layout: past-results-layout title: Meshery-Linkerd Past Results permalink: installation/compatibility-matrix/meshery-linkerd-past-results abstract: a complete compatibility matrix and project test status dashboard. language: en display-title: "false" list: exclude type: "project" service-mesh: "meshery-linkerd" subheading: Meshery-Linkerd
Project: Devfile (App Definition and Development / Application Definition & Image Build)
File: RELEASE.md

The `yaml` Project is released on an as-needed basis. The process is as follows: An issue is proposing a new release with a changelog since the last release All must LGTM this release An OWNER runs `git tag -s $VERSION` and inserts the changelog and pushes the tag with `git push $VERSION` The release issue is closed An announcement email is sent to `kubernetes-dev@googlegroups.com` with the subject `[ANNOUNCE] kubernetes-template-project $VERSION is released`
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: GoogleFirestore.md

Google Firestore sink connector Write data to Google Firestore | name | type | required | default value | |-|--|-|| | project_id | string | yes | - | | collection | string | yes | - | | credentials | string | no | - | The unique identifier for a Google Firestore database project. The collection of Google Firestore. The credentials of Google Cloud service account, use base64 codec. If not set, need to check the `GOOGLE APPLICATION CREDENTIALS` environment exists. Sink plugin common parameters, please refer to for details. ```bash GoogleFirestore { project_id = "dummy-project-id", collection = "dummy-collection", credentials = "dummy-credentials" } ``` Add Google Firestore Sink Connector
Project: KICS (Provisioning / Security & Compliance)
File: c757c6a3-ac87-4b9d-b28d-e5a5add6a315.md

title: Serverless API X-Ray Tracing Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c757c6a3-ac87-4b9d-b28d-e5a5add6a315 Query name: Serverless API X-Ray Tracing Disabled Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: AWS Serverless API should have X-Ray Tracing enabled<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" AWSTemplateFormatVersion: '2010-09-09' Transform: AWS::Serverless-2016-10-31 Description: AWS SAM template with a simple API definition Resources: ApiGatewayApi: Type: AWS::Serverless::Api Properties: StageName: prod ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="9" AWSTemplateFormatVersion: '2010-09-09' Transform: AWS::Serverless-2016-10-31 Description: AWS SAM template with a simple API definition Resources: ApiGatewayApi2: Type: AWS::Serverless::Api Properties: StageName: prod TracingEnabled: false ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: '2010-09-09' Transform: AWS::Serverless-2016-10-31 Description: AWS SAM template with a simple API definition Resources: ApiGatewayApi3: Type: AWS::Serverless::Api Properties: StageName: prod TracingEnabled: true ```
Project: YugabyteDB (App Definition and Development / Database)
File: 07-in.md

title: "IN" In this exercise we will query the shippers table and return only the rows that have a shipper\id_ of 1, 2, 3 or 4. ``` SELECT * FROM shippers WHERE shipper_id IN (1,2,3,4); ``` This query should return 4 rows In this exercise we will query the shippers table and return all the rows, except those that have a shipper\id_ of 3 or 4. ``` SELECT * FROM shippers WHERE shipper_id NOT IN (3,4); ``` This query should return 4 rows In this exercise we will query the orders table and return all the rows using a subquery to find all the orders who have an order\date_ of 1998-05-06. ``` SELECT customer_id FROM orders WHERE CAST (order_date AS DATE) = '1998-05-06'; ``` This query should return 4 rows
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: CHANGELOG-v2021.11.24.md

title: Changelog | KubeDB description: Changelog menu: docs_{{.version}}: identifier: changelog-kubedb-v2021.11.24 name: Changelog-v2021.11.24 parent: welcome weight: 20211124 product_name: kubedb menuname: docs{{.version}} sectionmenuid: welcome url: /docs/{{.version}}/welcome/changelog-v2021.11.24/ aliases: /docs/{{.version}}/CHANGELOG-v2021.11.24/ Fix UI crd schema Fix UI type pluralization Generate crd yamls for UI types (#823) Remove unused ui apis (#822) Update dependencies Add UI api types (#821) Add helper function to filter database pods (#820) Prepare for release v0.9.0 (#55) Fix SiteInfo publishing (#54) Update dependencies (#53) Prepare for release v0.24.0 (#643) Update dependencies (#642) Prepare for release v0.24.0 (#544) Provide node roles to config-merger init-container (#542) Fix SiteInfo publishing (#543) Add support for SearchGuard 7.14 (#534) Update dependencies (#541) Prepare for release v0.11.0 (#254) Fix SiteInfo publishing (#253) Update dependencies (#252) Prepare for release v2021.11.24 (#403) Update repository config (#402) Add support for SearchGuard 7.14.2 (#383) Update dependencies (#401) Update kubedb-opscenter chart dependencies via make file Add kubedb-opscenter chart (#400) Update ui-server chart Don't import UI crds (#399) Fix permissions for the ui-server chart Grant permission to watch rbac resources (#398) Add kubedb-ui-server chart (#396) Prepare for release v0.8.0 (#115) Fix SiteInfo publishing (#114) Update dependencies (#113) Prepare for release v0.4.0 (#27) Fix SiteInfo publishing (#26) Update dependencies (#25) Prepare for release v0.17.0 (#330) Fix SiteInfo publishing (#329) Update dependencies (#328) Prepare for release v0.17.0 (#440) Fix SiteInfo publishing (#439) Update dependencies (#438) Prepare for release v0.17.0 (#435) Fix SiteInfo publishing (#434) Update dependencies (#433) Fix MySQL app binding URL (#432) Update health checker to use only the database pods (#431) Ensure health checker uses only the database pods (#430) Prepare for release v0.2.0 (#21) Fix SiteInfo publishing (#20) Update dependencies (#19) Prepare for release v0.24.0 (#438) Fix SiteInfo publishing (#437) Update dependencies (#436) Prepare for release v0.11.0 (#233) Fix SiteInfo publishing (#232) Update dependencies (#231) Prepare for release v0.8.0 (#57) Update dependencies (#56) Check if pods are controlled by kubedb statefulset (#55) Prepare for release v0.11.0 (#193) Fix SiteInfo publishing (#192) Update dependencies (#191) Prepare for release v0.24.0 (#544) Fix SiteInfo publishing (#543) Update dependencies (#542) Ensure health checker uses only the database pods (#541) Prepare for release v0.11.0 (#210) Fix SiteInfo publishing (#209) Update dependencies (#208) Prepare for release v0.17.0 (#366) Fix SiteInfo publishing (#365) Update dependencies (#364) Prepare for release v0.3.0 (#16) Fix SiteInfo publishing (#15) Update dependencies (#14) Prepare for release v0.11.0 (#177) Update dependencies (#176) Prepare for release v0.9.0 (#158) Update dependencies (#157)
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_onprem.md

Manage a YugabyteDB Anywhere on-premises provider Create and manage an on-premises provider, instance types and node instances in YugabyteDB Anywhere. ``` yba provider onprem [flags] ``` ``` -n, --name string [Optional] The name of the provider for the action. Required for create, delete, describe, instance-types and nodes. -h, --help help for onprem ``` ``` -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 On-premises YugabyteDB Anywhere provider - Delete an On-premises YugabyteDB Anywhere provider - Describe an On-premises YugabyteDB Anywhere provider - Manage YugabyteDB Anywhere onprem instance types - List On-premises YugabyteDB Anywhere providers - Manage YugabyteDB Anywhere onprem node instances - Update an On-premises YugabyteDB Anywhere provider
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_logging_project_sink.md

+++ title = "googleloggingproject_sink resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleloggingproject_sink" identifier = "inspec/resources/gcp/googleloggingprojectsink.md googleloggingprojectsink resource" parent = "inspec/resources/gcp" +++ A `googleloggingproject_sink` is used to test a Google ProjectSink resource ```ruby describe googleloggingproject_sink(project: 'chef-gcp-inspec', name: 'inspec-gcp-org-sink') do it { should exist } its('filter') { should cmp 'resource.type = gce_instance AND severity = DEBUG' } end describe googleloggingproject_sink(project: 'chef-gcp-inspec', name: 'nonexistent') do it { should_not exist } end ``` describe googleloggingproject_sink(project: 'chef-inspec-gcp', sink: 'sink-name-abcd') do its('destination') { should eq 'storage.googleapis.com/gcp-inspec-logging-bucket' } end describe googleloggingproject_sink(project: 'chef-inspec-gcp', sink: 'sink-name-abcd') do its('filter') { should eq "resource.type = gceinstance AND resource.labels.instanceid = \"12345678910123123\"" } end describe googleloggingproject_sink(project: 'chef-inspec-gcp', sink: 'sink-name-abcd') do its('outputversionformat') { should eq "V2" } end describe googleloggingproject_sink(project: 'chef-inspec-gcp', sink: 'sink-name-abcd') do its('writer_identity') { should eq "serviceAccount:my-logging-service-account.iam.gserviceaccount.com" } end Properties that can be accessed from the `googleloggingproject_sink` resource: `project` : Id of the project that this sink belongs to. `name` : Name of the log sink. `filter` : An advanced logs filter. The only exported log entries are those that are in the resource owning the sink and that match the filter. `destination` : The export destination. `writer_identity` : An IAM identitya service account or groupunder which Logging writes the exported log entries to the sink's destination. This field is set by sinks.create and sinks.update based on the value of uniqueWriterIdentity in those methods. `include_children` : If the field is false, the default, only the logs owned by the sink's parent resource are available for export. If the field is true, then logs from all the projects, folders, and billing accounts contained in the sink's parent resource are also available for export. Whether a particular log entry from the children is exported depends on the sink's filter expression. Ensure the is enabled for the current project.
Project: YugabyteDB (App Definition and Development / Database)
File: savepoint_create.md

title: SAVEPOINT statement [YSQL] headerTitle: SAVEPOINT linkTitle: SAVEPOINT description: Use the `SAVEPOINT` statement to start a subtransaction within the current transaction. menu: v2.18: identifier: savepoint_create parent: statements type: docs Use the `SAVEPOINT` statement to define a new savepoint within the current transaction. A savepoint is a special "checkpoint" inside a transaction that allows all commands that are executed after it was established to be rolled back, restoring the transaction state to what it was at the time of the savepoint. {{%ebnf%}} savepoint_create {{%/ebnf%}} ```plpgsql SAVEPOINT name ``` The name of your savepoint. Create a sample table. ```plpgsql CREATE TABLE sample(k int PRIMARY KEY, v int); ``` Begin a transaction and insert some rows. ```plpgsql BEGIN TRANSACTION; INSERT INTO sample(k, v) VALUES (1, 2); SAVEPOINT test; INSERT INTO sample(k, v) VALUES (3, 4); ``` Now, check the rows in this table: ```plpgsql SELECT * FROM sample; ``` ```output k | v -+- 1 | 2 3 | 4 (2 rows) ``` And then, rollback to savepoint `test` and check the rows again. Note that the second row does not appear: ```plpgsql ROLLBACK TO test; SELECT * FROM sample; ``` ```output k | v -+- 1 | 2 (1 row) ``` We can even add a new row at this point. If we then commit the transaction, only the first and third row inserted will persist: ```plpgsql INSERT INTO sample(k, v) VALUES (5, 6); COMMIT; SELECT * FROM SAMPLE; ``` ```output k | v -+- 1 | 2 5 | 6 (2 rows) ```