cwielenb/CNCF-Dataset huggingface dataset:
Project: StarRocks (App Definition and Development / Database)
File: json_string.md

displayed_sidebar: "English" Converting JSON object to JSON string ```SQL jsonstring(jsonobject_expr) ``` `jsonobjectexpr`: the expression that represents the JSON object. The object can be a JSON column, or a JSON object that is produced by a JSON constructor function such as PARSE_JSON. Returns a VARCHAR value. Example 1: Converting the JSON object to a JSON string ```Plain select json_string('{"Name": "Alice"}'); +-+ | json_string('{"Name": "Alice"}') | +-+ | {"Name": "Alice"} | +-+ ``` Example 1: Convert the result of PARSE_JSON to a JSON string ```Plain select jsonstring(parsejson('{"Name": "Alice"}')); +-+ | json_string('{"Name": "Alice"}') | +-+ | {"Name": "Alice"} | +-+ ```
Project: RBAC Lookup (Provisioning / Security & Compliance)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: [triage, enhancement] 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: kiosk (Provisioning / Automation & Configuration)
File: CONDUCT.md

Cobra will follow a steady release cadence. Non breaking changes will be released as minor versions quarterly. Patch bug releases are at the discretion of the maintainers. Users can expect security patch fixes to be released within relatively short order of a CVE becoming known. For more information on security patch fixes see the CVE section below. Releases will follow . Users tracking the Master branch should expect unpredictable breaking changes as the project continues to move forward. For stability, it is highly recommended to use a release. We will maintain two major releases in a moving window. The N-1 release will only receive bug fixes and security updates and will be dropped once N+1 is released. Deprecation of Go versions or dependent packages will only occur in major releases. To reduce the change of this taking users by surprise, any large deprecation will be preceded by an announcement in the and an Issue on Github. Maintainers will make every effort to release security patches in the case of a medium to high severity CVE directly impacting the library. The speed in which these patches reach a release is up to the discretion of the maintainers. A low severity CVE may be a lower priority than a high severity one. Cobra maintainers will use GitHub issues and the as the primary means of communication with the community. This is to foster open communication with all users and contributors. Breaking changes are generally allowed in the master branch, as this is the branch used to develop the next release of Cobra. There may be times, however, when master is closed for breaking changes. This is likely to happen as we near the release of a new version. Breaking changes are not allowed in release branches, as these represent minor versions that have already been released. These version have consumers who expect the APIs, behaviors, etc, to remain stable during the lifetime of the patch stream for the minor release. Examples of breaking changes include: Removing or renaming exported constant, variable, type, or function. Updating the version of critical libraries such as `spf13/pflag`, `spf13/viper` etc... Some version updates may be acceptable for picking up bug fixes, but maintainers must exercise caution when reviewing. There may, at times, need to be exceptions where breaking changes are allowed in release branches. These are at the discretion of the project's maintainers, and must be carefully considered before merging. Maintainers will ensure the Cobra test suite utilizes the current supported versions of Golang. Changes to this document and the contents therein are at the discretion of the maintainers. None of the contents of this document are legally binding in any way to the maintainers or the users.
Project: StarRocks (App Definition and Development / Database)
File: weekofyear.md

displayed_sidebar: "English" Returns the week number for a given date within a year. The `date` parameter must be of the DATE or DATETIME type. ```Haskell INT WEEKOFYEAR(DATETIME date) ``` ```Plain Text MySQL > select weekofyear('2008-02-20 00:00:00'); +--+ | weekofyear('2008-02-20 00:00:00') | +--+ | 8 | +--+ ``` WEEKOFYEAR
Project: StarRocks (App Definition and Development / Database)
File: bitnot.md

displayed_sidebar: "English" Returns the bitwise negation of a numeric expression. ```Haskell BITNOT(x); ``` `x`: This expression must evaluate to any of the following data types: TINYINT, SMALLINT, INT, BIGINT, LARGEINT. The return value has the same type as `x`. If any value is NULL, the result is NULL. ```Plain Text mysql> select bitnot(3); +--+ | bitnot(3) | +--+ | -4 | +--+ ```
Project: StarRocks (App Definition and Development / Database)
File: CANCEL_BACKUP.md

displayed_sidebar: "English" Cancels an ongoing BACKUP task in a specified database. ```SQL CANCEL BACKUP FROM <db_name> ``` | Parameter | Description | | - | -- | | db_name | Name of the database that the BACKUP task belongs to. | Example 1: Cancels the BACKUP task under the database `example_db`. ```SQL CANCEL BACKUP FROM example_db; ```
Project: kpt (Provisioning / Automation & Configuration)
File: docs.md

CLI commands name should appear with inline quotes everywhere including in page titles: Correct: `diff` Incorrect: `Diff` Incorrect: `The Diff tool` Shell commands should be in `shell` code blocks and should contain exactly one command specifing using`$`: ```shell $ kpt <command> <output> ``` Links to other kpt doc pages should be absolute: Correct: `[pkg]: /reference/cli/pkg/get/` Incorrect: `[pkg]: ../../../reference/cli/pkg/get` Flags must appear after positional args: Correct: ```shell $ kpt fn eval my-package --image gcr.io/kpt-fn/search-replace ``` Incorrect: ```shell $ kpt fn eval --image gcr.io/kpt-fn/search-replace my-package ``` The name of the tool should always appear as small caps (even at start of sentences) and not in block quotes: Correct: kpt Incorrect: `kpt` Incorrect: Kpt Incorrect: KPT References to a particular KRM group, version, kind, field should appear with inline quotes: Correct: `ConfigMap` Incorrect: ConfigMap
Project: Beam (App Definition and Development / Streaming & Messaging)
File: android.md

title: "Android" icon: /images/logos/powered-by/android.png hasLink: "https://www.android.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: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-token-delete.md

layout: default title: mesheryctl-system-token-delete permalink: reference/mesheryctl/system/token/delete redirect_from: reference/mesheryctl/system/token/delete/ type: reference display-title: "false" language: en command: system subcommand: token Delete a token from your meshconfig Delete the token with provided token name from your meshconfig tokens. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system token delete [flags] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system token delete [token-name] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for delete </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: KICS (Provisioning / Security & Compliance)
File: c2f15af3-66a0-4176-a56e-e4711e502e5c.md

title: Hardcoded AWS Access Key hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c2f15af3-66a0-4176-a56e-e4711e502e5c Query name: Hardcoded AWS Access Key Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Secret Management URL: AWS Access Key should not be hardcoded<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" name: start an instance with a cpu_options community.aws.ec2_instance: name: "public-cpuoption-instance" vpcsubnetid: subnet-5ca1ab1e tags: Environment: Testing user_data: "1234567890123456789012345678901234567890$" ``` ```yaml title="Negative test num. 1 - yaml file" name: start an instance with a cpu_options community.aws.ec2_instance: name: public-cpuoption-instance vpcsubnetid: subnet-5ca1ab1e tags: Environment: Testing instance_type: c4.large volumes: device_name: /dev/sda1 ebs: deleteontermination: true cpu_options: core_count: 1 threadspercore: 1 ```
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: 1.13.md

We can't wait for you to try our newest features! New Cluster Mode! View resources from your cluster in real time Check the state of the resources at a glance Resource validation while in browsing the cluster Edit the YAML and redeploy to the cluster Enhanced Monokle's Compare & Sync feature with the addition of subfolder comparison For more info about these new features and additional updates
Project: Veinmind Tools (Provisioning / Security & Compliance)
File: veinmind-runner_completion_bash.md

Generate the autocompletion script for bash Generate the autocompletion script for the bash shell. This script depends on the 'bash-completion' package. If it is not installed already, you can install it via your OS's package manager. To load completions in your current shell session: source <(veinmind-runner completion bash) To load completions for every new session, execute once: veinmind-runner completion bash > /etc/bash_completion.d/veinmind-runner veinmind-runner completion bash > $(brew --prefix)/etc/bash_completion.d/veinmind-runner You will need to start a new shell for this setup to take effect. ``` veinmind-runner completion bash ``` ``` -h, --help help for bash --no-descriptions disable completion descriptions ``` ``` -e, --exit-code int exit-code when veinmind-runner find security issues -g, --glob string specifies the pattern of plugin file to find -o, --output string output filepath of report --threads int threads for scan action (default 5) ``` - Generate the autocompletion script for the specified shell
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: v1.7.0.md

title: v1.7.0 weight: 998993000 The scaffolded `--config` flag was not added to either ansible-/helm-operator binary when support was originally added, so does not currently work. The `--config` flag supports configuration of both binaries by file; this method of configuration only applies to the underlying , not the operator as a whole. To optionally configure the operator's Deployment with a config file, make the following update to config/default/kustomization.yaml: ```diff managerauthproxy_patch.yaml +# Mount the controller config file for loading manager configurations +# through a ComponentConfig type +- managerconfigpatch.yaml ``` This feature is opt-in: flags can be used as-is or to override config file values. See for more details. The operator-framework is removing support for the packagemanifests format in the near future. Hence, `operator-sdk generate packagemanifests` and `operator-sdk run packagemanifests` commands are deprecated. In order to migrate packagemanifests to bundles, `operator-sdk pkgman-to-bundle` command can be used. Run `operator-sdk pkgman-to-bundle --help` for more details. See for more details. Make the following changes to config/rbac/leaderelectionrole.yaml: ```diff rules: \- apiGroups: "" - coordination.k8s.io resources: configmaps verbs: +- get +- list +- watch +- create +- update +- patch +- delete +- apiGroups: +- coordination.k8s.io resources: leases verbs: get ``` See for more details. Importing `setup-envtest.sh` needs bash, so your Makefile's `SHELL` variable should be set to `bash` with error options: ```diff else GOBIN=$(shell go env GOBIN) endif +# Setting SHELL to bash allows bash commands to be executed by recipes. +# This is a requirement for 'setup-envtest.sh' in the test target. +# Options are set to exit when a recipe line exits non-zero or a piped command fails. +SHELL = /usr/bin/env bash -o pipefail +.SHELLFLAGS = -ec all: build ``` See for more details.
Project: Harbor (Provisioning / Container Registry)
File: 7-06-Trigger-immediate.md

Test 7-06 - Immediate trigger ======= To verify the immediate replication rule can work as expected. User guide This test requires that at least two Harbor instances are running and available. Create a new replication rule whose triggering condition is set to immediate and no filter is configured. Push an image to the project that the replication is applied to. Login UI as admin user. In `Administration->Replications` page, edit the rule and make sure the `Delete remote images when locally deleted` is checked. Delete the image pushed in step 1 on UI. In `Administration->Replications` page, edit the rule and make sure the `Delete remote images when locally deleted` is unchecked. Push the image to the project that the replication is applied to again. Delete the image pushed in step 6 on UI. In step 1, a job should be started and the image should be replicated to the remote registry. In step 4, a job should be started and the image should be deleted from the remote registry. In step 6, a job should be started and the image should be replicated to the remote registry. In step 7, a job should be started and the image should not be deleted from the remote registry. None
Project: ClickHouse (App Definition and Development / Database)
File: v23.2.3.17-stable.md

sidebar_position: 1 sidebar_label: 2023 Backported in : - Fix incorrect alias recursion in QueryNormalizer. (). Backported in : - Fix arithmetic operations in aggregate optimization with `min` and `max`. (). Backported in : Fix MSan report in the `maxIntersections` function. This closes . (). Backported in : Fix typo in systemd service, which causes the systemd service start to fail. (). Backported in : Fix concrete columns PREWHERE support. (). Use /etc/default/clickhouse in systemd too (). do flushUntrackedMemory when context switches (). Update typing for a new PyGithub version ().
Project: KICS (Provisioning / Security & Compliance)
File: 6c2d627c-de0f-45fb-b33d-dad9bffbb421.md

title: Cloud Storage Bucket Logging Not Enabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6c2d627c-de0f-45fb-b33d-dad9bffbb421 Query name: Cloud Storage Bucket Logging Not Enabled Platform: Crossplane Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Cloud storage bucket should have logging enabled<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="5" apiVersion: storage.gcp.crossplane.io/v1alpha3 kind: Bucket metadata: name: bucketSample spec: location: EU storageClass: MULTI_REGIONAL providerConfigRef: name: crossplane-gcp labels: made-by: crossplane deletionPolicy: Delete ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: storage.gcp.crossplane.io/v1alpha3 kind: Bucket metadata: name: bucketSample spec: location: EU logging: logBucket: example-logs-bucket storageClass: MULTI_REGIONAL providerConfigRef: name: crossplane-gcp labels: made-by: crossplane deletionPolicy: Delete ```
Project: Chef Infra (Provisioning / Automation & Configuration)
File: gem_installation_via_metadata.md

Support a 'gem' DSL method for cookbook metadata to create a dependency on a rubygem. The gem will be installed via `chef_gem` after all the cookbooks are synchronized, but before any other cookbook loading is done. As a Chef User, I want to be able to use additional gems in libraries, attributes and resources, and to avoid complex workarounds and double-run converges. Allow users to specify additional gem dependencies like: ```ruby gem "poise" gem "chef-sugar" gem "chef-provisioning" ``` In the `Chef::RunContext::CookbookCompiler#compile` method, a phase will be added before `compile_libraries`. This phase will install all of the gem declarations from all of the synchronized cookbooks before any other cookbook code is compiled. The implementation will use an in-memory bundler Gemfile which is constructed against all gem statements in all cookbooks which are in the `run_list`, solved at the same time. The syntax of the 'gem' statement will support the bundler gem syntax, with the qualification of since the syntax is compiled into metadata.json, that arbitrary ruby code will be expanded at cookbook upload time. The resulting gemset bundle will be installed into the LIBPATH of the running chef-client. This may either be directly into the base ruby libraries (per current `chef_gem` behavior), or into a custom location with the LIBPATH of the chef-client extended to use that location--as an open implementation question. The normal Gemfile `requires` tag may be used by users to autoload files out of gems.
Project: Harbor (Provisioning / Container Registry)
File: 3-22-DB-admin-role-user-search-project-members.md

Test 3-22 - Admin Role User Search Project Members (DB Mode) ======= To verify that a user with system admin role can search members of a project when users are managed locally by Harbor (DB mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database. ( auth_mode is set to db_auth* .) The user data is stored in a local database. A linux host with Docker CLI installed (Docker client). At least five(5) non-admin users are in Harbor. At least 5 members in a project that admin user is not a member of. NOTE: The below non-admin user M should NOT be the same as the non-admin user in Test 3-12. Assign an non-admin user M with system admin role and act as an admin user. Repeat all steps in Test 3-12. A user with system admin role can perform all operations the same as the admin user. Same as Test 3-12. None
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.21.md

RabbitMQ `3.9.21` is a maintenance release in the `3.9.x` release series. Please refer to the Upgrading to 3.9 section from if upgrading from a version prior to 3.9.0. This release requires at least Erlang 23.2, and supports Erlang 24. has more details on Erlang version requirements for RabbitMQ. Release notes can be found on GitHub at . Optimization: internal message GUID is no longer generated for quorum queues and streams, as they are specific to classic queues. GitHub issue: Two more AMQP 1.0 connection lifecycle events are now logged. GitHub issue: TLS configuration for inter-node stream replication connections now can use function references and definitions. GitHub issue: Stream protocol connection logging is now less verbose. GitHub issue: Max stream segment size is now limited to 3 GiB to avoid a potential stream position overflow. GitHub issue: Logging messages that use microseconds now use "us" for the SI symbol to be compatible with more tools. GitHub issue: Channels on connections to mixed clusters that had 3.8 nodes in them could run into an exception. GitHub issue: Inter-node cluster link statistics did not have any data when TLS was enabled for them. GitHub issue: Quorum queues now correctly propagate errors when a `basic.get` (polling consumption) operation hits a timeout. Contributed by Ayanda @Ayanda-D Dube. GitHub issue: Stream consumer that used AMQP 0-9-1 instead of a stream protocol client, and disconnected, leaked a file handle. GitHub issue: Max frame size and client heartbeat parameters for clients were not correctly set when taken from `rabbitmq.conf`. GitHub issue: Removed a duplicate exchange decorator set operation. Contributed by Pter @gomoripeti Gmri. GitHub issue: Node restarts could result in a hashing ring inconsistency. This required a potentially breaking change: this exchange type now only allows for one binding between an exchange and a queue (or another exchange). All subsequent binding operations between them will be ignored, so "first write wins". This is a natural topology for this plugin, and enforcing it helps avoid a set of potential issues with concurrent node restarts and client operations that affect consistent hash ring state. GitHub issue: Consul peer discovery now supports client-side TLS options, much like its Kubernetes and etcd peers. ``` ini cluster_formation.consul.scheme = https cluster_formation.consul.port = 8501 clusterformation.consul.ssloptions.cacertfile = /path/to/consul/generated/ca_certificate.pem clusterformation.consul.ssloptions.certfile = /path/to/client/certificate.pem clusterformation.consul.ssloptions.keyfile = /path/to/client/client_key.pem ``` GitHub issue: To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.21.tar.xz` instead of the source tarball produced by GitHub.
Project: Checkov (Provisioning / Security & Compliance)
File: CSV.md

layout: default published: true title: CSV nav_order: 20 A CSV output would generate 3 output files: iac.csv container_images.csv oss_packages.csv | Resource | Path | Git Org | Git Repository | Misconfigurations | Severity | |:-|:--|:--|:-|:-|:-| | awsdbinstance.default | /terraform/aws/db-app.tf | prisma | terragoat | CKVAWS161 | MEDIUM | | Package | Version | Path | Git Org | Git Repository | Vulnerability | Severity | Licenses | |:|:|:|:--|:-|:-|:-|:-| | xmldom | 0.5.0 | /packages/node/twistcli-test/package-lock.json | prisma | terragoat | CVE-2021-32796 | MEDIUM | | Package | Version | Path | Git Org | Git Repository | Vulnerability | Severity | Licenses | |:|:|:|:--|:-|:-|:-|:-| | xmldom | 0.5.0 | /Dockerfile (sha256:6a353e22ce) | prisma | terragoat | CVE-2021-32796 | MEDIUM |
Project: Gradle Build Tool (App Definition and Development / Application Definition & Image Build)
File: 0005-introduce-core-ui-architecture-module.md

2024-02-07 The Gradle core platform provides many services to the Gradle platforms and builds logic. One such group of services allows logic to interact with the build user, to provide diagnostics, progress information, prompt for questions, and so on. Currently, these services are part of the core platform runtime architecture module. A downside of this structure is that it is difficult to do focused work on the Gradle UI. Introduce a "UI" architecture module to the core platform, and move the user interaction services to this new module. This includes: Logging and progress services. Problem generation services (aka the "problems API"). User prompting services. Build options infrastructure. The console and CLI, as a specific implementation of these services. The UI architecture module uses the core runtime architecture module. It provides APIs that are used by the other modules and platforms. This ADR does not specify the owner of this new architecture module. However, as a separate module, it can be assigned ownership independently of the other core services. ACCEPTED Introduce the module and move the services and their implementations. Assign ownership of the module.