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

title: "Command - devspace render" sidebar_label: devspace render Render builds all defined images and shows the yamls that would be deployed ``` devspace render [flags] ``` ``` Builds all defined images and shows the yamls that would be deployed via helm and kubectl, but skips actual deployment. ``` ``` --build-sequential Builds the images one after another instead of in parallel --dependency strings Renders only the specific named dependencies --deployments string Only deploy a specific deployment (You can specify multiple deployments comma-separated -b, --force-build Forces to build every image -h, --help help for render --max-concurrent-builds int The maximum number of image builds built in parallel (0 for infinite) --skip-build Skips image building --skip-dependencies Skips rendering the dependencies --skip-dependency strings Skips rendering the following dependencies --skip-push Skips image pushing, useful for minikube deployment --skip-push-local-kube Skips image pushing, if a local kubernetes environment is detected (default true) -t, --tag strings Use the given tag for all built images --verbose-dependencies Builds the dependencies verbosely ``` ``` --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: MongoDB (App Definition and Development / Database)
File: TROUBLESHOOTING.md

This guide is for troubleshooting gRPC implementations based on C core library (sources for most of them are living in the `grpc/grpc` repository). Extra logging can be very useful for diagnosing problems. All gRPC implementations based on C core library support the `GRPCVERBOSITY` and `GRPCTRACE` environment variables that can be used to increase the amount of information that gets printed to stderr. `GRPC_VERBOSITY` is used to set the minimum level of log messages printed by gRPC (supported values are `DEBUG`, `INFO` and `ERROR`). If this environment variable is unset, only `ERROR` logs will be printed. `GRPC_TRACE` can be used to enable extra logging for some internal gRPC components. Enabling the right traces can be invaluable for diagnosing for what is going wrong when things aren't working as intended. Possible values for `GRPC_TRACE` are listed in . Multiple traces can be enabled at once (use comma as separator). ``` GRPCVERBOSITY=debug ./helloworldapplicationusinggrpc ``` ``` GRPCVERBOSITY=info GRPCTRACE=api ./helloworldapplicationusing_grpc ``` ``` GRPCVERBOSITY=debug GRPCTRACE=tcp,http,api ./helloworldapplicationusing_grpc ``` Known limitations: `GPRC_TRACE=tcp` is currently not implemented for Windows (you won't see any tcp traces). Please note that the `GRPC_TRACE` environment variable has nothing to do with gRPC's "tracing" feature (= tracing RPCs in microservice environment to gain insight about how requests are processed by deployment), it is merely used to enable printing of extra logs.
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_alter_server.md

title: ALTER SERVER statement [YSQL] headerTitle: ALTER SERVER linkTitle: ALTER SERVER description: Use the ALTER SERVER statement to create alter a foreign server. menu: v2.18: identifier: ddlalterserver parent: statements type: docs Use the `ALTER SERVER` command to alter the definition of a foreign server. The command can be used to alter the options of the foreign server, or to change its owner. {{%ebnf%}} alter_server {{%/ebnf%}} Alter the foreign server named server_name. The `VERSION` clause can be used to specify the updated version of the server. The `OPTIONS` clause can be used to specify the new options of the foreign server. `ADD`, `SET`, and `DROP` specify the action to be performed. `ADD` is assumed if no operation is explicitly specified. Change the server's version to `2.0`, set `opt1` to `'true'`, and drop `opt2`. ```plpgsql yugabyte=# ALTER SERVER my_server SERVER VERSION '2.0' OPTIONS (SET opt1 'true', DROP opt2); ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: yaml-combine.md

type: languages title: "Apache Beam YAML Aggregations" <!-- 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. --> Beam YAML has EXPERIMENTAL ability to do aggregations to group and combine values across records. The is accomplished via the `Combine` transform type. For example, one can write ``` type: Combine config: group_by: col1 combine: total: value: col2 fn: type: sum ``` If the function has no configuration requirements, it can be provided directly as a string ``` type: Combine config: group_by: col1 combine: total: value: col2 fn: sum ``` This can be simplified further if the output field name is the same as the input field name ``` type: Combine config: group_by: col1 combine: col2: sum ``` One can aggregate over may fields at once ``` type: Combine config: group_by: col1 combine: col2: sum col3: max ``` and/or group by more than one field ``` type: Combine config: group_by: [col1, col2] combine: col3: sum ``` or none at all (which will result in a global combine with a single output) ``` type: Combine config: group_by: [] combine: col2: sum col3: max ``` As with all transforms, `Combine` can take a windowing parameter ``` type: Combine windowing: type: fixed size: 60 config: group_by: col1 combine: col2: sum col3: max ``` If no windowing specification is provided, it inherits the windowing parameters from upstream, e.g. ``` type: WindowInto windowing: type: fixed size: 60 type: Combine config: group_by: col1 combine: col2: sum col3: max ``` is equivalent to the previous example. One can use aggregation functions defined in Python by setting the language parameter. ``` type: Combine config: language: python group_by: col1 combine: biggest: value: "col2 + col2" fn: type: 'apache_beam.transforms.combiners.TopCombineFn' config: n: 10 ``` By setting the language to SQL, one can provide full SQL snippets as the combine fn. ``` type: Combine config: language: sql group_by: col1 combine: num_values: "count(*)" total: "sum(col2)" ``` One can of course also use the `Sql` transform type and provide a query directly.
Project: ShardingSphere (App Definition and Development / Database)
File: evolution.en.md

+++ title = "Apache ShardingSphere architecture evolution driven by open source" weight = 5 chapter = true +++ This sharing will start with NewSQL, focusing on the evolution and planning of ShardingSphere architecture, and fall into the relationship and development between open source and contributors. From the perspective of product ecology, open source power, personal growth and development, it brings us interpretation and sharing. {{< bilibili BV1av41167ny >}}
Project: KICS (Provisioning / Security & Compliance)
File: 41abc6cc-dde1-4217-83d3-fb5f0cc09d8f.md

title: Redshift Using Default Port hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 41abc6cc-dde1-4217-83d3-fb5f0cc09d8f Query name: Redshift Using Default Port Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: Redshift should not use the default port (5439) because an attacker can easily guess the port<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsredshiftcluster" "positive1" { cluster_identifier = "tf-redshift-cluster" database_name = "mydb" master_username = "foo" master_password = "Mustbe8characters" node_type = "dc1.large" cluster_type = "single-node" publicly_accessible = false } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="9" resource "awsredshiftcluster" "positive2" { cluster_identifier = "tf-redshift-cluster" database_name = "mydb" master_username = "foo" master_password = "Mustbe8characters" node_type = "dc1.large" cluster_type = "single-node" publicly_accessible = false port = 5439 } ``` ```tf title="Negative test num. 1 - tf file" resource "awsredshiftcluster" "negative1" { cluster_identifier = "tf-redshift-cluster" database_name = "mydb" master_username = "foo" master_password = "Mustbe8characters" node_type = "dc1.large" cluster_type = "single-node" publicly_accessible = false port = 1150 } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.4.26.md

layout: release date: 2020-12-10 tag: v0.4.26 fixes for grafana bug @kumarabd (#2073) [mesheryctl] Implement meshery update prompt mesheryctl @uds5501 (#2052) Bump the meshery chart's version @Aisuko (#2071) Change the selector value to configuration @Aisuko (#2066) Updated CONTRIBUTING.md to reflect update to Go 1.15 @mgfeller (#2068) Restructure adapter dashboard @utkarsh-pro (#2069) [UI] Resize sidebar to accomodate external links @uds5501 (#2037) Kalradev/meshsync/endpoint @kalradev (#2013) fix: restructure mesheryctl version error handling @kushthedude (#1791) Bump @material-ui/lab from 4.0.0-alpha.56 to 4.0.0-alpha.57 in /ui @dependabot-preview (#2059) Bump caniuse-lite from 1.0.30001162 to 1.0.30001165 in /ui @dependabot-preview (#2063) Bump eslint from 7.14.0 to 7.15.0 in /provider-ui @dependabot-preview (#2053) Bump @material-ui/core from 4.11.1 to 4.11.2 in /provider-ui @dependabot-preview (#2054) Bump husky from 4.3.0 to 4.3.5 in /ui @dependabot-preview (#2061) Bump @material-ui/icons from 4.9.1 to 4.11.2 in /provider-ui @dependabot-preview (#2055) Bump cypress from 6.0.0 to 6.0.1 in /ui @dependabot-preview (#2062) Bump lint-staged from 10.5.2 to 10.5.3 in /ui @dependabot-preview (#2060) Bump eslint from 7.14.0 to 7.15.0 in /ui @dependabot-preview (#2058) Bump @material-ui/icons from 4.9.1 to 4.11.2 in /ui @dependabot-preview (#2057) correct usage of env @vineethvanga18 (#2051) CI: Fixed slack notification for repo stars @SudhanAruna (#2049) Bump @babel/traverse from 7.12.8 to 7.12.9 in /ui @dependabot-preview (#2001) Bump caniuse-lite from 1.0.30001159 to 1.0.30001162 in /ui @dependabot-preview (#1998) Bump @fortawesome/react-fontawesome from 0.1.12 to 0.1.13 in /ui @dependabot-preview (#2003) switched to docs.meshery.io @leecalcote (#2036) Bump cypress from 5.6.0 to 6.0.1 in /provider-ui @dependabot-preview (#2021) Bump lint-staged from 10.5.1 to 10.5.2 in /ui @dependabot-preview (#2002) Bump notistack from 1.0.1 to 1.0.2 in /ui @dependabot-preview (#2005) Bump cypress from 5.6.0 to 6.0.0 in /ui @dependabot-preview (#2000) Bump @material-ui/core from 4.11.0 to 4.11.1 in /provider-ui @dependabot-preview (#1996) Bump git.mills.io/prologic/bitcask from 0.3.6 to 0.3.9 @dependabot-preview (#2011) [Docs] Added Release Notes v0.4.23, v0.4.24, v0.4.25 to Docs Releases page @aneeshnema (#2064) fixes #2044 @sumit-kushwah (#2048) Leecalcote/docs update @leecalcote (#2046) [Docs] restructure 1 @leecalcote (#2045) [Docs] Update Content menu @chandrashritii (#2034) Fix invalid markdown lifecycle management page @Shulammite-Aso (#2027) [Docs] Copy-to-clipboard fix @chebro (#2017) [Docs] Adapter behavior notes @leecalcote (#2038) switched to docs.meshery.io @leecalcote (#2036) [Docs] Jekyll upgrade; Gemfile.lock tracking @leecalcote (#2023) [Docs] Fix broken links @chandrashritii (#2035) [Docs] README: fix for link to quick start guide @leecalcote (#2030) [Docs] brew instructions @chandrashritii (#2006) [Docs] Clipboard plugin @chandrashritii (#1946)
Project: StarRocks (App Definition and Development / Database)
File: array_intersect.md

displayed_sidebar: "English" Returns an array of the elements in the intersection of one or more arrays. ```Haskell array_intersect(input0, input1, ...) ``` `input`: one or more arrays whose intersection you want to obtain. Specify arrays in the `(input0, input1, ...)` format and make sure that the arrays that you specify are of the same data type. Returns an array of the same data type as the arrays that you specify. Example 1: ```Plain mysql> SELECT array_intersect(["SQL", "storage"], ["mysql", "query", "SQL"], ["SQL"]) AS no_intersect ; +--+ | no_intersect | +--+ | ["SQL"] | +--+ ``` Example 2: ```Plain mysql> SELECT arrayintersect(["SQL", "storage"], ["mysql", null], [null]) AS nointersect ; +--+ | no_intersect | +--+ | [] | +--+ ``` Example 3: ```Plain mysql> SELECT arrayintersect(["SQL", null, "storage"], ["mysql", null], [null]) AS nointersect ; +--+ | no_intersect | +--+ | [null] | +--+ ```
Project: Pinniped (Provisioning / Key Management)
File: supported-clusters.md

title: Supported cluster types description: See the supported cluster types for the Pinniped Concierge. cascade: layout: docs menu: docs: name: Supported Cluster Types weight: 10 parent: reference | Cluster Type | Concierge Works? | |-|-| | | Yes | | | Yes | | | Yes | | | Yes | | | Yes | | | Yes | The Pinniped Concierge has two strategies available to support clusters, under the following conditions: Token Credential Request API: Can be run on any Kubernetes cluster where a custom pod can be executed on the same node running `kube-controller-manager`. This type of cluster is typically called "self-hosted" because the cluster's control plane is running on nodes that are part of the cluster itself. Most managed Kubernetes services do not support this. Impersonation Proxy: Can be run on any Kubernetes cluster. Default configuration requires that a `LoadBalancer` service can be created. Most cloud-hosted Kubernetes environments have this capability. The Impersonation Proxy automatically provisions (when `spec.impersonationProxy.mode` is set to `auto`) a `LoadBalancer` for ingress to the impersonation endpoint. Users who wish to use the impersonation proxy without an automatically configured `LoadBalancer` can do so with an automatically provisioned `ClusterIP` or with a Service that they provision themselves. These options can be configured in the spec of the . If a cluster is capable of supporting both strategies, the Pinniped CLI will use the token credential request API strategy by default. To choose the strategy to use with the concierge, use the `--concierge-mode` flag with `pinniped get kubeconfig`. Possible values are `ImpersonationProxy` and `TokenCredentialRequestAPI`. Do not use the command line option `--anonymous-auth=false` in the `kube-apiserver` CLI for a cluster that does not use the impersonation proxy strategy. This is because the `kube-apiserver` blocks unauthenticated access to the TokenCredentialRequest API of the Concierge, which will prevent users from being able to authenticate. This does not matter while using the impersonation proxy strategy, which will allow these TokenCredentialRequests requests anyway.
Project: StarRocks (App Definition and Development / Database)
File: pmod.md

displayed_sidebar: "English" Returns the positive remainder of `dividend` divided by`divisor`. ```SQL pmod(dividend, divisor) ``` `dividend`: the number to be divided. `divisor`: the number that divides. Both `arg1` and `arg2` support the following data types: BIGINT DOUBLE NOTE `dividend` and `divisor` must agree in the data type. StarRocks performs an implicit conversion if they do not agree in the data type. Returns a value of the same data type as the `dividend`. StarRocks returns NULL if `divisor` is specified as 0. ```Plain mysql> select pmod(3.14,3.14); ++ | pmod(3.14, 3.14) | ++ | 0 | ++ mysql> select pmod(3,6); ++ | pmod(3, 6) | ++ | 3 | ++ mysql> select pmod(11,5); +-+ | pmod(11, 5) | +-+ | 1 | +-+ mysql> select pmod(-11,5); +--+ | pmod(-11, 5) | +--+ | 4 | +--+ mysql> SELECT pmod(11,-5); +--+ | pmod(11, -5) | +--+ | -4 | +--+ mysql> SELECT pmod(-11,-5); ++ | pmod(-11, -5) | ++ | -1 | ++ ```
Project: KCL (Provisioning / Automation & Configuration)
File: E2D34.md

KCL will report `IllegalInheritError` when an illegal inheritance occurs in the schema. The `ewcode` of `IllegalInheritError` is `E2D34`. For example: ```python schema FullnameMixin: fullName = "{} {}".format(firstName, lastName) schema Scholar(FullnameMixin): # mixin inheritance is illegal school: str ``` The KCL program will cause the following error message. ```shell error[E2D34]: IllegalInheritError --> /schema/inherit/inheritmixinfail/main.k:4:16 | 4 | schema Scholar(FullnameMixin): | ^ invalid schema inherit object type, expect schema, got 'FullnameMixin' | ``` Possible resolution: Schema supports single inheritance of schema in KCL.
Project: kpt (Provisioning / Automation & Configuration)
File: governance.md

The Kpt governance model is modeled after . In particular, we leverage the same hierarchy of steering committee, SIGs, subprojects, working groups that Kubernetes does to facilitiate engagement with the greater ecosystem. We plan to refine this over time as the number of contributors grow. As an example, we don't plan to record all sig meetings at the start but may over time as it becomes valuable for interested parties who miss the meetings. If something is not defined here, it is expected that we will inherit the Kubernetes equivalent. The Kpt Steering Committee is the governing body for the Kpt project Please reach out to us on slack or attend one of the SIG meetings to bring up anything you'd like to discuss. We actively partcipate in the SIGs as well as Office Hours | Name | Profile | | - | - | | Chris Sosa | | | Brian Grant | | | Justin Santa Barbara | | | John Belamaric | | Covers leveraging to customize and automate configuration at scale. This is the largest SIG in Kpt that spans most of its surface area including incubation for apply config as data to new use cases. Brian Grant ( *) Chris Sosa (*) Everything not covered by another sub-project including porch, fn render, etc Sunil Arora ( *) Morten Torkildsen (*) Owns the SDK that enables our Config as Data experience Yuwen Ma ( *) Focused on making it easy to leverage Config as Data with application workloads Chris Sosa (*) Focused on making it easy to automate deployments through GitOps. Owns the APIs and tools that are part of the Mike Borozdin ( *) Janet Kuo (*)
Project: KICS (Provisioning / Security & Compliance)
File: 6fa44721-ef21-41c6-8665-330d59461163.md

title: S3 Bucket Allows Delete Action From All Principals hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6fa44721-ef21-41c6-8665-330d59461163 Query name: S3 Bucket Allows Delete Action From All Principals Platform: Ansible Severity: <span style="color:#ff0000">Critical</span> Category: Access Control URL: S3 Buckets must not allow Delete Action From All Principals, as to prevent leaking private information to the entire internet or allow unauthorized data tampering / deletion. This means the 'Effect' must not be 'Allow' when the 'Action' is Delete, for all Principals.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="6" name: Bucket amazon.aws.s3_bucket: name: mys3bucket state: present policy: Version: "2020-10-07" Statement: Effect: Allow Action: DeleteObject Principal: "*" ``` ```yaml title="Negative test num. 1 - yaml file" name: Bucket amazon.aws.s3_bucket: name: mys3bucket state: present policy: Version: '2020-10-07' Statement: Effect: Deny Action: DeleteObject Principal: '*' ```
Project: StarRocks (App Definition and Development / Database)
File: KILL_ANALYZE.md

displayed_sidebar: "English" Cancels a running collection task, including manual and custom automatic tasks. This statement is supported from v2.4. ```SQL KILL ANALYZE <ID> ``` The task ID for a manual collection task can be obtained from SHOW ANALYZE STATUS. The task ID for a custom collection task can be obtained from SHOW ANALYZE SHOW ANALYZE JOB. For more information about collecting statistics for CBO, see .
Project: Copa (Provisioning / Security & Compliance)
File: output.md

title: Output :::caution Experimental: This feature might change without preserving backwards compatibility. ::: Copa optionally outputs a Vulnerability Exploitability eXchange (VEX) file as a result of the patching process to surface the vulnerabilities and packages that were patched. Currently, Copa supports the format, but it can be extended to support other formats. OpenVEX is an implementation of Vulnerability Exploitability eXchange (VEX) format. For more information, see . :::tip Use `COPAVEXAUTHOR` environment variable to set the author of the VEX document. If it's not set, the author will default to `Project Copacetic`. A VEX document must contain at least one VEX statement. If there are no fixed vulnerabilities, Copa will not generate a VEX document. ::: To generate a VEX document using OpenVEX, use `--format="openvex"` flag, and use `--output` to specify a file path. For example: ```bash copa patch -i docker.io/library/nginx:1.21.6 -r nginx.1.21.6.json -t 1.21.6-patched --format="openvex" --output "nginx.1.21.6-vex.json" ``` This will generate a VEX Document that looks like: ```json { "@context": "https://openvex.dev/ns", "@id": "https://openvex.dev/docs/public/vex-a6c44ec1d79e9dd4190dc01b4ecf7527ebb26bd37c01e32e6efcd203ae00d2a5", "author": "Project Copacetic", "timestamp": "2023-10-11T00:15:00.114768055Z", "version": 1, "tooling": "Project Copacetic", "statements": [ { "vulnerability": { "@id": "CVE-2021-22945" }, "products": [ { "@id": "pkg:oci/docker.io/library/nginx:1.21.6-patched", "subcomponents": [ { "@id": "pkg:deb/debian/curl@7.74.0-1.3+deb11u2?arch=amd64" }, { "@id": "pkg:deb/debian/libcurl4@7.74.0-1.3+deb11u2?arch=amd64" } ] } ], "status": "fixed" }, ... } ```
Project: YDB (App Definition and Development / Database)
File: weakfield.md

Fetches a table column from a strong schema, if it is in a strong schema, or from the `other` and `rest` fields. If the value is missing, it returns `NULL`. Syntax: `WeakField([<table>.]<field>, <type>[, <default_value>])`. The default value is used only if the column is missing in the data schema. To use the default value in any case, use . Examples: ```yql SELECT WeakField(my_column, String, "no value"), WeakField(mytable.othercolumn, Int64) FROM my_table; ```