cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: e4f54ff4-d352-40e8-a096-5141073c37a2.md

title: CDN Configuration Is Missing hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e4f54ff4-d352-40e8-a096-5141073c37a2 Query name: CDN Configuration Is Missing Platform: CloudFormation Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: Content Delivery Network (CDN) service is used within an AWS account to secure and accelerate the delivery of websites. The use of a CDN can provide a layer of security between your origin content and the destination.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="6 7" AWSTemplateFormatVersion: '2010-09-09' Resources: myDistribution: Type: 'AWS::CloudFront::Distribution' Properties: DistributionConfig: Enabled: 'false' Comment: Somecomment DefaultRootObject: index.html Logging: IncludeCookies: 'true' Bucket: mylogs.s3.amazonaws.com Prefix: myprefix ``` ```json title="Positive test num. 2 - json file" hl_lines="15 7" { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "myDistribution": { "Type": "AWS::CloudFront::Distribution", "Properties": { "DistributionConfig": { "Comment": "Somecomment", "DefaultRootObject": "index.html", "Logging": { "IncludeCookies": "true", "Bucket": "mylogs.s3.amazonaws.com", "Prefix": "myprefix" }, "Enabled": "false" } } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: '2010-09-09' Resources: myDistribution: Type: 'AWS::CloudFront::Distribution' Properties: DistributionConfig: Origins: DomainName: www.example.com Id: myCustomOrigin CustomOriginConfig: HTTPPort: '80' HTTPSPort: '443' OriginProtocolPolicy: http-only Enabled: 'true' Comment: Somecomment DefaultRootObject: index.html Logging: IncludeCookies: 'true' Bucket: mylogs.s3.amazonaws.com Prefix: myprefix ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "myDistribution": { "Type": "AWS::CloudFront::Distribution", "Properties": { "DistributionConfig": { "Enabled": "true", "Comment": "Somecomment", "DefaultRootObject": "index.html", "Logging": { "IncludeCookies": "true", "Bucket": "mylogs.s3.amazonaws.com", "Prefix": "myprefix" }, "Origins": [ { "DomainName": "www.example.com", "Id": "myCustomOrigin", "CustomOriginConfig": { "OriginProtocolPolicy": "http-only", "HTTPPort": "80", "HTTPSPort": "443" } } ] } } } } } ```
Project: DevStream (Provisioning / Automation & Configuration)
File: pull_request_template.md

Note: please complete _ALL_ items in the following checklist. documentation. [ ] My code has the necessary comments and documentation (if needed). [ ] I have added relevant tests <!-- Describe what this PR does and what problems it tries to solve in a few sentences. --> <!-- Will this PR close any open issues? If yes, would you please mention the issue(s) here? --> <!-- Describe the newly updated behavior, if relevant. -->
Project: YugabyteDB (App Definition and Development / Database)
File: yba_task_retry.md

Retry a YugabyteDB Anywhere task Retry a task in YugabyteDB Anywhere ``` yba task retry [flags] ``` ``` --task-uuid string [Required] The task UUID to be retried. -h, --help help for retry ``` ``` -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 tasks
Project: Tetragon (Provisioning / Security & Compliance)
File: options.md

title: "Options" weight: 3 description: "Pass options to hook" It's possible to pass options through spec file as an array of name and value pairs: ```yaml spec: options: name: "option-1" value: "True" name: "option-2" value: "10" ``` Options array is passed and processed by each hook used in the spec file that supports options. At the moment it's availabe for kprobe and uprobe hooks. : options for kprobe hooks. : disable kprobe multi link This option disables kprobe multi link interface for all the kprobes defined in the spec file. If enabled, all the defined kprobes will be atached through standard kprobe interface. It stays enabled for another spec file without this option. It takes boolean as value, by default it's false. Example: ```yaml options: name: "disable-kprobe-multi" value: "1" ``` : options for uprobe hooks. : disable uprobe multi link This option disables uprobe multi link interface for all the uprobes defined in the spec file. If enabled, all the defined uprobes will be atached through standard uprobe interface. It stays enabled for another spec file without this option. It takes boolean as value, by default it's false. Example: ```yaml options: name: "disable-uprobe-multi" value: "1" ```
Project: YugabyteDB (App Definition and Development / Database)
File: begin.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="463" height="85" viewbox="0 0 463 85"><path class="connector" d="M0 37h15m59 0h30m106 0h20m-136 25q0 5 5 5h5m57 0h54q5 0 5-5m-131-25q5 0 5 5v33q0 5 5 5h116q5 0 5-5v-33q0-5 5-5m5 0h50m-5 0q-5 0-5-5v-17q0-5 5-5h138q5 0 5 5v17q0 5-5 5m-5 0h40m-203 0q5 0 5 5v8q0 5 5 5h178q5 0 5-5v-8q0-5 5-5m5 0h15"/><polygon points="0,44 5,37 0,30" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="20" width="59" height="25" rx="7"/><text class="text" x="25" y="37">BEGIN</text><rect class="literal" x="104" y="20" width="106" height="25" rx="7"/><text class="text" x="114" y="37">TRANSACTION</text><rect class="literal" x="104" y="50" width="57" height="25" rx="7"/><text class="text" x="114" y="67">WORK</text><a xlink:href="../../../syntaxresources/grammardiagrams#transaction-mode"><rect class="rule" x="280" y="20" width="128" height="25"/><text class="text" x="290" y="37">transaction_mode</text></a><polygon points="459,44 463,44 463,30 459,30" style="fill:black;stroke-width:0"/></svg>
Project: KOTS (App Definition and Development / Application Definition & Image Build)
File: scheduled-update-check.md

KOTS (Admin Console) does not automatically check for new updates. This proposal adds the ability for KOTS (Admin Console) to check for updates on specific times for online installations. Pull new updates automatically for KOTS (Admin Console) online installations Deployment of the new updates Scheduled Update Checks for Airgap Installations Many customers assume that scheduled update checks are a given and are surprised when they do not receive updates automatically. This proposal is only for online installations in KOTS Admin console. The times on which the update check will happen is configurable by a cron spec. The ability to disable this feature completely. It will be enabled by default. The update check will happen in a background process/thread which is triggered on specific times defined by a cron job spec. On each trigger, the process will get all available applications and run update checks for each app. The update check will automatically create new versions for each update available in an app. A new column `updatecheckerspec` will be added to the `app` table in the postgress database using a migration. The column is a text and defaults to `@daily`, which will indicate that the cron job will run daily at midnight. By default, when the KOTS Admin Console's api starts: The api will read the cron spec value from the database. If the feature is enabled (`!= @never`), start a cron job schedule with the provided spec. Use the same logic from the update check request to check for updates for each application. The update check request logic already creates new versions automatically if there are updates available, and handles the scenario if multiple requests have been made to check for updates. Note: A cron job will also be added when creating a new app. To configure the update checker spec: There will be a "Configure update checker" link in the Admin Console's version history card & page. Upon clicking the link, a small modal will display the value of the cron job spec. The modal will have a "Update" button. Once the user clicks "Update", a request will be made with the new spec to the Admin Console's api. The request will update the spec in the database and reconfigure the cron job. If any of this fails, the request will return a failure message which will be displayed in the modal.
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: multi-partition.md

To achieve higher throughput(> 10K but < 30K tps), users can create multi-partitioned edges. Multi-partitioned edges are only supported for pipelines with JetStream as ISB. Please ensure that the JetStream is provisioned with more nodes to support higher throughput. Since partitions are owned by the vertex reading the data, to create a multi-partitioned edge we need to configure the vertex reading the data (to-vertex) to have multiple partitions. The following code snippet provides an example of how to configure a vertex (in this case, the `cat` vertex) to have multiple partitions, which enables it (`cat` vertex) to read at a higher throughput. ```yaml name: cat partitions: 3 udf: builtin: name: cat # A built-in UDF which simply cats the message ```
Project: KICS (Provisioning / Security & Compliance)
File: 96ed3526-0179-4c73-b1b2-372fde2e0d13.md

title: Default VPC Exists hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 96ed3526-0179-4c73-b1b2-372fde2e0d13 Query name: Default VPC Exists Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Defaults URL: It isn't recommended to use resources in default VPC<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsdefaultvpc" "positive1" { tags = { Name = "Default VPC" } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="14" module "vpc" { source = "terraform-aws-modules/vpc/aws" version = "3.7.0" name = "my-vpc" cidr = "10.0.0.0/16" azs = ["eu-west-1a", "eu-west-1b", "eu-west-1c"] private_subnets = ["10.0.1.0/24", "10.0.2.0/24", "10.0.3.0/24"] public_subnets = ["10.0.101.0/24", "10.0.102.0/24", "10.0.103.0/24"] enablenatgateway = true enablevpngateway = true defaultvpcname = "my-default-vpc" tags = { Terraform = "true" Environment = "dev" } } ``` ```tf title="Negative test num. 1 - tf file" resource "aws_vpc" "negative1" { cidr_block = "10.0.0.0/16" instance_tenancy = "default" tags = { Name = "main" } } ``` ```tf title="Negative test num. 2 - tf file" module "vpc" { source = "terraform-aws-modules/vpc/aws" version = "3.7.0" name = "my-vpc" cidr = "10.0.0.0/16" azs = ["eu-west-1a", "eu-west-1b", "eu-west-1c"] private_subnets = ["10.0.1.0/24", "10.0.2.0/24", "10.0.3.0/24"] public_subnets = ["10.0.101.0/24", "10.0.102.0/24", "10.0.103.0/24"] enablenatgateway = true enablevpngateway = true tags = { Terraform = "true" Environment = "dev" } } ```
Project: KICS (Provisioning / Security & Compliance)
File: 2f56b7ab-7fba-4e93-82f0-247e5ddeb239.md

title: MSK Cluster Logging Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2f56b7ab-7fba-4e93-82f0-247e5ddeb239 Query name: MSK Cluster Logging Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Ensure MSK Cluster Logging is enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="8 5 15" resource "awsmskcluster" "positive1" { logging_info { broker_logs { cloudwatch_logs { enabled = false loggroup = awscloudwatchloggroup.test.name } firehose { deliverystream = awskinesisfirehosedeliverystream.teststream.name } } } } resource "awsmskcluster" "positive2" { } ``` ```tf title="Negative test num. 1 - tf file" resource "awsmskcluster" "negative1" { logging_info { broker_logs { cloudwatch_logs { enabled = true loggroup = awscloudwatchloggroup.test.name } } } } ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: sys_info.md

+++ title = "sys_info resource" draft = false gh_repo = "inspec" platform = "os" [menu] [menu.inspec] title = "sys_info" identifier = "inspec/resources/os/sysinfo.md sysinfo resource" parent = "inspec/resources/os" +++ Use the `sys_info` Chef InSpec audit resource to test for operating system properties for the named host, and then returns that info as standard output. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. An `sys_info` resource block declares the hostname to be tested: describe sys_info do its('hostname') { should eq 'value' } end The `hostname` property tests the host for which standard output is returned: its('hostname') { should eq 'value' } The `fqdn` property tests the 'fully qualified domain name' of the system: its('fqdn') { should eq 'value' } The `domain` property tests the name of the DNS domain: its('domain') { should eq 'value' } The `ip-address` property tests all network addresses of the host: its('ip-address') { should eq 'value' } The `short` property tests the host name cut at the first dot: its('short') { should eq 'value' } The `manufacturer` property tests the host for which standard output is returned: its('manufacturer') { should eq 'ACME Corp.' } The `model` property tests the host for which standard output is returned: its('model') { should eq 'Flux Capacitor' } The following examples show how to use this Chef InSpec audit resource. describe sys_info do its('hostname') { should eq 'example.com' } end describe file('/path/to/some/file') do its('content') { should match sys_info.hostname } end Options can be passed as arguments to hostname as well. describe file('/path/to/some/file') do its('content') { should match sys_info.hostname('full') } end Currently supported arguments to `hostname` on Linux platforms are 'full'|'f'|'fqdn'|'long', 'domain'|'d', 'ip_address'|'i', and 'short'|'s'. Mac currently supports 'full'|'f'|'fqdn'|'long' and 'short'|'s' {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: Salt Project (Provisioning / Automation & Configuration)
File: 3006.4.md

(release-3006.4)= <! Do not edit this file. This is auto generated. Edit the templates in doc/topics/releases/templates/ for a given release. --> <!-- Add release specific details below --> <!-- Do not edit the changelog below. This is auto generated. --> Fix CVE-2023-34049 by ensuring we do not use a predictable name for the script and correctly check returncode of scp command. This only impacts salt-ssh users using the pre-flight option. Update to `gitpython>=3.1.35` due to https://github.com/advisories/GHSA-wfm5-v35h-vwf4 and https://github.com/advisories/GHSA-cwvm-v4w8-q58c Bump to `cryptography==41.0.4` due to https://github.com/advisories/GHSA-v8gr-m533-ghj9 Upgrade relenv to 0.13.12 to address CVE-2023-4807 Bump to `urllib3==1.26.17` or `urllib3==2.0.6` due to https://github.com/advisories/GHSA-v845-jxx5-vc9f Bump to `gitpython==3.1.37` due to https://github.com/advisories/GHSA-cwvm-v4w8-q58c
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: Enterprise-WeChat.md

Enterprise WeChat sink connector A sink plugin which use Enterprise WeChat robot send message For example, if the data from upstream is [`"alarmStatus": "firing", "alarmTime": "2022-08-03 01:38:49""alarmContent": "The disk usage exceeds the threshold"`], the output content to WeChat Robot is the following: ``` alarmStatus: firing alarmTime: 2022-08-03 01:38:49 alarmContent: The disk usage exceeds the threshold ``` Tips: WeChat sink only support `string` webhook and the data from source will be treated as body content in web hook. | name | type | required | default value | |--|--|-|| | url | String | Yes | - | | mentioned_list | array | No | - | | mentionedmobilelist | array | No | - | | common-options | | no | - | Enterprise WeChat webhook url format is https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=XXXXXXstring A list of userids to remind the specified members in the group (@ a member), @ all means to remind everyone. If the developer can't get the userid, he can use called mobile list Mobile phone number list, remind the group member corresponding to the mobile phone number (@ a member), @ all means remind everyone Sink plugin common parameters, please refer to for details simple: ```hocon WeChat { url = "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=693axxx6-7aoc-4bc4-97a0-0ec2sifa5aaa" } ``` ```hocon WeChat { url = "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=693axxx6-7aoc-4bc4-97a0-0ec2sifa5aaa" mentioned_list=["wangqing","@all"] mentionedmobilelist=["13800001111","@all"] } ``` Add Enterprise-WeChat Sink Connector )
Project: Dragonfly (Provisioning / Container Registry)
File: feature-request.md

name: Feature Request about: Request a new feature for dragonfly labels: enhancement <!-- Please describe the feature request and why you would like to have it --> <!-- Please add a concrete use case to demonstrate how such a feature would add value for the user. --> <!-- If this is about a new command or command line options, please let us know how you would add it to UI (in the code block below). -->
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.2.8.1.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Blocker | Root privilege escalation in experimental Docker support* CVE-2017-7669 / YARN's Docker support did not do enough input validation. This allowed a root level escalation from an ordinary user account.
Project: YugabyteDB (App Definition and Development / Database)
File: arctype.md

title: Use Arctype with YugabyteDB YSQL headerTitle: Arctype linkTitle: Arctype description: Use Arctype to work with distributed SQL databases in YugabyteDB. menu: v2.18: identifier: arctype parent: tools weight: 30 type: docs is a collaborative SQL database client that is free to use and cross platform. It offers one-click query sharing for teams, and you can visualize query output and combine multiple charts and tables into a dashboard. Arctype also features for connecting to YugabyteDB clusters. This document describes how to connect to YugabyteDB using Arctype. Your YugabyteDB cluster should be up and running. Refer to . Download clients for Windows, Linux, and Mac from the website. Follow these steps to connect your Arctype desktop client to YugabyteDB: Launch the Arctype desktop client. Follow the in-app prompts to create and log into your Arctype account. On the "Connect a Database" step, select YugabyteDB. Enter your YugabyteDB . Click Test Connection and, if the connection is successful, click Save. You can see the schemas and tables available in the YugabyteDB in the navigation panel. You've successfully created a connection to your YugabyteDB database, and you can now start querying and visualizing your DB using Arctype. To learn more about Arctype, refer to the . To learn about Arctype integration with Yugabyte, refer to the blog post and in the Arctype documentation. YugabyteDB includes sample databases for you to explore. Refer to .
Project: ShardingSphere (App Definition and Development / Database)
File: single.en.md

+++ title = "Single Table" weight = 12 +++ Single rule is used to specify which single tables need to be managed by ShardingSphere, or to set the default single table data source. ```yaml rules: !SINGLE tables: ds0.tsingle # Load specified single table ds_1.* # Load all single tables in the specified data source "." # Load all single tables ds0.public.tconfig ds_1.public.* ds_2.. "..*" defaultDataSource: ds_0 # The default data source is used when executing CREATE TABLE statement to create a single table. The default value is null, indicating random unicast routing. ```
Project: YugabyteDB (App Definition and Development / Database)
File: google-spanner.md

title: Compare Google Cloud Spanner with YugabyteDB headerTitle: Google Cloud Spanner linkTitle: Google Cloud Spanner description: Compare Google Cloud Spanner database with YugabyteDB. aliases: /comparisons/google-spanner/ menu: preview_faq: parent: comparisons identifier: comparisons-spanner weight: 1074 type: docs YugabyteDB's sharding, replication and transactions architecture is similar to that of which is also a globally-distributed CP database with high write availability. Both these databases are based on the design principles outlined in the published in 2012. Note that while Google Cloud Spanner leverages Google's proprietary (and expensive) network infrastructure, YugabyteDB is designed work on commodity infrastructure used by most enterprise users. Following blogs highlight how YugabyteDB differs from Google Cloud Spanner. Following blogs highlight how YugabyteDB works as an open source, cloud native Spanner derivative.
Project: OAuth2 Proxy (Provisioning / Key Management)
File: gitlab.md

id: gitlab title: GitLab This auth provider has been tested against Gitlab version 12.X. Due to Gitlab API changes, it may not work for version prior to 12.X (see ). Whether you are using GitLab.com or self-hosting GitLab, follow . Make sure to enable at least the `openid`, `profile` and `email` scopes, and set the redirect url to your application url e.g. https://myapp.com/oauth2/callback. If you need projects filtering, add the extra `read_api` scope to your application. The following config should be set to ensure that the oauth will work properly. To get a cookie secret follow ``` --provider="gitlab" --redirect-url="https://myapp.com/oauth2/callback" // Should be the same as the redirect url for the application in gitlab --client-id=GITLABCLIENTID --client-secret=GITLABCLIENTSECRET --cookie-secret=COOKIE_SECRET ``` Restricting by group membership is possible with the following option: ```shell --gitlab-group="mygroup,myothergroup" # restrict logins to members of any of these groups (slug), separated by a comma ``` If you are using self-hosted GitLab, make sure you set the following to the appropriate URL: ```shell --oidc-issuer-url="<your gitlab url>" ``` If your self-hosted GitLab is on a subdirectory (e.g. domain.tld/gitlab), as opposed to its own subdomain (e.g. gitlab.domain.tld), you may need to add a redirect from domain.tld/oauth pointing at e.g. domain.tld/gitlab/oauth.
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.2.7.2.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | Allow appending to existing SequenceFiles* Existing sequence files can be appended. | Major | Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs* Set YARN\FAIL\FAST to be false by default. If HA is enabled and if there's any state-store error, after the retry operation failed, we always transition RM to standby state.
Project: YugabyteDB (App Definition and Development / Database)
File: 10-is-null.md

title: "IS NULL" In this exercise we will query the customers table and find all the customers who do not have a region assigned to them. ``` SELECT contact_name, contact_title, city, country, region FROM customers WHERE region IS NULL; ``` This query should return 60 rows In this exercise we will query the customers table and find all the customers who do have a region assigned to them. ``` SELECT contact_name, contact_title, city, country, region FROM customers WHERE region IS NOT NULL; ``` This query should return 31 rows