cwielenb/CNCF-Dataset huggingface dataset:
Project: VMClarity (Provisioning / Security & Compliance)
File: command_line.md

``` ./cli/bin/vmclarity-cli scan --config ~/testConf.yaml -o outputfile ``` If we want to report results to the VMClarity backend, we need to create asset and asset scan object before scan because it requires asset-scan-id ``` ASSET_ID=$(./cli/bin/vmclarity-cli asset-create --file assets/dir-asset.json --server http://localhost:8080/api) --jsonpath {.id} ASSETSCANID=$(./cli/bin/vmclarity-cli asset-scan-create --asset-id $ASSET_ID --server http://localhost:8080/api) --jsonpath {.id} ./cli/bin/vmclarity-cli scan --config ~/testConf.yaml --server http://localhost:8080/api --asset-scan-id $ASSETSCANID ``` Using one-liner: ``` ./cli/bin/vmclarity-cli asset-create --file docs/assets/dir-asset.json --server http://localhost:8080/api --update-if-exists --jsonpath {.id} | xargs -I{} ./cli/bin/vmclarity-cli asset-scan-create --asset-id {} --server http://localhost:8080/api --jsonpath {.id} | xargs -I{} ./cli/bin/vmclarity-cli scan --config ~/testConf.yaml --server http://localhost:8080/api --asset-scan-id {} ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 52_transform_service.md

Prompt: What is Transform service in Apache Beam? Response: The Transform service is a service included in Apache Beam SDK versions 2.49.0 and later. It enables you to upgrade or downgrade the Beam SDK version of individual supported transforms in your pipeline without changing the overall Beam version of the pipeline. Additionally, you can utilize the Transform service to create and execute multi-language pipelines without needing to install support for additional language runtimes. You can utilize the Transform service to upgrade specific transforms only if you are using Beam Java SDK 2.53.0 and later. To employ this feature, execute a Java pipeline with additional pipeline options specifying the URNs of the transforms you want to upgrade and the desired Apache Beam version: ```java --transformsToOverride=beam:transform:org.apache.beam:bigquery_read:v1 --transformServiceBeamVersion=2.xy.z ``` In the provided example, `--transformsToOverride` specifies the URN of the transform to upgrade or downgrade, while `--transformServiceBeamVersion` specifies the target Beam version. The framework automatically downloads the specified version of Docker containers for the transforms and uses them in the pipeline. You must have Docker installed on the machine that starts the service. Currently, the Transform service can upgrade the following transforms: BigQuery read: `beam:transform:org.apache.beam:bigquery_read:v1` BigQuery write: `beam:transform:org.apache.beam:bigquery_write:v1` Kafka read: `beam:transform:org.apache.beam:kafkareadwith_metadata:v2` Kafka write: `beam:transform:org.apache.beam:kafka_write:v2` The Transform service implements the Beam expansion API, enabling multi-language pipelines to leverage it for expanding supported transforms. This feature allows you to create and run multi-language pipelines without additional language runtimes. For instance, you can build a Python pipeline that utilizes a Java `KafkaIO` transform without the need to install Java locally. In some cases, Apache Beam SDKs can start the Transform service automatically, provided that Docker is available locally. You can also start the Transform service manually by running the following command: ```java java -jar beam-sdks-java-transform-service-app-<Beam version for the jar>.jar --port <port> --beamversion <Beam version for the transform service> --projectname <a unique ID for the transform service> --command up ``` The Beam Transform service includes several portable transforms implemented in the Apache Beam Java and Python SDKs: Java transforms: Google Cloud I/O connectors, the Kafka I/O connector, and the JDBC I/O connector. Python transforms: all portable transforms implemented within the Apache Beam Python SDK, such as RunInference and DataFrame transforms.
Project: ClickHouse (App Definition and Development / Database)
File: sumcount.md

slug: /en/sql-reference/aggregate-functions/reference/sumcount sidebar_position: 144 title: sumCount Calculates the sum of the numbers and counts the number of rows at the same time. The function is used by ClickHouse query optimizer: if there are multiple `sum`, `count` or `avg` functions in a query, they can be replaced to single `sumCount` function to reuse the calculations. The function is rarely needed to use explicitly. Syntax ``` sql sumCount(x) ``` Arguments `x` Input value, must be , , or . Returned value Tuple `(sum, count)`, where `sum` is the sum of numbers and `count` is the number of rows with not-NULL values. Type: . Example Query: ``` sql CREATE TABLE s_table (x Int8) Engine = Log; INSERT INTO s_table SELECT number FROM numbers(0, 20); INSERT INTO s_table VALUES (NULL); SELECT sumCount(x) from s_table; ``` Result: ``` text sumCount(x) (190,20) ``` See also setting.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-12418.en.md

For JWT authentication, the claims to verify now may be provided as a list of maps: ``` [ { name = "claim_name" value = "${username}" }, ... ] ``` Expected values now treated as templates, uniformly with the oither authenticators. They now allow arbitrary expressions including `${username}` and `${clientid}` variables. Previousy, only fixed `"${username}"` `"${clientid}"` values were supported for interpolation. Improved the documentation for the `verify_claims` parameter.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_report_cluster.md

title: kbcli report cluster Report Cluster information ``` kbcli report cluster NAME [-f file] [-with-logs] [-mask] [flags] ``` ``` kbcli report cluster mycluster kbcli report cluster mycluster -f filename kbcli report cluster mycluster --with-logs kbcli report cluster mycluster --with-logs --mask kbcli report cluster mycluster --with-logs --since 1h kbcli report cluster mycluster --with-logs --since-time 2023-05-23T00:00:00Z kbcli report cluster mycluster --with-logs --all-containers ``` ``` --all-containers Get all containers' logs in the pod(s). Byt default, only the main container (the first container) will have logs recorded. -f, --file string zip file for output -h, --help help for cluster --mask mask sensitive info for secrets and configmaps (default true) -o, --output string Output format. One of: json|yaml. (default "json") --since duration Only return logs newer than a relative duration like 5s, 2m, or 3h. Defaults to all logs. Only one of since-time / since may be used. --since-time string Only return logs after a specific date (RFC3339). Defaults to all logs. Only one of since-time / since may be used. --with-logs include pod logs ``` ``` --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 ``` - report kubeblocks or cluster info.
Project: Meshery (Provisioning / Automation & Configuration)
File: pulsar-resources-operator.md

layout: integration title: Pulsar Resources Operator subtitle: Collaborative and visual infrastructure as code for Pulsar Resources Operator image: /assets/img/integrations/pulsar-resources-operator/icons/color/pulsar-resources-operator-color.svg permalink: extensibility/integrations/pulsar-resources-operator docURL: https://docs.meshery.io/extensibility/integrations/pulsar-resources-operator description: integrations-category: App Definition and Development integrations-subcategory: Streaming & Messaging registrant: Artifact Hub components: name: pulsar-connection colorIcon: assets/img/integrations/pulsar-resources-operator/components/pulsar-connection/icons/color/pulsar-connection-color.svg whiteIcon: assets/img/integrations/pulsar-resources-operator/components/pulsar-connection/icons/white/pulsar-connection-white.svg description: name: pulsar-namespace colorIcon: assets/img/integrations/pulsar-resources-operator/components/pulsar-namespace/icons/color/pulsar-namespace-color.svg whiteIcon: assets/img/integrations/pulsar-resources-operator/components/pulsar-namespace/icons/white/pulsar-namespace-white.svg description: name: pulsar-permission colorIcon: assets/img/integrations/pulsar-resources-operator/components/pulsar-permission/icons/color/pulsar-permission-color.svg whiteIcon: assets/img/integrations/pulsar-resources-operator/components/pulsar-permission/icons/white/pulsar-permission-white.svg description: name: pulsar-tenant colorIcon: assets/img/integrations/pulsar-resources-operator/components/pulsar-tenant/icons/color/pulsar-tenant-color.svg whiteIcon: assets/img/integrations/pulsar-resources-operator/components/pulsar-tenant/icons/white/pulsar-tenant-white.svg description: name: pulsar-topic colorIcon: assets/img/integrations/pulsar-resources-operator/components/pulsar-topic/icons/color/pulsar-topic-color.svg whiteIcon: assets/img/integrations/pulsar-resources-operator/components/pulsar-topic/icons/white/pulsar-topic-white.svg description: name: pulsar-geo-replication colorIcon: assets/img/integrations/pulsar-resources-operator/components/pulsar-geo-replication/icons/color/pulsar-geo-replication-color.svg whiteIcon: assets/img/integrations/pulsar-resources-operator/components/pulsar-geo-replication/icons/white/pulsar-geo-replication-white.svg description: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_test.Common.BeforeOptions.md

/ / / BeforeOptions ..BeforeOptions `Optional` noApp: `boolean` `Optional` noProxySessionWait: `boolean` `Optional` popup: `string`[] `Optional` afterStart(): `Promise`<`void`\> `Promise`<`void`\> `Optional` beforeStart(): `Promise`<`void`\> `Promise`<`void`\>
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v0.3.0.md

We're happy to announce the release of Dapr 0.3.0. This release focused on improvements to our , making Service Discovery into pluggable components to support more hosting platforms, adding a few new components, improving CLI error messages and stability, and resolving bugs on and improving the Dotnet SDK. Visit the page to get started with Dapr. To get the latest bits, follow the instructions to download the latest and greatest CLI release and binaries. Once you have the Dapr CLI in your path: ``` dapr uninstall --all dapr init ``` Wait for the update to finish, and you're good to go! If you previously installed Dapr on your Kubernetes cluster using the Dapr CLI, first download the latest CLI release as outlined above. Once you have the CLI, run: ``` dapr uninstall --kubernetes dapr init --kubernetes ``` If installed Dapr previously via Helm, run the following command to upgrade: ``` helm upgrade dapr dapr/dapr --set global.tag=0.3.0 ``` Note: If you installed with a different chart name, use `helm upgrade <your-chart-name>` Decoupled Service Discovery from the runtime by making discovery a pluggable component Added as a Pub/Sub Message Bus Improved Error message for unsupported state store for actors Improved Go import statements Improved End-To-End tests infrastructure and helper utils Added End-To-End state management tests Added End-To-End bindings tests Added Flags to be presented as environment variables Changed Name of `send` command to `invoke` Added The ability to choose an installation path for Dapr binaries Improved Error message when Docker isn't running Fixed Unregister timer error Added Serialization of ReminderInfo and Timer Added Ability for actor type to be specified during registration Changed Stylecop.Analyzers to be a private dependency Fixed Hello World node sample hanging if a state store isn't enabled Improved Structure for Hello World and Hello World Kubernetes
Project: Artifact Hub (App Definition and Development / Application Definition & Image Build)
File: knative_client_plugins_repositories.md

Knative client plugins repositories are expected to be hosted in GitHub, GitLab or Bitbucket repos. When adding your repository to Artifact Hub, the url used must follow the following format: `https://github.com/user/repo[/path/to/packages]` `https://gitlab.com/user/repo[/path/to/packages]` `https://bitbucket.org/user/repo[/path/to/packages]` By default the `master` branch is used, but it's possible to specify a different one from the UI. Please NOTE that the repository URL used when adding the repository to Artifact Hub must NOT contain the git hosting platform specific parts, like tree/branch, just the path to your packages like it would show in the filesystem. The path/to/packages provided can contain metadata for one or more packages. Each package version must be on a separate folder, and it's up to you to decide if you want to publish one or multiple versions of your package. The structure of a repository with multiple plugins packages and versions could look something like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 1.0.0 README.md artifacthub-pkg.yml 2.0.0 README.md artifacthub-pkg.yml package2 1.0.0 README.md artifacthub-pkg.yml ``` This structure is flexible, and in some cases it can be greatly simplified. In the case of a single package with a single version available at a time (the publisher doesn't want to make previous ones available, for example), the structure could look like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 README.md artifacthub-pkg.yml ``` In the previous case, even the `package1` directory could be omitted. The reason is that both packages names and versions are read from the `artifacthub-pkg.yml` metadata file, so directories names are not used at all. Each package version needs an `artifacthub-pkg.yml` metadata file. Please see the file for more details. The repository metadata file shown above can be used to setup features like or . This file must be located at `/path/to/packages`. Once you have added your repository, you are all set up. As you add new versions of your plugins packages or even new packages to your git repository, they'll be automatically indexed and listed in Artifact Hub.
Project: CockroachDB (App Definition and Development / Database)
File: nodes-request.md

<a name="cockroach.server.serverpb.NodesRequest"></a> NodesRequest requests a copy of the node information as known to gossip and the KV layer. Support status: | Field | Type | Label | Description | Support status | | -- | - | -- | -- | -- | | redact | | | redact, if true, requests redaction of sensitive data away from the API response. | |
Project: Harbor (Provisioning / Container Registry)
File: Test-10-12-Scan-image-on-push.md

Test 10-12 Scan Image on Push ======= To verify that trivy can automatic scan image when image is pushed. User guide This test requires that a Harbor instance is running and available. Harbor is installed with trivy enable. A linux host with Docker CLI installed. Trivy has been updated to the latest. Login Harbor as admin. Create a new project. Goto project configuration page. Enable automatically scan. Push an image not scanned before to the project. Step5 image should be scanned automatically.
Project: YugabyteDB (App Definition and Development / Database)
File: tsrangebytime.md

title: TSRANGEBYTIME linkTitle: TSRANGEBYTIME description: TSRANGEBYTIME menu: preview: parent: api-yedis weight: 2440 aliases: /preview/api/redis/tsrangebytime /preview/api/yedis/tsrangebytime type: docs `TSRANGEBYTIME key low_ts high_ts` This command fetches the values for the given `lowts`, `hights` range in the time series that is specified by the given `key`. If the given `key` is associated with non-time series data, an error is raised. If the given `lowts` or `hights` are not a valid signed 64 bit integers, an error is raised. `lowts` and `hights` are inclusive unless they are prefixed with `(`, in that case they are exclusive. Special bounds `-inf` and `+inf` are also supported to retrieve an entire range Returns a list of timestamp, value pairs found in the range specified by `lowts`, `hights`. You can do this as shown below. ```sh TSADD ts 1 one 2 two 3 three 4 four 5 five 6 six ``` ``` "OK" ``` ```sh TSRANGEBYTIME ts_key 2 4 ``` ``` 1) "2" 2) "two" 3) "3" 4) "three" 5) "4" 6) "four" ``` 2 is exclusive ```sh TSRANGEBYTIME ts_key (2 4 ``` ``` 1) "3" 2) "three" 3) "4" 4) "four" ``` 2 and 4 are exclusive ```sh TSRANGEBYTIME ts_key (2 (4 ``` ``` 1) "3" 2) "three" ``` ```sh TSRANGEBYTIME ts_key -inf 3 ``` ``` 1) "1" 2) "one" 3) "2" 4) "two" 5) "3" 6) "three" ``` ```sh TSRANGEBYTIME ts_key 2 +inf ``` ``` 1) "2" 2) "two" 3) "3" 4) "three" 5) "4" 6) "four" 7) "5" 8) "five" 9) "6" 10) "six" ``` , , , , ,
Project: YDB (App Definition and Development / Database)
File: union_all.md

Concatenating results of multiple `SELECT` statements (or subqueries). Two `UNION ALL` modes are supported: by column names (the default mode) and by column positions (corresponds to the ANSI SQL standard and is enabled by the ). In the "by name" mode, the output of the resulting data schema uses the following rules: {% include %} The order of output columns in this mode is equal to the largest common prefix of the order of inputs, followed by all other columns in the alphabetic order. If the largest common prefix is empty (for example, if the order isn't specified for one of the inputs), then the output order is undefined. In the "by position" mode, the output of the resulting data schema uses the following rules: All inputs must have equal number of columns The order of columns must be defined for all inputs The names of the resulting columns must match the names of columns in the first table The type of the resulting columns is output as a common (widest) type of input column types having the same positions The order of the output columns in this mode is the same as the order of columns in the first input. Examples ```yql SELECT 1 AS x UNION ALL SELECT 2 AS y UNION ALL SELECT 3 AS z; ``` In the default mode, this query returns a selection with three columns x, y, and z. When `PRAGMA PositionalUnionAll;` is enabled, the selection only includes the x column. ```yql PRAGMA PositionalUnionAll; SELECT 1 AS x, 2 as y UNION ALL SELECT * FROM ASTABLE([<|x:3, y:4|>]); -- error: the order of columns in ASTABLE is undefined ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.6.14.md

RabbitMQ `3.6.14` is a maintenance release that primarily fixes an issue in systemd unit files that affected some systems. It is virtually identical to otherwise. See the for general documentation on upgrades. This release has no known incompatibilities with versions 3.6.7 through 3.6.13. See the upgrade and compatibility sections in the if upgrading from an earlier release. Please read this node on . systemd service unit no longer has trailing comments that could lead nodes into restart loops on some systems. GitHub issues: Expandable sections on node metrics page failed to expand. GitHub issues: To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained. When upgrading using definitions export/import from versions earlier than 3.6.0, see http://rabbitmq.com/passwords.html. To upgrade a RabbitMQ cluster, follow the instructions . 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.6.13.tar.gz`.
Project: KICS (Provisioning / Security & Compliance)
File: b90033cf-ad9f-4fb9-acd1-1b9d6d278c87.md

title: Multiple Body Parameters In The Same Operation hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b90033cf-ad9f-4fb9-acd1-1b9d6d278c87 Query name: Multiple Body Parameters In The Same Operation Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Structure and Semantics URL: Only one body parameter is allowed on operation's parameters type field<br> ```json title="Positive test num. 1 - json file" hl_lines="10" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "parameters": [ { "name": "limit", "in": "body", "description": "max records to return", "required": true, "schema": { "type": "integer" } }, { "name": "limit2", "in": "body", "description": "max records to return", "required": true, "schema": { "type": "string" } } ], "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } } } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="8" swagger: '2.0' info: title: Simple API Overview version: 1.0.0 paths: "/": get: parameters: name: limit in: body description: max records to return required: true schema: type: integer name: limit2 in: body description: max records to return required: true schema: type: string operationId: listVersionsv2 summary: List API versions responses: '200': description: 200 response ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "parameters": [ { "name": "limit", "in": "body", "description": "max records to return", "required": true, "schema": { "type": "integer" } }, { "name": "pageCount", "in": "query", "description": "records per page", "required": true, "schema": { "type": "integer" } } ], "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } } } } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: '2.0' info: title: Simple API Overview version: 1.0.0 paths: "/": get: parameters: name: limit in: body description: max records to return required: true schema: type: integer name: pageCount in: query description: records per page required: true schema: type: integer operationId: listVersionsv2 summary: List API versions responses: '200': description: 200 response ```