cwielenb/CNCF-Dataset huggingface dataset:
Project: KOTS (App Definition and Development / Application Definition & Image Build)
File: helm-v3.md

KOTS currently pulls and renders Charts using Helm V2. This proposal is to add support for Helm V3. Render Helm Charts using Helm V3 Any additional Helm functionality outside of the current pull and render workflows Helm V3 has been stable since Nov 13, 2019. Some Charts are using apiVerion v2 and additional Helm V3 Chart functionality. KOTS does not currently use Helm V3 to render Charts. A new property `spec.helmVersion` will be added to the `kots.io/beta` `HelmChart` spec which can be used to toggle the Helm version used to pull and render the Helm Chart. This property will default to `v2` and can optionally be set to `v3`. As Helm V3 is backwards compatible with V2, once there is evidence of success in various environments including real world scenarios, it is the intention to change this property to default to `v3`. A new property `spec.helmVersion` will be added to the `kots.io/beta` `HelmChart` spec which can be used to toggle the Helm version used to pull and render the Helm Chart. This property will default to `v2` and can optionally be set to `v3`. When unset or set to `v2` KOTS will use the `helm.sh/helm/v2` Go library to pull and render the Helm Chart. The existing code path should remain the same. When set to `v3` KOTS will use the `helm.sh/helm/v3` Go library to pull and render the Helm Chart.
Project: StarRocks (App Definition and Development / Database)
File: DROP_CATALOG.md

displayed_sidebar: "English" Deletes an external catalog. The internal catalog cannot be deleted. A StarRocks cluster has only one internal catalog named `default_catalog`. ```SQL DROP CATALOG <catalog_name> ``` `catalog_name`: The name of an external catalog. Create a Hive catalog named `hive1`. ```SQL CREATE EXTERNAL CATALOG hive1 PROPERTIES( "type"="hive", "hive.metastore.uris"="thrift://xx.xx.xx.xx:9083" ); ``` Delete the Hive catalog. ```SQL DROP CATALOG hive1; ```
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: styra-academy.md

title: Styra Academy subtitle: OPA Learning Portal software: [] inventors: styra labels: category: learning type: poweredbyopa tutorials: https://academy.styra.com https://academy.styra.com/courses/opa-by-example https://academy.styra.com/courses/opa-rego https://academy.styra.com/courses/opa-k8s-admission-control https://academy.styra.com/courses/opa-performance code: https://github.com/StyraInc/academy-samples docs_features: learning-rego: note: | is a free course that teaches the fundamentals of writing Rego policies. Styra Academy is a free, self-paced learning portal for OPA and Styra Products. It includes a series of courses on a range of topics from beginner to advanced.
Project: StarRocks (App Definition and Development / Database)
File: st_circle.md

displayed_sidebar: "English" Converts a WKT (WEll Known Text) to a circle on the sphere of the earth. ```Haskell GEOMETRY STCircle(DOUBLE centerlng, DOUBLE center_lat, DOUBLE radius) ``` `center_lng` indicates the longitude of the center of the circle. `center_lat` indicates the latitude of the center of the circle. `radius` indicates the radius of a circle, in meters. A maximum of 9999999 radius is supported. ```Plain Text MySQL > SELECT STAsText(STCircle(111, 64, 10000)); +--+ | stastext(stcircle(111.0, 64.0, 10000.0)) | +--+ | CIRCLE ((111 64), 10000) | +--+ ``` ST_CIRCLE,ST,CIRCLE
Project: Harbor (Provisioning / Container Registry)
File: 2-02-DB-user-push-multiple-images.md

Test 2-02 - User Push Multiple Images (DB Mode) ======= To verify that a non-admin user can push multiple images to 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 a non-admin user and the user has at least a project as project admin. NOTE: In below test, user A is non-admin user. User A and project X should be replaced by longer and meaningful names. Log in to UI as user A (non-admin). Verify User A has at least a project X with the role of project admin. On a Docker client, log in as User A and run `docker push` to push an image with tag (e.g. nginx:1.5) to project X. Continue to push at least 5 images with different tags, for example, nginx:1.6, nginx:1.7, nginx:1.8, nginx:release . In the UI, go to "My Projects" to see if all images/tags are properly displayed. Checks the detail info of each tag. Enter keyword to search(filter) images/tags of a project. On a Docker client, log in as User A and run `docker pull` to pull images with different tags from project X. Step 3-5, images can be pushed to project X and can be shown in UI. Step 6, image/tag info should be correct. Step 7, image/tag should be filtered and results should be matched the search criteria. Step 8, images can be pulled from project X. None
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: read-object.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: read-object namespace: default spec: components: name: express-server type: webservice properties: image: oamdev/hello-world port: 8000 workflow: steps: name: read-object type: read-object outputs: name: cpu valueFrom: output.value.data["cpu"] name: memory valueFrom: output.value.data["memory"] properties: apiVersion: v1 kind: ConfigMap name: my-cm-name cluster: <your cluster name name: apply type: apply-component inputs: from: cpu parameterKey: cpu from: memory parameterKey: memory properties: component: express-server ```
Project: StarRocks (App Definition and Development / Database)
File: array_cum_sum.md

displayed_sidebar: "English" Returns the cumulative sums of elements in an array. ```Haskell arraycumsum(array(bigint)) arraycumsum(array(double)) ``` `array`: The elements in the array must be of the BIGINT (8-byte signed integer) or DOUBLE (8-byte floating-point number) type. Returns an array. NULL is returned if the input array is NULL. Example 1: Return the cumulative sums of an array. ```Plain select arraycumsum([11, 11, 12]); ++ | arraycumsum([11,11,12]) | ++ | [11,22,34] | ++ ``` Example 2: Use this function with CAST. ```Plain select arraycumsum([cast(11.33 as double),cast(11.11 as double),cast(12.324 as double)]); ++ | arraycumsum([CAST(11.33 AS DOUBLE), CAST(11.11 AS DOUBLE), CAST(12.324 AS DOUBLE)]) | ++ | [11.33,22.439999999999998,34.763999999999996] | ++ ``` Example 3: The input array contains a null. ```Plain select arraycumsum([null,1,2]); ++ | arraycumsum([null,1,2]) | ++ | [null,1,3] | ++ ``` Example 4: The input array is null. ```Plain select arraycumsum(null); ++ | arraycumsum(NULL) | ++ | NULL | ++ ```
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v1.0.1.md

Fixed race condition in actor reminders (https://github.com/dapr/dapr/issues/2705) Added etag support to MongoDB state store describes how actor reminders can fail to persist when deleted with concurrent updates. It means that if there are multiple reminders for the same actor type being registered or unregistered at the same time, an update might be overwritten by another update. The root cause was that all instances for a given actor type shares the same record in the database to keep track of the list of registered reminders. Concurrent updates to this list were not done atomically. The fix uses `eTag` feature in state stores in Dapr to only update if etag is unchanged from the time it was last read and avoid race conditions. With this fix, states stores must be transactional and support eTag in order to be used as actors' state store. The only transactional state store in Dapr that did not have eTag support was MongoDB but that is being added in this hotfix as well. The issue was fixed with the following pull requests: https://github.com/dapr/components-contrib/pull/734 https://github.com/dapr/components-contrib/pull/736 https://github.com/dapr/dapr/pull/2873 https://github.com/dapr/dapr/pull/2877 In addition, the changes above also include a new E2E test scenario reproducing the issue to avoid future regressions. Note: Applications using MongoDB as state store for actors can safely upgrade to this version since the eTag will be added automatically on the first update to actors' reminders.
Project: KICS (Provisioning / Security & Compliance)
File: d25edb51-07fb-4a73-97d4-41cecdc53a22.md

title: Glue With Vulnerable Policy hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d25edb51-07fb-4a73-97d4-41cecdc53a22 Query name: Glue With Vulnerable Policy Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Glue policy should avoid wildcard in 'principals' and 'actions'<br> ```tf title="Positive test num. 1 - tf file" hl_lines="15" data "awsiampolicy_document" "glue-example-policy" { statement { actions = [ "glue:*", ] resources = ["arn:data.awspartition.current.partition:glue:data.awsregion.current.name:data.awscalleridentity.current.account_id:*"] principals { identifiers = ["*"] type = "AWS" } } } resource "awsglueresource_policy" "example" { policy = data.awsiampolicy_document.glue-example-policy.json } ``` ```tf title="Negative test num. 1 - tf file" data "awsiampolicy_document" "glue-example-policy2" { statement { actions = [ "glue:CreateTable", ] resources = ["arn:data.awspartition.current.partition:glue:data.awsregion.current.name:data.awscalleridentity.current.account_id:*"] principals { identifiers = ["arn:aws:iam::var.accountid:saml-provider/var.providername"] type = "AWS" } } } resource "awsglueresource_policy" "example2" { policy = data.awsiampolicy_document.glue-example-policy2.json } ```
Project: StarRocks (App Definition and Development / Database)
File: build_starrocks_on_ubuntu.md

displayed_sidebar: "English" This topic describes how to compile StarRocks on the Ubuntu operating system. StarRocks supports compilation on both x86_64 and AArch64 architectures. Run the following commands to install necessary dependencies: ```bash sudo apt-get update ``` ``` sudo apt-get install automake binutils-dev bison byacc ccache flex libiberty-dev libtool maven zip python3 python-is-python3 bzip2 -y ``` If you are using Ubuntu 22.04 or later, run the following command to install the tools and compilers: ```bash sudo apt-get install cmake gcc g++ default-jdk -y ``` If you are using an Ubuntu version earlier than 22.04, run the following commands to check the versions of tools and compilers: Check GCC/G++ versions: ```bash gcc --version g++ --version ``` GCC/G++ versions must be 10.3 or later. If you are using earlier versions, . Check JDK version: ```bash java --version ``` OpenJDK version must be 8 or later. If you are using an earlier version, . Check CMake version: ```bash cmake --version ``` CMake version must be 3.20.1 or later. If you are using an earlier version, . Run the following command to start the compilation: ```bash ./build.sh ``` The default compilation parallelism is equal to CPU core count/4. Assuming you have 32 CPU cores, the default parallelism is 8. If you want to adjust the parallelism, you can specify the number of CPU cores to be used for compilation via `-j` in the command line. The following example uses 24 CPU cores for compilation: ```bash ./build.sh -j 24 ``` Q: Building `awscppsdk` fails on Ubuntu 20.04 with the error "Error: undefined reference to pthread_create". How can I resolve this? A: This error occurs due to a lower version of CMake. Please upgrade CMake to version 3.20.1 or above.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.7.3.md

RabbitMQ `3.7.3` is a patch release with some bug fixes and enhancements. This release has no known incompatibilities with earlier 3.7.x versions. See upgrade and compatibility notes if upgrading from an earlier release. See the for general documentation on upgrades. See for release notes of other releases. Logging to `amq.rabbitmq.log` exchange is available again as a logging mechanism. Note that the user must opt-in by setting `log.exchange = true` in the . GitHub issue: During node boot, the logger will temporarily accept a much higher maximum rate so that no messages are dropped. GitHub issue: Plugin activation could hang if a plugin's channel interceptor failed to activate with an exception. GitHub issue: During node boot, virtual host that are not yet initialised could be queried for status, which resulted in log noise. GitHub issue: will now prohibit logins with blank passwords. Such attempts are usually made by mistake because a passwordless user that was meant to authenticate using was not configured to use the correct [authentication mechanism](https://www.rabbitmq.com/authentication.html). Note that the same behavior can already be achieved using a , so this is just an extra safety measure. GitHub issue: Definition import now stores global parameters in a way that the MQTT plugin expects. GitHub issue: User update form now successfully updates tags for passwordless users (or if the password is cleared at the same time). GitHub issue: Requeue is now the default option in the Get Messages section. Contributed by @dparkinson. GitHub issue: For , the "no password" option on the user editing form is now preselected. GitHub issue: More config keys are now supported via . GitHub issue: When a node registers with Consul it will now set its initial health check status to `passing`. Previously the node would be in the `critical` state until it first reported its health for the first time (in 15 seconds with default settings), which could prevent its peers from discovering it. Kudos to @andersenleo for investigating this issue and recommending a solution. GitHub issue: CLI tools honor `RABBITMQCTLERL_ARGS` again. GitHub issue: Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-3.7.3.tar.gz`.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_target_http_proxies.md

+++ title = "googlecomputetargethttpproxies resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputetargethttpproxies" identifier = "inspec/resources/gcp/googlecomputetargethttpproxies.md googlecomputetargethttpproxies resource" parent = "inspec/resources/gcp" +++ A `googlecomputetargethttpproxies` is used to test a Google TargetHttpProxy resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputetargethttpproxies(project: 'chef-gcp-inspec') do its('names') { should include 'inspec-gcp-http-proxy' } its('descriptions') { should include 'A HTTP proxy' } end ``` Properties that can be accessed from the `googlecomputetargethttpproxies` resource: See the resource for more information. `creation_timestamps` : an array of `googlecomputetargethttpproxy` creation_timestamp `descriptions` : an array of `googlecomputetargethttpproxy` description `ids` : an array of `googlecomputetargethttpproxy` id `names` : an array of `googlecomputetargethttpproxy` name `url_maps` : an array of `googlecomputetargethttpproxy` url_map 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: KICS (Provisioning / Security & Compliance)
File: 8e75e431-449f-49e9-b56a-c8f1378025cf.md

title: Role Assignment Not Limit Guest User Permissions hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8e75e431-449f-49e9-b56a-c8f1378025cf Query name: Role Assignment Not Limit Guest User Permissions Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Role Assignment should limit guest user permissions<br> ```tf title="Positive test num. 1 - tf file" hl_lines="20" resource "azurermroledefinition" "example" { name = "my-custom-role" scope = data.azurerm_subscription.primary.id description = "This is a custom role created via Terraform" permissions { actions = ["*"] not_actions = [] } assignable_scopes = [ data.azurerm_subscription.primary.id, ] } resource "azurermroleassignment" "example" { name = "00000000-0000-0000-0000-000000000000" scope = data.azurerm_subscription.primary.id roledefinitionname = "Guest" roledefinitionid = azurermroledefinition.example.roledefinitionresource_id principalid = data.azurermclientconfig.example.objectid } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermroledefinition" "example2" { name = "my-custom-role" scope = data.azurerm_subscription.primary.id description = "This is a custom role created via Terraform" permissions { actions = [] not_actions = ["*"] } assignable_scopes = [ data.azurerm_subscription.primary.id, ] } resource "azurermroleassignment" "example2" { name = "00000000-0000-0000-0000-000000000000" scope = data.azurerm_subscription.primary.id roledefinitionname = "Guest" roledefinitionid = azurermroledefinition.example2.roledefinitionresource_id principalid = data.azurermclientconfig.example.objectid } ```
Project: YDB (App Definition and Development / Database)
File: copy.md

Using the `tools copy` subcommand, you can create a copy of a DB table. General command format: ```bash {{ ydb-cli }} [global options...] tools copy [options...] ``` `global options`: . `options`: . View a description of the command to copy a table: ```bash {{ ydb-cli }} tools copy --help ``` | Parameter name | Parameter description | | | | | `--client-timeout <value>` | Client side operation timeout, ms. | | `--operation-timeout <value>` | Server side operation timeout, ms. | | `--cancel-after <value>` | Operation lifetime, after which the operation is canceled, ms. | | `--item <value>=<value>,...` | Operation parameters. Possible values:<br/><ul><li>`destination`, `dst`, or `d` required parameter, the path of the destination table. If the destination path contains folders, they must be created in advance. The table with the destination name should not exist.</li><li>`source`, `src`, or `s` required parameter, the path of the source table.</li></ul> | Create the `backup` folder in the DB: ```bash {{ ydb-cli }} scheme mkdir backup ``` Copy the `seasons` table to the `seasons-v1` table in the `backup` folder: ```bash {{ ydb-cli }} tools copy \ --item destination=backup/seasons-v1,source=seasons ``` View the listing of objects in the `backup` folder: ```bash {{ ydb-cli }} scheme ls backup ``` Result: ```text seasons-v1 ```
Project: KICS (Provisioning / Security & Compliance)
File: adcd0082-e90b-4b63-862b-21899f6e6a48.md

title: Security Groups With Meta IP hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: adcd0082-e90b-4b63-862b-21899f6e6a48 Query name: Security Groups With Meta IP Platform: CloudFormation Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: Security Groups allows 0.0.0.0/0 for all ports and protocols.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="19" Resources: Ec2Instance: Type: 'AWS::EC2::Instance' Properties: SecurityGroups: !Ref InstanceSecurityGroup KeyName: mykey ImageId: '' InstanceSecurityGroup: Type: AWS::EC2::SecurityGroup Properties: GroupDescription: Allow http to client host VpcId: Ref: myVPC SecurityGroupIngress: IpProtocol: tcp FromPort: 0 ToPort: 65535 CidrIp: 0.0.0.0/0 SecurityGroupEgress: IpProtocol: tcp FromPort: 80 ToPort: 80 CidrIp: 0.0.0.0/0 ``` ```json title="Positive test num. 2 - json file" hl_lines="24" { "Resources": { "Ec2Instance": { "Properties": { "SecurityGroups": [ "InstanceSecurityGroup" ], "KeyName": "mykey", "ImageId": "" }, "Type": "AWS::EC2::Instance" }, "InstanceSecurityGroup": { "Type": "AWS::EC2::SecurityGroup", "Properties": { "GroupDescription": "Allow http to client host", "VpcId": { "Ref": "myVPC" }, "SecurityGroupIngress": [ { "FromPort": 0, "ToPort": 65535, "CidrIp": "0.0.0.0/0", "IpProtocol": "tcp" } ], "SecurityGroupEgress": [ { "IpProtocol": "tcp", "FromPort": 80, "ToPort": 80, "CidrIp": "0.0.0.0/0" } ] } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: Ec2Instance: Type: 'AWS::EC2::Instance' Properties: SecurityGroups: !Ref InstanceSecurityGroup KeyName: mykey ImageId: '' InstanceSecurityGroup: Type: AWS::EC2::SecurityGroup Properties: GroupDescription: Allow http to client host VpcId: Ref: myVPC SecurityGroupIngress: IpProtocol: tcp FromPort: 80 ToPort: 80 CidrIp: 127.0.0.1/32 SecurityGroupEgress: IpProtocol: tcp FromPort: 80 ToPort: 80 CidrIp: 127.0.0.1/33 ``` ```json title="Negative test num. 2 - json file" { "Resources": { "Ec2Instance": { "Properties": { "SecurityGroups": [ "InstanceSecurityGroup" ], "KeyName": "mykey", "ImageId": "" }, "Type": "AWS::EC2::Instance" }, "InstanceSecurityGroup": { "Type": "AWS::EC2::SecurityGroup", "Properties": { "GroupDescription": "Allow http to client host", "VpcId": { "Ref": "myVPC" }, "SecurityGroupIngress": [ { "ToPort": 80, "CidrIp": "127.0.0.1/32", "IpProtocol": "tcp", "FromPort": 80 } ], "SecurityGroupEgress": [ { "IpProtocol": "tcp", "FromPort": 80, "ToPort": 80, "CidrIp": "127.0.0.1/33" } ] } } } } ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_alert_list-receivers.md

title: kbcli alert list-receivers List all alert receivers. ``` kbcli alert list-receivers [flags] ``` ``` kbcli alert list-receivers ``` ``` -h, --help help for list-receivers ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Manage alert receiver, include add, list and delete receiver.