cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 2f737336-b18a-4602-8ea0-b200312e1ac1.md

title: RDS Associated with Public Subnet hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2f737336-b18a-4602-8ea0-b200312e1ac1 Query name: RDS Associated with Public Subnet Platform: Terraform Severity: <span style="color:#ff0000">Critical</span> Category: Networking and Firewall URL: RDS should not run in public subnet<br> ```tf title="Positive test num. 1 - tf file" hl_lines="11" resource "awsdbinstance" "positive1" { allocated_storage = 10 engine = "mysql" engine_version = "5.7" instance_class = "db.t3.micro" name = "mydb" username = "foo" password = "foobarbaz" parametergroupname = "positive1.mysql5.7" skipfinalsnapshot = true dbsubnetgroupname = awsdbsubnetgroup.subnetGroup.name } resource "awsdbsubnet_group" "subnetGroup" { name = "main" subnetids = [awssubnet.frontend.id, aws_subnet.backend.id] tags = { Name = "My DB subnet group" } } resource "aws_subnet" "frontend" { vpcid = awsvpcipv4cidrblockassociation.secondarycidr.vpcid cidr_block = "172.2.0.0/24" } resource "aws_subnet" "backend" { vpcid = awsvpcipv4cidrblockassociation.secondarycidr.vpcid cidr_block = "0.0.0.0/0" } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="11" resource "awsdbinstance" "positive2" { allocated_storage = 10 engine = "mysql" engine_version = "5.7" instance_class = "db.t3.micro" name = "mydb" username = "foo" password = "foobarbaz" parametergroupname = "positive2.mysql5.7" skipfinalsnapshot = true dbsubnetgroup_name = "subnetGroup2" } resource "awsdbsubnet_group" "subnetGroup2" { name = "main" subnetids = [awssubnet.frontend2.id, aws_subnet.backend2.id] tags = { Name = "My DB subnet group" } } resource "aws_subnet" "frontend2" { vpcid = awsvpcipv4cidrblockassociation.secondarycidr.vpcid cidr_block = "172.2.0.0/24" } resource "aws_subnet" "backend2" { vpcid = awsvpcipv4cidrblockassociation.secondarycidr.vpcid cidr_block = "0.0.0.0/0" } ``` ```tf title="Negative test num. 1 - tf file" resource "awsdbinstance" "negative1" { allocated_storage = 10 engine = "mysql" engine_version = "5.7" instance_class = "db.t3.micro" name = "mydb" username = "foo" password = "foobarbaz" parametergroupname = "negative1.mysql5.7" skipfinalsnapshot = true dbsubnetgroupname = awsdbsubnetgroup.subnetGroup3.name } resource "awsdbsubnet_group" "subnetGroup3" { name = "main" subnetids = [awssubnet.frontend3.id, aws_subnet.backend3.id] tags = { Name = "My DB subnet group" } } resource "aws_subnet" "frontend3" { vpcid = awsvpcipv4cidrblockassociation.secondarycidr.vpcid cidr_block = "172.2.0.0/24" } resource "aws_subnet" "backend3" { vpcid = awsvpcipv4cidrblockassociation.secondarycidr2.vpcid cidr_block = "176.2.0.0/24" } ```
Project: KICS (Provisioning / Security & Compliance)
File: 054d07b5-941b-4c28-8eef-18989dc62323.md

title: PostgreSQL Log Disconnections Not Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 054d07b5-941b-4c28-8eef-18989dc62323 Query name: PostgreSQL Log Disconnections Not Set Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Make sure that for PostgreSQL Database, server parameter 'log_disconnections' is set to 'ON'<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="37 7 13 19 25 31" name: Update PostgreSQL Server setting azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_disconnections value: off name: Update PostgreSQL Server setting2 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_disconnections value: Off name: Update PostgreSQL Server setting3 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_disconnections value: OFF name: Update PostgreSQL Server setting4 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_disconnections value: "off" name: Update PostgreSQL Server setting5 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_disconnections value: "Off" name: Update PostgreSQL Server setting6 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_disconnections value: "OFF" ``` ```yaml title="Negative test num. 1 - yaml file" name: Update PostgreSQL Server setting azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_disconnections value: on name: Update PostgreSQL Server setting2 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_disconnections value: On name: Update PostgreSQL Server setting3 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_disconnections value: ON name: Update PostgreSQL Server setting4 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_disconnections value: on name: Update PostgreSQL Server setting5 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_disconnections value: On name: Update PostgreSQL Server setting6 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_disconnections value: ON ```
Project: StarRocks (App Definition and Development / Database)
File: aes_decrypt.md

displayed_sidebar: "English" Uses the AES128ECB algorithm to decrypt a string and returns a binary string. AES is short for advanced encryption standard and ECB is short for electronic code book. The key used to encrypt the string is a 128-bit string. ```Haskell aesdecrypt(str,keystr); ``` `str`: the string to decrypt. It must be of the VARCHAR type. `key_str`: the key used to encrypt `str`. It must be of the VARCHAR type. Returns a value of the VARCHAR type. If the input is invalid, NULL is returned. Decode a Base64 string and use this function to decrypt the decoded string into the original string. ```Plain Text mysql> select AESDECRYPT(frombase64('uv/Lhzm74syo8JlfWarwKA== '),'F3229A0B371ED2D9441B830D21A390C3'); +--+ | aesdecrypt(frombase64('uv/Lhzm74syo8JlfWarwKA== '), 'F3229A0B371ED2D9441B830D21A390C3') | +--+ | starrocks | +--+ 1 row in set (0.00 sec) ```
Project: StarRocks (App Definition and Development / Database)
File: bitmap_to_array.md

displayed_sidebar: "English" Converts a BITMAP into a BIGINT array. ```Haskell ARRAY<BIGINT> BITMAPTOARRAY (bitmap) ``` `bitmap`: the bitmap you want to convert. Returns a BIGINT array. ```Plain select bitmaptoarray(bitmapfromstring("1, 7")); +-+ | bitmaptoarray(bitmapfromstring('1, 7')) | +-+ | [1,7] | +-+ select bitmaptoarray(NULL); +--+ | bitmaptoarray(NULL) | +--+ | NULL | +--+ ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: sbom-scanner-command.md

Generate SBOMs by running the specified command from the scanner image. If multiple commands are specified, they are run in the order in which they are specified. These text substitutions are performed: {ROOTFS} The root of the built image's filesystem, bind mounted. {CONTEXT} The build context and additional build contexts, bind mounted. {OUTPUT} The name of a temporary output file, to be read and merged with others or copied elsewhere.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: uts.md

Sets the configuration for UTS namespaces when handling `RUN` instructions. The configured value can be "" (the empty string) or "container" to indicate that a new UTS namespace to be created, or it can be "host" to indicate that the UTS namespace in which `podman` itself is being run is reused, or it can be the path to a UTS namespace which is already in use by another process.
Project: Glasskube (App Definition and Development / Application Definition & Image Build)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: enhancement, needs-triage assignees: '' Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here.
Project: YDB (App Definition and Development / Database)
File: current_tz.md

`CurrentTzDate()`, `CurrentTzDatetime()`, and `CurrentTzTimestamp()`: Get the current date and/or time in the specified in the first argument. The result data type is specified at the end of the function name. The arguments that follow are optional and work same as . Examples ```yql SELECT CurrentTzDate("Europe/Moscow"); ``` ```yql SELECT CurrentTzTimestamp("Europe/Moscow", TableRow()) FROM my_table; ``` Adding the time zone information to the date/time in UTC. In the result of `SELECT` or after `CAST`, a `String` will be subject to the time zone rules used to calculate the time offset. Arguments: Date: the type is `Date``Datetime`/`Timestamp`. . Result type: `TzDate`/`TzDatetime`/`TzTimestamp`, depending on the input data type. Examples ```yql SELECT AddTimezone(Datetime("2018-02-01T12:00:00Z"), "Europe/Moscow"); ``` Removing the time zone data and converting the value to date/time in UTC. Arguments: Date: the type is `TzDate`/`TzDatetime`/`TzTimestamp`. Result type: `Date`/`Datetime`/`Timestamp`, depending on the input data type. Examples ```yql SELECT RemoveTimezone(TzDatetime("2018-02-01T12:00:00,Europe/Moscow")); ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.0-rc-5a.md

layout: release date: 2022-02-18 tag: v0.6.0-rc-5a language: en Fix context switching for None provider @Revolyssup (#5086) update meshkit version @warunicorn19 (#5071) allow 201 code from meshery cloud while saving k8s context @Revolyssup (#5065) fix k8s registeration bug after multi-context PR @Revolyssup (#5064) [mesheryctl] Mesheryctl moves with Meshkit logger @piyushsingariya (#5085) Fix/mesh deploy hang/#4313 @Zanda256 (#5059) [mesheryctl] minor change in skip-browser flag functionality @piyushsingariya (#5066) updated style and fixed search in context switcher @warunicorn19 (#5090) [UI] Multi-Context Switcher: style changes and bug fix @warunicorn19 (#5081) [UI] Updated Sidebar of Meshery According to New Figma Design @YashKamboj (#5079) Bump follow-redirects from 1.11.0 to 1.14.8 in /ui @dependabot (#5061) Fix Multi-Context @utkarsh-pro (#5076) Bump nanoid from 3.1.23 to 3.3.0 in /ui @dependabot (#5072) Bump cached-path-relative from 1.0.2 to 1.1.0 in /ui @dependabot (#5073) Bump follow-redirects from 1.14.1 to 1.14.8 in /provider-ui @dependabot (#5062) [Extension] Add loading component for the load of meshery extension @Abhishek-kumar09 (#5063) modify cypress tests after multi-ctx PR @Abhishek-kumar09 (#5069) [Perf] fixed search issue @asubedy (#4915) Fix Meshery Crash on loading lifecycle @Abhishek-kumar09 (#5067) Multi-Context Support @utkarsh-pro (#4218) Redux: Extract drawer collapse variable with redux @Abhishek-kumar09 (#5058) Bump github.com/prometheus/client_golang from 1.11.0 to 1.12.1 @dependabot (#5025) Bump github.com/layer5io/meshsync from 0.1.30 to 0.5.0 @dependabot (#5049) Bump follow-redirects from 1.11.0 to 1.14.8 in /ui @dependabot (#5061) Bump nanoid from 3.1.23 to 3.3.0 in /ui @dependabot (#5072) Bump cached-path-relative from 1.0.2 to 1.1.0 in /ui @dependabot (#5073) Bump github.com/layer5io/meshkit from 0.5.2 to 0.5.6 @dependabot (#5074) Bump follow-redirects from 1.14.1 to 1.14.8 in /provider-ui @dependabot (#5062) removed slack and spanish @warunicorn19 (#5088) [Docs] Improving navigability of error code guide @shubham-tyagi (#4981) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Revolyssup, @YashKamboj, @Zanda256, @asubedy, @dependabot, @dependabot[bot], @hexxdump, @l5io, @leecalcote, @navendu-pottekkat, @piyushsingariya, @shubham-tyagi, @sudo-NithishKarthik, @utkarsh-pro and @warunicorn19
Project: ClickHouse (App Definition and Development / Database)
File: kurtsamp.md

slug: /en/sql-reference/aggregate-functions/reference/kurtsamp sidebar_position: 154 Computes the of a sequence. It represents an unbiased estimate of the kurtosis of a random variable if passed values form its sample. ``` sql kurtSamp(expr) ``` Arguments `expr` returning a number. Returned value The kurtosis of the given distribution. Type . If `n <= 1` (`n` is a size of the sample), then the function returns `nan`. Example ``` sql SELECT kurtSamp(value) FROM serieswithvalue_column; ```
Project: YugabyteDB (App Definition and Development / Database)
File: 13-union.md

title: "UNION" In this exercise we will query the suppliers and customers table and combine the result sets while removing duplicates it finds. ``` SELECT company_name FROM suppliers UNION SELECT company_name FROM customers; ``` This query should return 120 rows In this exercise we will query the suppliers and customers tables and combine the result sets without removing duplicates if they exist. ``` SELECT company_name FROM suppliers UNION ALL SELECT company_name FROM customers; ``` This query should return 120 rows In this exercise we will query the suppliers and customers tables, combine the result sets without removing duplicates if they exist and ordering them in descending order. ``` SELECT company_name FROM suppliers UNION ALL SELECT company_name FROM customers ORDER BY company_name DESC ``` This query should return 120 rows
Project: Meshery (Provisioning / Automation & Configuration)
File: 06-15-2023-18-53-06_2dce4e09.md

timestamp: "2023-06-15 18:52:58 UTC Thu" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "*name" k8s-distro: minikube k8s-version: "v1.21.5" service-mesh: Consul service-mesh-version: "v1.2.0-rc1" tests: consul-client: null consul-server: null overall-status: "failing"
Project: Terraform (Provisioning / Automation & Configuration)
File: releasing-new-version.md

Terraform's plugin protocol is the contract between Terraform's plugins and Terraform, and as such releasing a new version requires some coordination between those pieces. This document is intended to be a checklist to consult when adding a new major version of the protocol (X in X.Y) to ensure that everything that needs to be is aware of it. The protocol is defined in protobuf files that live in the hashicorp/terraform repository. Adding a new version of the protocol involves creating a new `.proto` file in that directory. It is recommended that you copy the latest protocol file, and modify it accordingly. The repository serves as the foundation for Terraform's plugin ecosystem. It needs to know about the new major protocol version. Either open an issue in that repo to have the Plugin SDK team add the new package, or if you would like to contribute it yourself, open a PR. It is recommended that you copy the package for the latest protocol version and modify it accordingly. The Terraform Registry validates the protocol versions a provider advertises support for when ingesting providers. Providers will not be able to advertise support for the new protocol version until it is added to that list. Terraform only downloads providers that speak protocol versions it is compatible with from the Registry during `terraform init`. When adding support for a new protocol, you need to tell Terraform it knows that protocol version. Modify the `SupportedPluginProtocols` variable in hashicorp/terraform's `internal/getproviders/registry_client.go` file to include the new protocol. Use the provider test framework to test a provider written with the new protocol. This end-to-end test ensures that providers written with the new protocol work correctly with the test framework, especially in communicating the protocol version between the test framework and Terraform. Publish a provider, either to the public registry or to the staging registry, and test running `terraform init` and `terraform apply`, along with exercising any of the new functionality the protocol version introduces. This end-to-end test ensures that all the pieces needing to be updated before practitioners can use providers built with the new protocol have been updated.
Project: Goldilocks (Provisioning / Security & Compliance)
File: CODE_OF_CONDUCT.md

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

layout: default title: mesheryctl-system-config-aks permalink: reference/mesheryctl/system/config/aks redirect_from: reference/mesheryctl/system/config/aks/ type: reference display-title: "false" language: en command: system subcommand: config Configure Meshery to use AKS cluster Configure Meshery to connect to AKS cluster <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system config aks [flags] </div> </pre> Configure Meshery to connect to AKS cluster using auth token <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system config aks --token auth.json </div> </pre> Configure Meshery to connect to AKS cluster (if session is logged in using login subcommand) <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system config aks </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for aks -t, --token string Path to token for authenticating to Meshery API </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -c, --context string (optional) temporarily change the current context. -v, --verbose verbose output -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.1.5-patch.2.en.md

This change allows to set the minReadySeconds for the StatefulSet. This allows to add a gap between the restarts of each pod by upgrade or restart command. Add `node.brokerpoolsize`, `node.genericpoolsize`, `node.channelcleanupbatch_size` options to EMQX configuration. Tuning these options can significantly improve performance if cluster interconnect network latency is high. Improved retained message publishing latency by consolidating multiple index update operations into a single mnesia activity, leveraging the new APIs introduced in mria 0.6.0. Improve the error reason of the `datetounix_ts` to make more sense. Increase `emqxroutersup` restart intensity. The goal is to tolerate occasional crashes that can happen under relatively normal conditions and don't seem critical to shutdown the whole app (emqx). For example, mria write/delete call delegated from a replicant to a core node by `emqxrouterhelper` may fail, if the core node is being stopped / restarted / not ready. Reintroduce `cacerts` TLS client option as a deprecated option. This fixes issues found when trying to upgrade from 5.1.3 where that option is set in the configuration files or persisted in EMQX Operator settings.
Project: Buildpacks (App Definition and Development / Application Definition & Image Build)
File: chore.md

name: Chore about: Suggest a chore that will help contributors and doesn't affect end users. title: '' labels: type/chore, status/triage assignees: '' <!-- A concise description of why this chore matters, who will enjoy it and how. --> <!-- A clear and concise description of how do you think the chore should be implemented. --> <!-- Add any other context or screenshots about the chore that may help. -->
Project: StarRocks (App Definition and Development / Database)
File: rpad.md

displayed_sidebar: "English" This function returns strings with a length of `len` (starting counting from the first syllable) in `str`. If `len` is longer than `str`, the return value is lengthened to `len` characters by adding pad characters behind `str`. If `str` is longer than `len`, the return value is shortened to `len` characters. `len` means the length of characters, not bytes. ```Haskell VARCHAR rpad(VARCHAR str, INT len[, VARCHAR pad]) ``` `str`: required, the string to be padded, which must evaluate to a VARCHAR value. `len`: required, the length of return value, it means the length of characters, not bytes, which must evaluate to an INT value. `pad`: optional, the characters to be added behind str, which must be a VARCHAR value. If this parameter is not specified, spaces are added by default. Returns a VARCHAR value. ```Plain Text MySQL > SELECT rpad("hi", 5, "xy"); ++ | rpad('hi', 5, 'xy') | ++ | hixyx | ++ MySQL > SELECT rpad("hi", 1, "xy"); ++ | rpad('hi', 1, 'xy') | ++ | h | ++ MySQL > SELECT rpad("hi", 5); ++ | rpad('hi', 5, ' ') | ++ | hi | ++ ``` RPAD