cwielenb/CNCF-Dataset huggingface dataset:
Project: CDEvents (App Definition and Development / Streaming & Messaging)
File: _index.md

<!-- title: "CDEvents Documentation" linkTitle: "Documentation" weight: 10 menu: main: weight: 20 pre: <i class='fas fa-book'></i> --> <!-- markdownlint-disable-file MD041 --> <!-- cSpell:locale en-US --> Welcome to the CDEvents specification documentation for release {{< param "version" >}}. Here, you can find all the information necessary to understand and implement CDEvents within your application. For those new to CDEvents, we recommend starting with the and the , to help you rapidly understand the concepts. Note that CDEvents builds upon <a href="https://cloudevents.io/" target="_blank">CloudEvents</a>, so it may be helpful to have some understanding of that specification first. To help you get up to speed quickly, we have broken the specification down into bite-sized chunks. The sections below will help you navigate to the information that you need. <br><br> {{% blocks/section type="section" color="white" %}} {{% cardpane %}} {{< blocks/feature icon="fa-solid fa-file-word" title="" >}} The Continuous Delivery Foundation White Paper on CDEvents<br><br> {{< /blocks/feature >}} {{< blocks/feature icon="fa-solid fa-graduation-cap" title="" >}} An introduction to CDEvents and associated concepts<br><br> {{< /blocks/feature >}} {{< blocks/feature icon="fas fa-info-circle" title="" >}} An overview of Metadata common across the CDEvents Specification<br><br> {{< /blocks/feature >}} {{< blocks/feature icon="fa-solid fa-bars-staggered" title="" >}} Definition of specific events that are fundamental to pipeline execution and orchestration<br><br> {{< /blocks/feature >}} {{< blocks/feature icon="fa-solid fa-code-branch" title="" >}} Handling Events relating to changes in version management of Source Code and related assets<br><br> {{< /blocks/feature >}} {{< blocks/feature icon="fa-solid fa-network-wired" title="" >}} Handling Events associated with Continuous Integration activities, typically involving build and test<br><br> {{< /blocks/feature >}} {{< blocks/feature icon="fa-solid fa-satellite-dish" title="" >}} Handling Events associated with Continuous Deployment activities<br><br> {{< /blocks/feature >}} {{< blocks/feature icon="fa-solid fa-arrow-right-arrow-left" title="" >}} Defining how CDEvents are mapped to CloudEvents for transportation and delivery<br><br> {{< /blocks/feature >}} {{< blocks/feature icon="fa-solid fa-rocket-launch" >}} {{< /blocks/feature >}} {{% /cardpane %}} {{% /blocks/section %}}
Project: Beam (App Definition and Development / Streaming & Messaging)
File: syntax.md

type: languages title: "Beam ZetaSQL function call rules" <!-- 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. --> The following rules apply to all functions unless explicitly indicated otherwise in the function description: For functions that accept numeric types, if one operand is a floating point operand and the other operand is another numeric type, both operands are converted to FLOAT64 before the function is evaluated. If an operand is `NULL`, the result is `NULL`, with the exception of the IS operator. For functions that are time zone sensitive (as indicated in the function description), the default time zone, UTC, is used if a time zone is not specified.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: userns.pod.md

Set the user namespace mode for all the containers in a pod. It defaults to the `PODMAN_USERNS` environment variable. An empty value ("") means user namespaces are disabled. Rootless user --userns=Key mappings: Key | Host User | Container User -|| "" |$UID |0 (Default User account mapped to root user in container.) host |$UID |0 (Default User account mapped to root user in container.) keep-id |$UID |$UID (Map user account to same UID within container.) auto |$UID | nil (Host User UID is not mapped into container.) nomap |$UID | nil (Host User UID is not mapped into container.) Valid mode values are: auto[:OPTIONS,...]: automatically create a namespace. It is possible to specify these options to `auto`: gidmapping=CONTAINER\GID:HOST\GID:SIZE to force a GID mapping to be present in the user namespace. size=SIZE: to specify an explicit size for the automatic user namespace. e.g. `--userns=auto:size=8192`. If `size` is not specified, `auto` estimates the size for the user namespace. uidmapping=CONTAINER\UID:HOST\UID:SIZE to force a UID mapping to be present in the user namespace. host: run in the user namespace of the caller. The processes running in the container have the same privileges on the host as any other process launched by the calling user (default). keep-id: creates a user namespace where the current rootless user's UID:GID are mapped to the same values in the container. This option is not allowed for containers created by the root user. nomap: creates a user namespace where the current rootless user's UID:GID are not mapped into the container. This option is not allowed for containers created by the root user.
Project: CDK for Kubernetes (CDK8s) (Provisioning / Automation & Configuration)
File: testing.md

cdk8s bundles a set of test utilities under the `Testing` class: `Testing.app()` returns an `App` object bound to a temporary output directory. `Testing.chart()` returns a `Chart` object bound to a testing app. `Testing.synth(chart)` returns the Kubernetes manifest synthesized from a chart.
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_drop_trigger.md

title: DROP TRIGGER statement [YSQL] headerTitle: DROP TRIGGER linkTitle: DROP TRIGGER description: Use the DROP TRIGGER statement to remove a trigger from the database. menu: v2.18: identifier: ddldroptrigger parent: statements type: docs Use the `DROP TRIGGER` statement to remove a trigger from the database. {{%ebnf%}} drop_trigger {{%/ebnf%}} `RESTRICT` is the default and it will throw an error if any objects depend on the trigger. `CASCADE` will drop all objects that (transitively) depend on the trigger. ```plpgsql DROP TRIGGER update_moddatetime ON posts; ```
Project: StarRocks (App Definition and Development / Database)
File: conv.md

displayed_sidebar: "English" Converts the number `x` from one numeric base system to another, and returns the result as a string value. ```Haskell CONV(x,y,z); ``` `x`: the number to be converted. VARCHAR or BIGINT is supported. `y`: the source base. TINYINT is supported. `z`: the target base. TINYINT is supported. Returns a value of the VARCHAR data type. Convert the number 8 from numeric base system 2 to numeric base system 10: ```Plain mysql> select conv(8,10,2); +-+ | conv(8, 10, 2) | +-+ | 1000 | +-+ 1 row in set (0.00 sec) ```
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.2.10.1.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | Add ability to specify user environment variables individually* Environment variables for MapReduce tasks can now be specified as separate properties, e.g.: mapreduce.map.env.VARNAME=value mapreduce.reduce.env.VARNAME=value yarn.app.mapreduce.am.env.VARNAME=value yarn.app.mapreduce.am.admin.user.env.VARNAME=value This form of specifying environment variables is useful when the value of an environment variable contains commas. | Major | ZKFC ignores dfs.namenode.rpc-bind-host and uses dfs.namenode.rpc-address to bind to host address* ZKFC binds host address to "dfs.namenode.servicerpc-bind-host", if configured. Otherwise, it binds to "dfs.namenode.rpc-bind-host". If neither of those is configured, ZKFC binds itself to NameNode RPC server address (effectively "dfs.namenode.rpc-address"). | Critical | TestDataNodeHotSwapVolumes fails in trunk Jenkins runs* Submitted version of patch for branch-2.10 | Critical | WASB: Update azure-storage-java SDK* Azure WASB bug fix that can cause list results to appear empty. | Major | Docker image cannot set HADOOP\_CONF\_DIR* The HADOOP\CONF\DIR environment variable is no longer unconditionally inherited by containers even if it does not appear in the nodemanager whitelist variables specified by the yarn.nodemanager.env-whitelist property. If the whitelist property has been modified from the default to not include HADOOP\CONF\DIR yet containers need it to be inherited from the nodemanager's environment then the whitelist settings need to be updated to include HADOOP\CONF\DIR.
Project: KICS (Provisioning / Security & Compliance)
File: a1bc27c6-7115-48d8-bf9d-5a7e836845ba.md

title: Run Using apt hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a1bc27c6-7115-48d8-bf9d-5a7e836845ba Query name: Run Using apt Platform: Buildah Severity: <span style="color:#edd57e">Low</span> Category: Supply-Chain URL: apt is discouraged by the linux distributions as an unattended tool as its interface may suffer changes between versions. Better use the more stable apt-get and apt-cache<br> ```sh title="Positive test num. 1 - sh file" hl_lines="3" c=$(buildah from fedora) buildah run ${c} apt install python3-setuptools -y ``` ```sh title="Negative test num. 1 - sh file" c=$(buildah from fedora) buildah run ${c} apt-get install python3-setuptools -y ```
Project: Strimzi (App Definition and Development / Streaming & Messaging)
File: README-ppc64le.md

Run Jenkins pipeline on ppc64le VM Nightly builds will run on ppc64le VM to build the artifacts and run acceptance profile of system test on master branch at 12:00 am EST each day. Link to access Jenkins builds on ppc64le VM: http://140.211.168.45:8080/job/strimzi-kafka-operator/job/strimzi-kafka-operator/ Note: This link may change in the future.
Project: YugabyteDB (App Definition and Development / Database)
File: server-to-server.md

title: Enable server-to-server encryption headerTitle: Enable server-to-server encryption linkTitle: Enable server-to-server encryption description: Enable server-to-server encryption (using TLS) for intranode communication. headcontent: Enable server-to-server encryption (using TLS) for intranode communication. menu: v2.18: identifier: server-to-server parent: tls-encryption weight: 20 type: docs Before you can enable and use server-to-server encryption, you need to create and configure server certificates for each node of your YugabyteDB cluster. For information, see . To enable server-to-server encryption using TLS, start your YB-Master and YB-TServer nodes using the following flags. Flag | Node | Description | -|--|| `usenodetonodeencryption` | YB-Master, YB-TServer | Set to `true` to enable encryption between YugabyteDB nodes. Default value is `false`. | `allowinsecureconnections` | YB-Master, YB-TServer | Set to `false` to disallow any service with unencrypted communication from joining this cluster. Default value is `true`. Note that this flag requires `--usenodetonodeencryption` to be enabled. | `certs_dir` | YB-Master, YB-TServer | Optional. This directory should contain the configuration that was prepared in the a step for this node to perform encrypted communication with the other nodes. Default value for YB-Masters is `<data drive>/yb-data/master/data/certs` and for YB-TServers this location is `<data drive>/yb-data/tserver/data/certs` | You can enable access control by starting the `yb-master` services with the `--usenodetonodeencryption=true` flag as described above. Your command should look similar to this: ```sh bin/yb-master \ --fsdatadirs=<data directories> \ --master_addresses=<master addresses> \ --certsdir=/home/centos/tls/$NODEIP \ --allowinsecureconnections=false \ --usenodetonodeencryption=true ``` For information on starting YB-Master nodes for a deployment, see . You can enable access control by starting the `yb-tserver` services using the `--usenodetonodeencryption=true` flag described above. Your command should look similar to this: ```sh bin/yb-tserver \ --fsdatadirs=<data directories> \ --tservermasteraddrs=<master addresses> \ --certsdir /home/centos/tls/$NODEIP \ --usenodetonodeencryption=true & ``` For information on starting YB-TServers for a deployment, see . Because you have only enabled server-to-server encryption and not , you can now connect to this cluster using the YSQL shell (`ysqlsh`) or the YCQL shell (`ycqlsh`) without enabling encryption as shown here. ```sh $ ./bin/ysqlsh ``` ```output ysqlsh (11.2-YB-2.0.11.0-b0) Type "help" for help yugabyte=# ``` ```sh $ ./bin/ycqlsh ``` ```output Connected to local cluster at 127.0.0.1:9042. [ycqlsh 5.0.1 | Cassandra 3.9-SNAPSHOT | CQL spec 3.4.2 | Native protocol v4] Use HELP for help. ycqlsh> ```
Project: KICS (Provisioning / Security & Compliance)
File: df58dd45-8009-43c2-90f7-c90eb9d53ed9.md

title: Nifcloud Computing Has Common Private Network hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: df58dd45-8009-43c2-90f7-c90eb9d53ed9 Query name: Nifcloud Computing Has Common Private Network Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: The instance has common private network<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "nifcloud_instance" "positive" { imageid = data.nifcloudimage.ubuntu.id securitygroup = nifcloudsecuritygroup.example.groupname network_interface { networkid = "net-COMMONPRIVATE" } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "nifcloud_instance" "positive" { imageid = data.nifcloudimage.ubuntu.id securitygroup = nifcloudsecuritygroup.example.groupname network_interface { networkid = "net-COMMONGLOBAL" } network_interface { networkid = "net-COMMONPRIVATE" } } ``` ```tf title="Negative test num. 1 - tf file" resource "nifcloud_instance" "negative" { imageid = data.nifcloudimage.ubuntu.id securitygroup = nifcloudsecuritygroup.example.groupname network_interface { networkid = nifcloudprivate_lan.main.id } } ```
Project: KubeMQ (App Definition and Development / Streaming & Messaging)
File: kubemq_queues_list.md

Queues list of 'queues' channels Queues list command allows to get a list of 'queues' channels ``` kubemq queues list [flags] ``` ``` kubemq queue list kubemq queue list -f some-queue ``` ``` -f, --filter string set filter for channel / client name -h, --help help for list ``` - Execute Kubemq 'queues' commands
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.CommandStartEvent.md

/ / CommandStartEvent .CommandStartEvent command: `string` echo: `boolean` evaluatorOptions: execOptions: execType: execUUID: `string` pipeStages: `Object` | Name | Type | | : | :-- | | `prefix?` | `string` | | `redirect?` | `string` | | `redirector?` | `">"` \| `">>"` \| `"2>&1"` \| `">&"` \| `">>&"` | | `stages` | `string` | redirectDesired: `boolean` The output will be redirected to a file; do not display any live output route: `string` startTime: `number` tab:
Project: YugabyteDB (App Definition and Development / Database)
File: extension-postgresql-hll.md

title: postgresql-hll extension headerTitle: postgresql-hll extension linkTitle: postgresql-hll description: Using the postgresql-hll extension in YugabyteDB menu: v2.18: identifier: extension-postgresql-hll parent: pg-extensions weight: 20 type: docs The extension adds a new data type hll, which is a HyperLogLog data structure. HyperLogLog is a fixed-size, set-like structure used for distinct value counting with tunable precision. For example, in 1280 bytes hll can estimate the count of tens of billions of distinct values with only a few percent error. First, enable the extension: ```sql CREATE EXTENSION "hll"; ``` To run the helloworld example from the repository, connect using `ysqlsh` and run the following: ```sql CREATE TABLE helloworld (id integer, set hll); ``` ```output CREATE TABLE ``` Insert an empty HLL as follows: ```sql INSERT INTO helloworld(id, set) VALUES (1, hll_empty()); ``` ```output INSERT 0 1 ``` Add a hashed integer to the HLL as follows: ```sql UPDATE helloworld SET set = hlladd(set, hllhash_integer(12345)) WHERE id = 1; ``` ```output UPDATE 1 ``` Add a hashed string to the HLL as follows: ```sql UPDATE helloworld SET set = hlladd(set, hllhash_text('hello world')) WHERE id = 1; ``` ```output UPDATE 1 ``` Get the cardinality of the HLL as follows: ```sql SELECT hll_cardinality(set) FROM helloworld WHERE id = 1; ``` ```output hll_cardinality -- 2 (1 row) ``` For a more advanced example, see the .
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-completion.md

layout: default title: mesheryctl-system-completion permalink: reference/mesheryctl/system/completion redirect_from: reference/mesheryctl/system/completion/ type: reference display-title: "false" language: en command: system subcommand: completion Output shell completion code Output shell completion code <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system completion [bash|zsh|fish] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> source /dev/stdin <<< "$(mesheryctl system completion bash)" </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> source <(mesheryctl system completion bash) </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> brew install bash-completion # ensure you have bash-completion 1.3+ </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system completion bash > $(brew --prefix)/etc/bash_completion.d/mesheryctl </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> brew install bash-completion@2 </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system completion bash > $(brew --prefix)/etc/bash_completion.d/mesheryctl </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> $ echo "autoload -U compinit; compinit" >> ~/.zshrc </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> source <(mesheryctl system completion zsh) </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system completion zsh > "${fpath[1]}/_mesheryctl" </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system completion fish | source </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system completion fish > ~/.config/fish/completions/mesheryctl.fish </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for completion </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
Project: MongoDB (App Definition and Development / Database)
File: zstdless.1.md

zstdless(1) -- view zstandard-compressed files ============================================================================ SYNOPSIS -- `zstdless` [<flags>] [<file> ...] DESCRIPTION -- `zstdless` runs `less`(1) on files or stdin, if no <file> argument is given, after decompressing them with `zstdcat`(1). SEE ALSO -- `zstd`(1)
Project: StarRocks (App Definition and Development / Database)
File: st_polygon.md

displayed_sidebar: "English" Converts a WKT (Well Known Text) to a corresponding polygon memory form. ```Haskell GEOMETRY ST_Polygon(VARCHAR wkt) ``` ```Plain Text MySQL > SELECT STAsText(STPolygon("POLYGON ((0 0, 10 0, 10 10, 0 10, 0 0))")); ++ | stastext(stpolygon('POLYGON ((0 0, 10 0, 10 10, 0 10, 0 0))')) | ++ | POLYGON ((0 0, 10 0, 10 10, 0 10, 0 0)) | ++ ``` STPOLYGON,STPOLYFROMTEXT,ST_POLYGONFROMTEXT,ST,POLYGON,POLYFROMTEXT,POLYGONFROMTEXT
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_plugin_index_list.md

title: kbcli plugin index list List configured indexes ``` kbcli plugin index list [flags] ``` ``` kbcli plugin index list ``` ``` -h, --help help for list ``` ``` --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 custom plugin indexes
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.0-rc-5d.md

layout: release date: 2022-03-21 tag: v0.6.0-rc-5d language: en [CI] Chore: Bump to Golang 1.17 @leecalcote (#5243) Thank you to our contributors for making this release possible: @leecalcote
Project: ArangoDB (App Definition and Development / Database)
File: equality_success_type.md

+++ title = "`bool operator!=(const success_type<A> &) const`" description = "Returns true if this result does not compare equal to the success type sugar. Constexpr and noexcept propagating." categories = ["comparisons"] weight = 850 +++ Returns true if this result is not successful or its value does not compares equal to the value in the success type sugar. Comparison is done using `operator!=` on `valuetype` and `A`. If `A` is `void`, this call aliases {{% api "bool haserror() const noexcept" %}}. Requires: `operator!=` must be a valid expression between `valuetype` and `A`, or `A` is `void`. If `valuetype` is `void`, then so must be `A`. Complexity: Whatever the underlying `operator!=` has. Constexpr and noexcept of underlying operations is propagated. Guarantees: None.