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

Manage YugabyteDB Anywhere onprem node instances Manage YugabyteDB Anywhere on-premises node instances ``` yba provider onprem node [flags] ``` ``` -h, --help help for node ``` ``` -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") -n, --name string [Optional] The name of the provider for the action. Required for create, delete, describe, instance-types and nodes. -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 a YugabyteDB Anywhere on-premises provider - Add a node instance to YugabyteDB Anywhere on-premises provider - List node instances of a YugabyteDB Anywhere on-premises provider - Preflight check a node of a YugabyteDB Anywhere on-premises provider - Delete node of a YugabyteDB Anywhere on-premises provider
Project: ShardingSphere (App Definition and Development / Database)
File: show-shadow-table-rule.en.md

+++ title = "SHOW SHADOW TABLE RULES" weight = 2 +++ The `SHOW SHADOW TABLE RULES` syntax is used to query shadow table rules for specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowEncryptRule::= 'SHOW' 'SHADOW' 'TABLE' 'RULES' ('FROM' databaseName)? databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When `databaseName` is not specified, the default is the currently used `DATABASE`. If `DATABASE` is not used, `No database selected` will be prompted. | Column | Description | |--|--| | shadow_table | Shadow table | | shadowalgorithmname | Shadow algorithm name | Query shadow table rules for specified database. ```sql SHOW SHADOW TABLE RULES FROM shadow_db; ``` ```sql mysql> SHOW SHADOW TABLE RULES FROM shadow_db; +--+-+ | shadowtable | shadowalgorithm_name | +--+-+ | torderitem | shadowruletorderitemvaluematch | | torder | sqlhintalgorithm,shadowruletorderregexmatch | +--+-+ 2 rows in set (0.00 sec) ``` Query shadow table rules for current database. ```sql SHOW SHADOW TABLE RULES; ``` ```sql mysql> SHOW SHADOW TABLE RULES; +--+-+ | shadowtable | shadowalgorithm_name | +--+-+ | torderitem | shadowruletorderitemvaluematch | | torder | sqlhintalgorithm,shadowruletorderregexmatch | +--+-+ 2 rows in set (0.01 sec) ``` `SHOW`, `SHADOW`, `TABLE`, `RULES`, `FROM`
Project: Athenz (Provisioning / Key Management)
File: zms_api.md

The Authorization Management Service (ZMS) API This API has the following attributes: | Attribute | Value | | |-| | namespace | com.yahoo.athenz.zms | | version | 1 | All ZMS API commands require that the client use a TLS certificate issued by Athenz. Services can use their Athenz Issued Service Identity certificates when communicating with ZMS. Every write request against ZMS server is authorized against the configured policy data to verify that the principal has been given the rights to make the requested change. Each request description below gives the authorization command that includes the action and resource that the ZMS Server will run the authorization check against. For example, the create subdomain command has the following authorize statement: ``` sourceCode authorize ("create", "{parent}:domain"); ``` This indicates that the principal requesting to create subdomain called athens.ci must have grant rights to action "create" for resource called "domain" in domain "athens". Please refer to the
Project: StarRocks (App Definition and Development / Database)
File: SHOW_INDEX.md

displayed_sidebar: "English" This statement is used to show information related to index in a table. It currently only supports bitmap index. :::tip This operation does not require privileges. ::: ```sql SHOW INDEX[ES] FROM [dbname.]tablename [FROM database] Or SHOW KEY[S] FROM [dbname.]tablename [FROM database] ``` Show all indexes under the specified table_name: ```sql SHOW INDEX FROM exampledb.tablename; ```
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: ENG-002-Dapr-Release.md

Proposal This record descibes how to safely release new dapr binaries and the corresponding configurations without any blockers to users. Integration build refers to the build from `master` branch once we merge PullRequest to master branch. This build will be used for development purposes and must not be released to users and impact their environments. Pre-release build will be built from `release-<major>.<minor>` branch and versioned by git version tag suffix e.g. `-alpha.0`, `-alpha.1`, etc. This build is not released to users who use the latest stable version. Pre-release process Create branch `release-<major>.<minor>` from master and push the branch. e.g. `release-0.1` Add pre-release version tag(with suffix -alpha.0 e.g. v0.1.0-alpha.0) and push the tag ``` $ git tag "v0.1.0-alpha.0" -m "v0.1.0-alpha.0" $ git push --tags ``` CI creates new build and push the images with only version tag Test and validate the functionalities with the specific version If there are regressions and bugs, fix them in release-* branch and merge back to master Create new pre-release version tag(with suffix -alpha.1, -alpha.2, etc) Repeat from 4 to 6 until all bugs are fixed Once all bugs are fixed, we will create the release note under and run CI release manually in order to deliver the stable version to users. We will work on the existing `release-<major>.<minor>` branch to release patch version. Once all bugs are fixed, we will add new patch version tag, such as `v0.1.1-alpha.0`, and then release the build manually. Keep master branch in a working state Deliver the stable version to user safely
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_reset_vars.md

title: "Command - devspace reset vars" sidebar_label: devspace reset vars Resets the current config vars ``` devspace reset vars [flags] ``` ``` Resets the saved variables of the current config Examples: devspace reset vars ``` ``` -h, --help help for vars ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ```
Project: ClickHouse (App Definition and Development / Database)
File: v21.11.2.2-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Skip maxpartitionsizetodrop check in case of ATTACH PARTITION ... FROM and MOVE PARTITION ... (). Backported in : Using `formatRow` function with not row formats led to segfault. Don't allow to use this function with such formats (because it doesn't make sense). (). Backported in : Fix JSONValue/Query with quoted identifiers. This allows to have spaces in json path. Closes . (). Return back accidentally removed code ().
Project: KubeMQ (App Definition and Development / Streaming & Messaging)
File: kubemq_events_store_list.md

Events-Store list of 'events store' channels Events-Store list command allows to get a list of 'events store' channels ``` kubemq events_store list [flags] ``` ``` kubemq events_store list kubemq events_store list -f some-events-store ``` ``` -f, --filter string set filter for channel / client name -h, --help help for list ``` - Execute Kubemq 'Events-Store' Pub/Sub commands
Project: StarRocks (App Definition and Development / Database)
File: approx_top_k.md

displayed_sidebar: "English" Returns the top `k` most frequently occurring item values in an `expr` along with their approximate counts. This function is supported from v3.0. ```Haskell APPROXTOPK(<expr> [ , <k> [ , <counter_num> ] ] ) ``` `expr`: An expression of STRING, BOOLEAN, DATE, DATETIME, or numeric type. `k`: An optional INTEGER literal greater than 0. If `k` is not specified, it defaults to `5`. The maximum value is `100000`. `counternum`: An optional INTEGER literal greater than or equal to `k`, The larger the `counternum` is, the more accurate the result will be. However, this also comes with increased CPU and memory costs. The maximum value is `100000`. If `counter_num` is not specified, it defaults to `max(min(2 * k, 100), 100000)`. Results are returned as an ARRAY of type STRUCT, where each STRUCT contains an `item` field for the value (with its original input type) and a `count` field (of type BIGINT) with the approximate number of occurrences. The array is sorted by `count` descending. The aggregate function returns the top `k` most frequently occurring item values in an expression expr along with their approximate counts. The error in each count may be up to `2.0 * numRows / counternum` where `numRows` is the total number of rows. Higher values of `counternum` provide better accuracy at the cost of increased memory usage. Expressions that have fewer than `counter_num` distinct items will yield exact item counts. Results include `NULL` values as their own item in the results. Use data in the table as an example. ```plaintext -- Calculate the score distribution of each subject. MySQL > SELECT subject, APPROXTOPK(score) AS top_k FROM scores GROUP BY subject; ++--+ | subject | top_k | ++--+ | physics | [{"item":99,"count":2},{"item":null,"count":1},{"item":100,"count":1},{"item":85,"count":1},{"item":60,"count":1}] | | english | [{"item":null,"count":1},{"item":92,"count":1},{"item":98,"count":1},{"item":100,"count":1},{"item":85,"count":1}] | | NULL | [{"item":90,"count":1}] | | math | [{"item":80,"count":2},{"item":null,"count":1},{"item":92,"count":1},{"item":95,"count":1},{"item":70,"count":1}] | ++--+ -- Calculate the score distribution of the math subject. MySQL > SELECT subject, APPROXTOPK(score) AS top_k FROM scores WHERE subject IN ('math') GROUP BY subject; ++-+ | subject | top_k | ++-+ | math | [{"item":80,"count":2},{"item":null,"count":1},{"item":95,"count":1},{"item":92,"count":1},{"item":70,"count":1}] | ++-+ ``` APPROXTOPK
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-aux-show-databases.md

layout: global title: SHOW DATABASES displayTitle: SHOW DATABASES license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Lists the databases that match an optionally supplied regular expression pattern. If no pattern is supplied then the command lists all the databases in the system. Please note that the usage of `SCHEMAS` and `DATABASES` are interchangeable and mean the same thing. ```sql SHOW { DATABASES | SCHEMAS } [ LIKE regex_pattern ] ``` regex_pattern* Specifies a regular expression pattern that is used to filter the results of the statement. Except for `` and `|` character, the pattern works like a regular expression. `` alone matches 0 or more characters and `|` is used to separate multiple different regular expressions, any of which can match. The leading and trailing blanks are trimmed in the input pattern before processing. The pattern match is case-insensitive. ```sql -- Create database. Assumes a database named `default` already exists in -- the system. CREATE DATABASE payroll_db; CREATE DATABASE payments_db; -- Lists all the databases. SHOW DATABASES; ++ |databaseName| ++ | default| | payments_db| | payroll_db| ++ -- Lists databases with name starting with string pattern `pay` SHOW DATABASES LIKE 'pay*'; ++ |databaseName| ++ | payments_db| | payroll_db| ++ -- Lists all databases. Keywords SCHEMAS and DATABASES are interchangeable. SHOW SCHEMAS; ++ |databaseName| ++ | default| | payments_db| | payroll_db| ++ ```
Project: Notary (Provisioning / Security & Compliance)
File: README.md

The package implement a simple plugin for Notation plugin extensibility E2E test. It support following commands: get-plugin-metadata (the plugin information) describe-key (the keySpec) generate-signature (signing a payload with protected data) generate-envelope (signing a payload with a descriptor and generate the envelope) verify-signature (fake verifier for testing the plugin protocol) the `SIGNATUREGENERATOR.RAW` and `SIGNATUREGENERATOR.ENVELOPE` capabilities are hidden by default. `SIGNATUREVERIFIER.TRUSTEDIDENTITY` and `SIGNATUREVERIFIER.REVOCATIONCHECK` are shown all the time in the response of `get-plugin-metadata` command. You can enable one of signing capability by passing the enable flag in PluginConfig for `get-plugin-metadata` command: ```json { "pluginConfig": { "SIGNATURE_GENERATOR.RAW": "true" } } ``` Notation only uses one of `SIGNATUREGENERATOR.RAW` or `SIGNATUREGENERATOR.ENVELOPE` capability for a signing operation. It reads the $NOTATIONCONFIGDIR/pluginkeys.json to get the key and cert info. example pluginkey.json file ```json { "keys": [ { "name": "e2e", "id": "keyid", "keyPath": "/home/username/.config/notation/localkeys/e2e.key", "certPath": "/home/username/.config/notation/localkeys/e2e.crt" } ] } ```
Project: ShardingSphere (App Definition and Development / Database)
File: alter-traffic-rule.en.md

+++ title = "ALTER TRAFFIC RULE" weight = 7 +++ The `ALTER TRAFFIC RULE` syntax is used to alter dual routing rule. {{< tabs >}} {{% tab name="Grammar" %}} ```sql AlterTrafficRule ::= 'ALTER' 'TRAFFIC' 'RULE' '(' 'LABELS' '(' lableName ')' ',' trafficAlgorithmDefinition ',' loadBalancerDefinition ')' lableName ::= identifier trafficAlgorithmDefinition ::= 'TRAFFIC_ALGORITHM' '(' 'TYPE' '(' 'NAME' '=' trafficAlgorithmTypeName (',' propertiesDefinition)? ')' ')' loadBalancerDefinition ::= 'LOAD_BALANCER' '(' 'TYPE' '(' 'NAME' '=' loadBalancerName (',' propertiesDefinition)? ')' ')' propertiesDefinition ::= 'PROPERTIES' '(' key '=' value (',' key '=' value)* ')' trafficAlgorithmTypeName ::= string loadBalancerTypeName ::= string key ::= string value ::= literal ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} `TRAFFICALGORITHM` support `SQLMATCH` and `SQL_HINT` two types; `LOADBALANCER` support `RANDOM` and `ROUNDROBIN` two types. Alter dual routing rule ```sql TRAFFIC RULE sqlmatchtraffic ( LABELS (OLTP), TRAFFICALGORITHM(TYPE(NAME="SQLMATCH",PROPERTIES("sql" = "SELECT * FROM torder WHERE orderid = 1; UPDATE torder SET orderid = 5;"))), LOAD_BALANCER(TYPE(NAME="RANDOM"))); ``` `ALTER`, `TRAFFIC`, `RULE`, `LABELS`, `TYPE`, `NAME`, `PROPERTIES`, `TRAFFICALGORITHM`, `LOADBALANCER`
Project: Trivy (Provisioning / Security & Compliance)
File: ruby.md

Trivy supports and . The following scanners are supported for Cargo. | Package manager | SBOM | Vulnerability | License | |--|:-:|:-:|:-:| | Bundler | | | - | | RubyGems | | | | The following table provides an outline of the features Trivy offers. | Package manager | File | Transitive dependencies | Dev dependencies | | Position | |--|--|:--:|:--|::|:--:| | Bundler | Gemfile.lock | | Included | | | | RubyGems | .gemspec | - | Included | - | - | Trivy searches for `Gemfile.lock` to detect dependencies. `.gemspec` files doesn't contains transitive dependencies. You need to scan each `.gemspec` file separately.
Project: KICS (Provisioning / Security & Compliance)
File: 837e033c-4717-40bd-807e-6abaa30161b7.md

title: Stack Notifications Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 837e033c-4717-40bd-807e-6abaa30161b7 Query name: Stack Notifications Disabled Platform: CloudFormation Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: AWS CloudFormation should have stack notifications enabled to be notified when an event occurs<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="5" AWSTemplateFormatVersion: '2010-09-09' Resources: myStackWithParams: Type: AWS::CloudFormation::Stack Properties: TemplateURL: https://s3.amazonaws.com/cloudformation-templates-us-east-2/EC2ChooseAMI.template Parameters: InstanceType: t1.micro KeyName: mykey ``` ```json title="Positive test num. 2 - json file" hl_lines="6" { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "myStackWithParams": { "Type": "AWS::CloudFormation::Stack", "Properties": { "TemplateURL": "https://s3.amazonaws.com/cloudformation-templates-us-east-2/EC2ChooseAMI.template", "Parameters": { "InstanceType": "t1.micro", "KeyName": "mykey" } } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: '2010-09-09' Resources: myStackWithParams: Type: AWS::CloudFormation::Stack Properties: NotificationARNs: "String" TemplateURL: https://s3.amazonaws.com/cloudformation-templates-us-east-2/EC2ChooseAMI.template Parameters: InstanceType: t1.micro KeyName: mykey ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "myStackWithParams": { "Type": "AWS::CloudFormation::Stack", "Properties": { "NotificationARNs": [ "string" ], "TemplateURL": "https://s3.amazonaws.com/cloudformation-templates-us-east-2/EC2ChooseAMI.template", "Parameters": { "InstanceType": "t1.micro", "KeyName": "mykey" } } } } } ```
Project: ClickHouse (App Definition and Development / Database)
File: groupbitor.md

slug: /en/sql-reference/aggregate-functions/reference/groupbitor sidebar_position: 126 Applies bit-wise `OR` for series of numbers. ``` sql groupBitOr(expr) ``` Arguments `expr` An expression that results in `UInt` or `Int` type. Returned value Value of the `UInt` or `Int` type. Example Test data: ``` text binary decimal 00101100 = 44 00011100 = 28 00001101 = 13 01010101 = 85 ``` Query: ``` sql SELECT groupBitOr(num) FROM t ``` Where `num` is the column with the test data. Result: ``` text binary decimal 01111101 = 125 ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: vbscript.md

+++ title = "vbscript resource" draft = false gh_repo = "inspec" platform = "windows" [menu] [menu.inspec] title = "vbscript" identifier = "inspec/resources/os/vbscript.md vbscript resource" parent = "inspec/resources/os" +++ Use the `vbscript` Chef InSpec audit resource to test a VBScript on the Windows platform. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `vbscript` resource block tests the output of a VBScript on the Windows platform: describe vbscript('script contents') do its('stdout') { should eq 'output' } end where `'script_name'` is the name of the VBScript to test `('output')` is the expected output of the VBScript The following examples show how to use this Chef InSpec audit resource. A VBScript file similar to: script = <<-EOH WScript.Echo "hello" EOH may be tested for multiple lines: describe vbscript(script) do its('stdout') { should eq "hello\r\n" } end and tested for whitespace removal from standard output: describe vbscript(script) do its('strip') { should eq "hello" } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_list_commands.md

title: "Command - devspace list commands" sidebar_label: devspace list commands Lists all custom DevSpace commands ``` devspace list commands [flags] ``` ``` Lists all DevSpace custom commands defined in the devspace.yaml ``` ``` -h, --help help for commands ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ```