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

One {{ ydb-short-name }} installation consists of a cluster that is divided into nodes. A node is a single process in the system, usually ydbd. This node is part of a cluster and can exchange data with its other nodes via Interconnect. Each node has its own ID which is usually named NodeId. NodeID is a 20-bit integer equal to or greater than 1. NodeID 0 is reserved for internal needs and usually indicates the current node or no node. A number of services are run on each node and implemented via actors. Nodes can be static and dynamic. A configuration of static nodes, that is, their complete list with the address for connecting via Interconnect specified, is stored in a configuration file and is read once when the process is started. A set of static nodes changes very rarely. This usually happens when expanding clusters or moving nodes from one physical machine to another. To change a set of static nodes, you must apply the updated configuration to every node and then perform a rolling restart of the entire cluster. Dynamic nodes are not known in advance and are added to the system as new processes are started. This may be due, for example, to the creation of new tenants in {{ ydb-short-name }} installations as a database. When a dynamic node is registered, its process first connects to one of the static nodes via gRPC, transmits information about itself through a special service called Node Broker, and receives a NodeID to use to log into the system. The mechanism for assigning nodes is pretty much similar to the DHCP in the context of distributing IP addresses.
Project: Meshery (Provisioning / Automation & Configuration)
File: vineyard.md

layout: integration title: Vineyard subtitle: Collaborative and visual infrastructure as code for Vineyard image: /assets/img/integrations/vineyard/icons/color/vineyard-color.svg permalink: extensibility/integrations/vineyard docURL: https://docs.meshery.io/extensibility/integrations/vineyard description: integrations-category: Runtime integrations-subcategory: Cloud Native Storage registrant: Artifact Hub components: 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: KICS (Provisioning / Security & Compliance)
File: c999cf62-0920-40f8-8dda-0caccd66ed7e.md

title: API Gateway Stage Without API Gateway UsagePlan Associated hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c999cf62-0920-40f8-8dda-0caccd66ed7e Query name: API Gateway Stage Without API Gateway UsagePlan Associated Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Resource Management URL: API Gateway Stage should have API Gateway UsagePlan defined and associated.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1 10" resource "awsapigateway_stage" "positive1" { restapiid = "some deployment id" deployment_id = "some rest api id" stage_name = "some name" tags { project = "ProjectName" } } resource "awsapigateway_stage" "positive2" { deployment_id = "some deployment id" restapiid = "some rest api id" stage_name = "development" } resource "awsapigatewayusageplan" "positive3" { name = "my-usage-plan" description = "my description" product_code = "MYCODE" api_stages { api_id = "another id" stage = "development" } } ``` ```tf title="Negative test num. 1 - tf file" resource "awsapigateway_stage" "negative1" { deployment_id = "some deployment id" restapiid = "restapi1" stage_name = "development" } resource "awsapigatewayusageplan" "negative2" { name = "my-usage-plan" description = "my description" product_code = "MYCODE" api_stages { apiid = "restapi_1" stage = "development" } } ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: carfinance247.md

title: "Car Finance 24/7" icon: /images/logos/powered-by/carfinance247.png hasLink: "https://www.carfinance247.co.uk/" <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->
Project: Sonobuoy (Provisioning / Security & Compliance)
File: 2021-03-18-release-v0-50.md

title: Introducing Sonobuoy v0.50 image: /img/sonobuoy.svg excerpt: Sonobuoy 0.50 release announcement author_name: Vladimir Vivien, Wilson Husin author_url: https://github.com/vmware-tanzu categories: [kubernetes, sonobuoy, distroless] tags: ['Sonobuoy Team', 'Vladimir Vivien', 'Wilson Husin'] date: 2021-03-18 slug: sonobuoy-v0-50 In December, we announced that Sonobuoy releases will be decoupled from Kubernetes releases along with plenty of other items on the roadmap. With this release, Sonobuoy continues to make progress and this write up highlights two of its major themes. Previously the Sonobuoy version number was coupled with the Kubernetes release number. As part of the march toward version v1.0, we decided to break that incremental versioning scheme and decouple our releases from that of Kubernetes release cadence. To amplify this effort, we have decided to reset our release number scheme going from v0.20 to v0.50 to ensure that there is no perceived relation between a Sonobuoy release and a Kubernetes release. This is because all Sonobuoy binaries will support most Kubernetes releases. One of the thorny issues that keeps occuring is the constant request for CVE remediations caused by programs bundled in Debian container images, which happens to be the base image for Sonobuoy. This usually happens when a security scan detects a vulnerability from a (likely outdated) component packaged in the operating system. Today, we are excited to announce that Sonobuoy has gone Distroless! This means the Sonobuoy container image is now built without including any of the operating system items that are traditionally packaged with OS-based container images. As a direct result, this release managed to shed more than 60% of its size going from 99.6 MB, in the previous version, to 32 MB in this release.
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: v1.22.0.md

title: v1.22.0 weight: 998978000 IMPORTANT The `community.kubernetes` collection is being renamed to `kubernetes.core`. As of version 2.0.0, the collection has been replaced by deprecated redirects for all content to kubernetes.core. If you are using FQCNs starting with `community.kubernetes`, please update them to `kubernetes.core`. Ensure that you check the to verify if your Operator code must be updated and it is affected by the MAJOR changes. In the `requirements.yml` file: Replace: ```yaml collections: name: community.kubernetes version: "1.2.1" ``` With: ```yaml collections: name: community.kubernetes version: "2.0.1" ``` See for more details. Ensure that you check the to verify if your Operator code must be updated and it is affected by the MAJOR changes. In the `requirements.yml` file: Replace: ```yaml collections: ... name: kubernetes.core version: "2.2.0" ``` With: ```yaml collections: ... name: kubernetes.core version: "2.3.1" ``` See for more details. In the `requirements.yml` file: Replace: ```ymal collections: ... name: cloud.common version: "2.1.0" ``` With: ```ymal collections: ... name: cloud.common version: "2.1.1" ``` See for more details. To update your project to support Kubernetes 1.24: In `go.mod`: Replace `k8s.io/api v0.23.5` with `k8s.io/api v0.24.0` Replace `k8s.io/apimachinery v0.23.5` with `k8s.io/apimachinery v0.24.0` Replace `k8s.io/client-go v0.23.5` with `k8s.io/client-go v0.24.0` Replace `sigs.k8s.io/controller-runtime v0.11.2` with `sigs.k8s.io/controller-runtime v0.12.1` Hybrid Helm (hybrid) only: Replace `github.com/operator-framework/helm-operator-plugins v0.0.11` with `github.com/operator-framework/helm-operator-plugins v0.0.12-0.20220608155702-d3967d2ae2ac` Run `go mod tidy` to ensure all dependencies are upgraded In `Makefile`: Replace `CONTROLLERTOOLSVERSION ?= 0.8.0` with `CONTROLLERTOOLSVERSION ?= 0.9.0` Replace `ENVTESTK8SVERSION = 1.23` with `ENVTESTK8SVERSION = 1.24` Run `make` to run all make targets See for more details. To update your project to use Go 1.18: In the `go.mod` file: Replace `go 1.17` with `go 1.18` Run `go mod tidy` to ensure all dependencies are upgraded See for more details. To update your project to use OPM `v1.23.0`: In the `Makefile`: Replace `curl -sSLo $(OPM) https://github.com/operator-framework/operator-registry/releases/download/v1.19.1/$${OS}-$${ARCH}-opm` with `curl -sSLo $(OPM) https://github.com/operator-framework/operator-registry/releases/download/v1.23.0/$${OS}-$${ARCH}-opm` Run `make opm` See for more details.
Project: FOSSA (Provisioning / Security & Compliance)
File: renv.md

Currently, we only support analysis of r project which are using . | Files | Direct Deps | Deep Deps | Edges | Classifies Dev & Test Deps | Container Scanning | | | | | | -- | | | `renv.lock` | (included but not classified as direct) | :whitecheckmark: | :whitecheckmark: | :x: | :whitecheckmark: | | `DESCRIPTION` & `renv.lock` | :whitecheckmark: | :whitecheckmark: | :whitecheckmark: | :x: | :whitecheckmark: | Find a file named `DESCRIPTION`, and optionally look for `renv.lock` in the same directory as `DESCRIPTION`. Discovery will not look for projects inside `renv` directory, if `renv.lock` or `DESCRIPTION` files are discovered. Parse `DESCRIPTION` file to identify direct dependencies - we look for packages in `Depends`, `Imports`, `Suggests`, `Enhances`, `LinkingTo`. Parse `renv.lock` file to identify deep dependencies, and edges among them. If only `DESCRIPTION` file is accessible, FOSSA CLI will ignore version constraints, and will always default to latest version. Create `DESCRIPTION` file: ```text Type: project Description: My project Depends: tidyverse ``` Create `main.R` file: ```r options(renv.config.install.verbose = TRUE) options(renv.config.install.transactional = FALSE) renv::init(bare = TRUE) renv::install("glue@1.2.0") renv::install() Square <- function(x) { return(x^2) } print(Square(4)) renv::snapshot() ``` execute `rscript main.R` execute `fossa analyze --only-target renv --output` (run analysis only `renv`, but do not upload result to an endpoint) `fossa-cli` cannot identify test or development dependencies, and by default includes all dependencies in the analysis. `fossa-cli` will ignore version constraint if `renv.lock` file is not present. `fossa-cli` cannot analyze path dependencies. <!-- renv does not have docs on local packages --> Please refer to for workaround. Explicitly specify an analysis target in `.fossa.yml` file. The example below excludes all other analysis targets: ```yaml version: 3 targets: only: type: renv ``` Please file a ticket at . Make sure to attach following for quick response from support or development team. `DESCRIPTION` file `renv.lock` file (if any) stdout of `renv::diagnostics()`
Project: YugabyteDB (App Definition and Development / Database)
File: update,returning_clause,update_item,column_values,column_names.grammar.md

```output.ebnf update ::= [ WITH [ RECURSIVE ] { commontableexpression [ , ... ] } ] UPDATE tableexpr [ [ AS ] alias ] SET updateitem [ , ... ] [ WHERE boolean_expression | WHERE CURRENT OF cursor_name ] [ returning_clause ] returningclause ::= RETURNING { * | { outputexpression [ [ AS ] output_name ] } [ , ... ] } updateitem ::= columnname = column_value | ( columnnames ) = [ ROW ] ( columnvalues ) | ( column_names ) = ( query ) column_values ::= { expression | DEFAULT } [ , ... ] columnnames ::= columnname [ , ... ] ```
Project: Druid (App Definition and Development / Database)
File: select-query.md

id: select-query title: "Select queries" sidebar_label: "Select" <!-- ~ 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. --> Older versions of Apache Druid included a Select query type. Since Druid 0.17.0, it has been removed and replaced by the , which offers improved memory usage and performance. This solves issues that users had with Select queries causing Druid to run out of memory or slow down.
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.24.0.md

Added questionnaire doc for WOT by @BtXin in https://github.com/Edgenesis/shifu/pull/660 Bump k8s.io/client-go from 0.27.3 to 0.27.4 by @dependabot in https://github.com/Edgenesis/shifu/pull/659 Bump github.com/gopcua/opcua from 0.3.15 to 0.4.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/657 Bump github.com/eclipse/paho.mqtt.golang from 1.4.2 to 1.4.3 by @dependabot in https://github.com/Edgenesis/shifu/pull/656 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.23.0...v0.24.0
Project: external-secrets (Provisioning / Security & Compliance)
File: fake.md

We provide a `fake` implementation to help with testing. This provider returns static key/value pairs and nothing else. To use the `fake` provider simply create a `SecretStore` or `ClusterSecretStore` and configure it like in the following example: !!! note inline end The provider returns static data configured in `value`. You can define a `version`, too. If set the `remoteRef` from an ExternalSecret must match otherwise no value is returned. ```yaml {% include 'fake-provider-store.yaml' %} ``` Please note that `value` is intended for exclusive use with `data` for `dataFrom`. You can use the `data` to set a `JSON` compliant value to be used as `dataFrom`. Here is an example `ExternalSecret` that displays this behavior: !!! warning inline end This provider supports specifying different `data[].version` configurations. However, `data[].property` is ignored. ```yaml {% include 'fake-provider-es.yaml' %} ``` This results in the following secret: ```yaml {% include 'fake-provider-secret.yaml' %} ```
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.2.0.5-alpha.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | ReplicationMonitor thread can exit with NPE due to the race between delete and replication of same file. | Blocker | namenode | Uma Maheswara Rao G | Uma Maheswara Rao G | | | GzipCodec NPE upon reset with IBM JDK | Major | io | Luke Lu | Yu Li | | | inside of FileOutputCommitter the initialized Credentials cache appears to be empty | Blocker | mrv2 | Roman Shaposhnik | Vinod Kumar Vavilapalli | | | commons-daemon 1.0.3 dependency has bad group id causing build issues | Major | build | Sangjin Lee | Sangjin Lee | | | smart-test-patch.sh hangs for new version of patch (2.7.1) | Major | . | Ravi Prakash | Ravi Prakash |
Project: Beam (App Definition and Development / Streaming & Messaging)
File: additional-common-features-not-yet-part-of-the-beam-model.md

type: runners title: "Additional common features not yet part of the Beam model" layout: "capability-template" <!-- 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. --> <!-- Summary table --> {{< documentation/capability-matrix-big cap-data="capability-matrix" cap-view="full" cap-index=6 >}}
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_cancel-ops.md

title: kbcli cluster cancel-ops Cancel the pending/creating/running OpsRequest which type is vscale or hscale. ``` kbcli cluster cancel-ops NAME [flags] ``` ``` kbcli cluster cancel-ops <opsRequestName> ``` ``` --auto-approve Skip interactive approval before cancel the opsRequest -h, --help help for cancel-ops ``` ``` --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 ``` - Cluster command.
Project: YDB (App Definition and Development / Database)
File: env_cloud.md

If the value of the `IAM_TOKEN` environment variable is set, the Access Token authentication mode is used, where this variable value is passed. Otherwise, if the value of the `YC_TOKEN` environment variable is set, the Refresh Token authentication mode is used and the token to transfer to the IAM endpoint is taken from this variable value when repeating the request. Otherwise, if the value of the `USEMETADATACREDENTIALS` environment variable is set to 1, the Metadata authentication mode is used. Otherwise, if the value of the `SAKEYFILE` environment variable is set, the Service Account Key authentication mode is used and the key is taken from the file whose name is specified in this variable.
Project: Meshery (Provisioning / Automation & Configuration)
File: 10-03-2022-04-20-10_a3374f2f.md

timestamp: "2022-10-03 04:20:09 UTC Mon" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "v0.6.10" k8s-distro: minikube k8s-version: "v1.20.11" service-mesh: Consul service-mesh-version: "v0.49.0" tests: consul-client: null consul-server: null overall-status: "failing"
Project: ClickHouse (App Definition and Development / Database)
File: prewhere.md

slug: /en/sql-reference/statements/select/prewhere sidebar_label: PREWHERE Prewhere is an optimization to apply filtering more efficiently. It is enabled by default even if `PREWHERE` clause is not specified explicitly. It works by automatically moving part of condition to prewhere stage. The role of `PREWHERE` clause is only to control this optimization if you think that you know how to do it better than it happens by default. With prewhere optimization, at first only the columns necessary for executing prewhere expression are read. Then the other columns are read that are needed for running the rest of the query, but only those blocks where the prewhere expression is `true` at least for some rows. If there are a lot of blocks where prewhere expression is `false` for all rows and prewhere needs less columns than other parts of query, this often allows to read a lot less data from disk for query execution. The clause has the same meaning as the `WHERE` clause. The difference is in which data is read from the table. When manually controlling `PREWHERE` for filtration conditions that are used by a minority of the columns in the query, but that provide strong data filtration. This reduces the volume of data to read. A query may simultaneously specify `PREWHERE` and `WHERE`. In this case, `PREWHERE` precedes `WHERE`. If the setting is set to 0, heuristics to automatically move parts of expressions from `WHERE` to `PREWHERE` are disabled. If query has modifier, the `PREWHERE` optimization is not always correct. It is enabled only if both settings and are turned on. :::note The `PREWHERE` section is executed before `FINAL`, so the results of `FROM ... FINAL` queries may be skewed when using `PREWHERE` with fields not in the `ORDER BY` section of a table. ::: `PREWHERE` is only supported by tables from the family. ```sql CREATE TABLE mydata ( `A` Int64, `B` Int8, `C` String ) ENGINE = MergeTree ORDER BY A AS SELECT number, 0, if(number between 1000 and 2000, 'x', toString(number)) FROM numbers(10000000); SELECT count() FROM mydata WHERE (B = 0) AND (C = 'x'); 1 row in set. Elapsed: 0.074 sec. Processed 10.00 million rows, 168.89 MB (134.98 million rows/s., 2.28 GB/s.) -- let's enable tracing to see which predicate are moved to PREWHERE set sendlogslevel='debug'; MergeTreeWhereOptimizer: condition "B = 0" moved to PREWHERE -- Clickhouse moves automatically `B = 0` to PREWHERE, but it has no sense because B is always 0. -- Let's move other predicate `C = 'x'` SELECT count() FROM mydata PREWHERE C = 'x' WHERE B = 0; 1 row in set. Elapsed: 0.069 sec. Processed 10.00 million rows, 158.89 MB (144.90 million rows/s., 2.30 GB/s.) -- This query with manual `PREWHERE` processes slightly less data: 158.89 MB VS 168.89 MB ```