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

Generate the autocompletion script for powershell Generate the autocompletion script for powershell. To load completions in your current shell session: yba completion powershell | Out-String | Invoke-Expression To load completions for every new session, add the output of the above command to your powershell profile. ``` yba completion powershell [flags] ``` ``` -h, --help help for powershell --no-descriptions disable completion descriptions ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Generate the autocompletion script for the specified shell
Project: Pravega (App Definition and Development / Streaming & Messaging)
File: deployment.md

<!-- Copyright Pravega Authors. 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. --> This guide describes the options for running Pravega for development, testing and in production. If you are interested on deploying Pravega in production, we recommend you to have a look to our [Configuration and Provisioning Guide](../admin-guide/cluster-dependencies.md). There are two modes for running Pravega. Standalone - Standalone mode is suitable for development and testing Pravega applications. It can either be run from the source code, from the distribution package or as a docker container. Distributed - Distributed mode runs each component separately on a single or multiple nodes. This is suitable for production in addition for development and testing. The deployment options in this mode include a manual installation, running in a docker swarm, or using the Kubernetes operators. The following prerequisites are required for running Pravega in all modes. Java 11 The following prerequisites are required for running in production. These are only required for running in distributed mode. AWS S3, Azure Blob Storage, Google Cloud Storage, HDFS or a mounted distributed filesystem Zookeeper 3.6.3 Bookkeeper 4.14.1 For more details on the prerequisites and recommended configuration options for bookkeeper see the . There are multiple options provided for running Pravega in different environments. Most of these use the installation package from a Pravega release. You can find the latest Pravega release on the . - Running Pravega locally is suitable for development and testing. - Production - Multi-node installation suitable for running in production. - using for production clusters.
Project: KubeDL (Provisioning / Automation & Configuration)
File: GOVERNANCE.md

The governance model adopted in KubeDL is influenced by many CNCF projects. Open: KubeDL is open source community. Welcoming and respectful: See . Transparent and accessible: Work and collaboration should be done in public. Merit: Ideas and contributions are accepted according to their technical merit and alignment with project objectives, scope and design principles. Classify GitHub issues and perform pull request reviews for other maintainers and the community. Maintainers are expected to respond to assigned Pull Requests in a reasonable time frame. Participate when called upon in the security release process. Note that although this should be a rare occurrence, if a serious vulnerability is found, the process may take up to several full days of work to implement. We will expect you to have completed a reasonable amount of contributions in code, documentations etc. We will expect you to review other contributors' PRs in your area of expertise. We will expect you to have a good understanding about the project, and share responsibilities in maintaining the projects. Finally, talk to one of the existing project to show your interest in becoming a maintainer. The KubeDL community will never forcefully remove a current Maintainer, unless a maintainer fails to meet the principles of KubeDL community. Decisions are made based on consensus between maintainers. In extreme cases, a simple majority voting process is invoked where each maintainer receives one vote. Proposals and ideas can either be submitted for agreement via a github issue or PR. In general, we prefer that technical issues and maintainer membership are amicably worked out between the persons involved. If a dispute cannot be decided independently, get a third-party maintainer (e.g. a mutual contact with some background on the issue, but not involved in the conflict) to intercede and the final decision will be made. Decision making process should be transparent to adhere to the principles of KubeDL project. The KubeDL is aligned with the CNCF Code of Conduct. Some contents in this documents have been borrowed from .
Project: YugabyteDB (App Definition and Development / Database)
File: dp-results.md

title: dp-results linkTitle: dp-results headerTitle: Output from running dontile(), dopercentrank(), and documedist() on t4.dpscore description: Output from running dontile(), dopercentrank(), and documedist() on t4.dpscore. menu: v2.18: identifier: dp-results parent: normal-distribution-analysis-reports weight: 20 type: docs ``` Using ntile(). bucket | n | mins | maxs --+++ 1 | 5000 | 0.00000 | 33.41577 2 | 5000 | 33.41745 | 37.61929 3 | 5000 | 37.61952 | 40.42450 4 | 5000 | 40.42474 | 42.68859 5 | 5000 | 42.68912 | 44.63344 6 | 5000 | 44.63349 | 46.38263 7 | 5000 | 46.38321 | 47.97366 8 | 5000 | 47.97368 | 49.52608 9 | 5000 | 49.52624 | 51.02729 10 | 5000 | 51.02734 | 52.46619 11 | 5000 | 52.46621 | 53.92146 12 | 5000 | 53.92151 | 55.34590 13 | 5000 | 55.34603 | 56.86802 14 | 5000 | 56.86867 | 58.48624 15 | 5000 | 58.48660 | 60.24952 16 | 5000 | 60.24984 | 62.18791 17 | 5000 | 62.18821 | 64.47986 18 | 5000 | 64.47995 | 67.35160 19 | 5000 | 67.35283 | 71.46368 20 | 5000 | 71.46578 | 100.00000 Using percent_rank(). 1 | 5000 | 0.00000 | 33.41577 2 | 5000 | 33.41745 | 37.61929 3 | 5000 | 37.61952 | 40.42450 4 | 5000 | 40.42474 | 42.68859 5 | 5000 | 42.68912 | 44.63344 6 | 5000 | 44.63349 | 46.38263 7 | 5000 | 46.38321 | 47.97366 8 | 5000 | 47.97368 | 49.52608 9 | 5000 | 49.52624 | 51.02729 10 | 5000 | 51.02734 | 52.46619 11 | 5000 | 52.46621 | 53.92146 12 | 5000 | 53.92151 | 55.34590 13 | 5000 | 55.34603 | 56.86802 14 | 5000 | 56.86867 | 58.48624 15 | 5000 | 58.48660 | 60.24952 16 | 5000 | 60.24984 | 62.18791 17 | 5000 | 62.18821 | 64.47986 18 | 5000 | 64.47995 | 67.35160 19 | 5000 | 67.35283 | 71.46368 20 | 5000 | 71.46578 | 100.00000 Using cume_dist(). 1 | 5000 | 0.00000 | 33.41577 2 | 5000 | 33.41745 | 37.61929 3 | 5000 | 37.61952 | 40.42450 4 | 5000 | 40.42474 | 42.68859 5 | 5000 | 42.68912 | 44.63344 6 | 5000 | 44.63349 | 46.38263 7 | 5000 | 46.38321 | 47.97366 8 | 5000 | 47.97368 | 49.52608 9 | 5000 | 49.52624 | 51.02729 10 | 5000 | 51.02734 | 52.46619 11 | 5000 | 52.46621 | 53.92146 12 | 5000 | 53.92151 | 55.34590 13 | 5000 | 55.34603 | 56.86802 14 | 5000 | 56.86867 | 58.48624 15 | 5000 | 58.48660 | 60.24952 16 | 5000 | 60.24984 | 62.18791 17 | 5000 | 62.18821 | 64.47986 18 | 5000 | 64.47995 | 67.35160 19 | 5000 | 67.35283 | 71.46368 20 | 5000 | 71.46578 | 100.00000 ```
Project: KICS (Provisioning / Security & Compliance)
File: d740d048-8ed3-49d3-b77b-6f072f3b669e.md

title: StatefulSet Has No PodAntiAffinity hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d740d048-8ed3-49d3-b77b-6f072f3b669e Query name: StatefulSet Has No PodAntiAffinity Platform: Kubernetes Severity: <span style="color:#edd57e">Low</span> Category: Resource Management URL: Check if StatefulSet resources don't have a podAntiAffinity policy, which prevents multiple pods from being scheduled on the same node.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="53 23" apiVersion: apps/v1 kind: StatefulSet metadata: name: zk-mismatch spec: selector: matchLabels: app: zk serviceName: zk-hs replicas: 3 updateStrategy: type: RollingUpdate podManagementPolicy: OrderedReady template: metadata: labels: app: abc spec: affinity: podAntiAffinity: requiredDuringSchedulingIgnoredDuringExecution: labelSelector: matchLabels: app: zk topologyKey: "kubernetes.io/hostname" containers: name: kubernetes-zookeeper imagePullPolicy: Always image: "k8s.gcr.io/kubernetes-zookeeper:1.0-3.4.10" resources: requests: memory: "1Gi" cpu: "0.5" apiVersion: apps/v1 kind: StatefulSet metadata: name: zk-noaffinity spec: selector: matchLabels: app: zk serviceName: zk-hs replicas: 3 updateStrategy: type: RollingUpdate podManagementPolicy: OrderedReady template: metadata: labels: app: zk spec: affinity: podAffinity: requiredDuringSchedulingIgnoredDuringExecution: labelSelector: matchExpressions: key: app operator: In values: store topologyKey: "kubernetes.io/hostname" containers: name: kubernetes-zookeeper imagePullPolicy: Always image: "k8s.gcr.io/kubernetes-zookeeper:1.0-3.4.10" resources: requests: memory: "1Gi" cpu: "0.5" ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: apps/v1 kind: StatefulSet metadata: name: zk spec: selector: matchLabels: app: zk serviceName: zk-hs replicas: 3 updateStrategy: type: RollingUpdate podManagementPolicy: OrderedReady template: metadata: labels: app: zk spec: affinity: podAntiAffinity: requiredDuringSchedulingIgnoredDuringExecution: labelSelector: matchLabels: app: zk topologyKey: "kubernetes.io/hostname" containers: name: kubernetes-zookeeper imagePullPolicy: Always image: "k8s.gcr.io/kubernetes-zookeeper:1.0-3.4.10" resources: requests: memory: "1Gi" cpu: "0.5" ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_iam_service_account_key.md

+++ title = "googleiamserviceaccountkey resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleiamserviceaccountkey" identifier = "inspec/resources/gcp/googleiamserviceaccountkey.md googleiamserviceaccountkey resource" parent = "inspec/resources/gcp" +++ A `googleiamserviceaccountkey` is used to test a Google ServiceAccountKey resource ```ruby googleiamserviceaccountkeys(project: 'chef-gcp-inspec', serviceaccount: "display-name@project-id.iam.gserviceaccount.com").keynames.each do |sakeyname| describe end ``` Properties that can be accessed from the `googleiamserviceaccountkey` resource: `name` : The name of the key. `privatekeytype` : Output format for the service account key. `key_algorithm` : Specifies the algorithm for the key. `privatekeydata` : Private key data. Base-64 encoded. `publickeydata` : Public key data. Base-64 encoded. `validaftertime` : Key can only be used after this time. `validbeforetime` : Key can only be used before this time. `key_type` : Specifies the type of the key. Possible values include: KEYTYPEUNSPECIFIED USER_MANAGED SYSTEM_MANAGED `service_account` : The name of the serviceAccount. `path` : The full name of the file that will hold the service account private key. The management of this file will depend on the value of sync_file parameter. File path must be absolute. Ensure the is enabled for the current project.
Project: KICS (Provisioning / Security & Compliance)
File: dd706080-b7a8-47dc-81fb-3e8184430ec0.md

title: Public Security Group Rule Unknown Port hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: dd706080-b7a8-47dc-81fb-3e8184430ec0 Query name: Public Security Group Rule Unknown Port Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: A unknown port, such as port 24 or port 111, is open to the public in either TCP or UDP or ALL protocol/protocols mentioned<br> ```tf title="Positive test num. 1 - tf file" hl_lines="10" resource "alicloudsecuritygroup" "default" { name = "default" } resource "alicloudsecuritygrouprule" "allowall_tcp" { type = "ingress" ip_protocol = "tcp" nic_type = "internet" policy = "accept" port_range = "54/60" priority = 1 securitygroupid = alicloudsecuritygroup.default.id cidr_ip = "0.0.0.0/0" } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="10" resource "alicloudsecuritygroup" "default" { name = "default" } resource "alicloudsecuritygrouprule" "allowall_tcp" { type = "ingress" ip_protocol = "all" nic_type = "internet" policy = "accept" port_range = "-1/-1" priority = 1 securitygroupid = alicloudsecuritygroup.default.id cidr_ip = "0.0.0.0/0" } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudsecuritygroup" "default" { name = "default" } resource "alicloudsecuritygrouprule" "allowall_tcp" { type = "ingress" ip_protocol = "tcp" nic_type = "internet" policy = "accept" port_range = "1/65535" priority = 1 securitygroupid = alicloudsecuritygroup.default.id cidr_ip = "10.159.6.18/12" } ``` ```tf title="Negative test num. 2 - tf file" resource "alicloudsecuritygroup" "default" { name = "default" } resource "alicloudsecuritygrouprule" "allowall_tcp" { type = "ingress" ip_protocol = "icmp" nic_type = "internet" policy = "accept" port_range = "-1/-1" priority = 1 securitygroupid = alicloudsecuritygroup.default.id cidr_ip = "10.159.6.18/12" } ```
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: concepts.md

id: concepts title: Concepts description: A list of important permission framework concepts Any action that a user performs within Backstage may be represented as a permission. More complex actions, like executing a , may require for multiple permissions throughout the flow. Permissions are identified by a unique name and optionally include a set of attributes that describe the corresponding action. are responsible for defining and exposing the permissions they enforce as well as enforcing restrictions from the permission framework. User are authorized by a central, user-defined permission policy. At a high level, a policy is a function that receives a Backstage user and permission, and returns a decision to allow or deny. Policies are expressed as code, which decouples the framework from any particular model, like role-based access control (RBAC) or attribute-based access control (ABAC). Two important responsibilities of any authorization system are to decide if a user can do something, and to enforce that decision. In the Backstage permission framework, policies are responsible for decisions and plugins (typically backends) are responsible for enforcing them. In many cases, a permission represents a user's interaction with another object. This object likely has information that policy authors can use to define more granular access. The permission framework introduces two abstractions to account for this: and . For example, the catalog plugin defines a resource for catalog entities and a rule to check if an entity has a given annotation. need additional data before they can be used in a decision. Once a is bound to relevant information it forms a . Conditional decisions tell the to delegate evaluation to the that owns the corresponding . Permission requests that result in a conditional decision are allowed if all of the provided conditions evaluate to be true. A good example would be the catalog plugin's "has annotation" rule which needs to know what annotation to look for on a given entity. The permission framework would respond to a request by the catalog plugin in this case with a condition decision. The catalog plugin would then need to correctly filter for entities matching the "has annotations" condition. This conditional behavior avoids coupling between policies and resource schemas, and allows plugins to evaluate complex rules in an efficient way. For example, a plugin may convert a conditional decision to a database query instead of loading and filtering objects in memory.
Project: Tetragon (Provisioning / Security & Compliance)
File: kubernetes.md

title: "Deploy on Kubernetes" linkTitle: "Kubernetes" weight: 1 description: "Deploy and manage Tetragon on Kubernetes" The recommended way to deploy Tetragon on a Kubernetes cluster is to use the Helm chart with Helm 3. Tetragon uses the repository to release the helm chart. To install the latest release of the Tetragon helm chart, use the following command. {{< note >}} You can find the chart and its documentation with all available values for configuration in in the Tetragon repository. You can use any of the values and override them with `--set KEY1=VALUE1,KEY2=VALUE2`. {{< /note >}} ```shell helm repo add cilium https://helm.cilium.io helm repo update helm install tetragon cilium/tetragon -n kube-system ``` To wait until Tetragon deployment is ready, use the following `kubectl` command: ```shell kubectl rollout status -n kube-system ds/tetragon -w ``` {{< note >}} By default, pods in the kube-system namespace are filtered-out. {{< /note >}} {{< note >}} If Tetragon does not to start due to BTF issues, please refer to the for details and solutions. {{< /note >}} You can then make modifications to the Tetragon configuration using `helm upgrade`, see the following example. ```shell helm upgrade tetragon cilium/tetragon -n kube-system --set tetragon.grpc.address=localhost:1337 ``` You can also edit the `tetragon-config` ConfigMap directly and restart the Tetragon daemonset with: ```shell kubectl edit cm tetragon-config -n kube-system kubectl rollout restart ds/tetragon -n kube-system ``` Upgrade Tetragon using a new specific version of the helm chart. ```shell helm upgrade tetragon cilium/tetragon -n kube-system --version 0.9.0 ``` Uninstall Tetragon using the following command. ```shell helm uninstall tetragon -n kube-system ```
Project: YDB (App Definition and Development / Database)
File: debug.md

{% if tech %} {% if feature_webui %} | Value type | Default | | | | | Flag | false | An auxiliary setting for previewing tables in the (both for the web interface and console client). {% endif %} | Value type | Default | | | | | String: None/Lazy/Greedy | None | Validating whether UDF results match the declared signature. The Greedy mode enforces materialization of lazy containers, although the Lazy mode doesn't. | Value type | Default | | | | | A string with the cluster name | hahn | Selecting a cluster for calculations that don't access tables. | Value type | Default | | | | | Flag | false | Getting diagnostic information from YQL as an additional result of a query. {% endif %}
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_ui.md

title: "Command - devspace ui" sidebar_label: devspace ui Opens the localhost UI in the browser ``` devspace ui [flags] ``` ``` Opens the localhost UI in the browser ``` ``` --dev Ignore errors when downloading UI -h, --help help for ui --host string The host to use when opening the ui server (default "localhost") --port int The port to use when opening the ui server --server If enabled will force start a server (otherwise an existing UI server is searched) ``` ``` --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: Ansible (Provisioning / Automation & Configuration)
File: Unclear purpose or motivation.md

<! Describe the change below, including rationale and design decisions --> <! HINT: Include "Fixes #nnn" if you are fixing an existing issue --> <! Pick one below and delete the rest --> Bugfix Pull Request Docs Pull Request Feature Pull Request Test Pull Request <! Include additional information to help people understand the change here --> <! A step-by-step reproduction of the problem is helpful if there is no related issue --> <! Paste verbatim command output below, e.g. before and after your change --> ```paste below ```
Project: ArangoDB (App Definition and Development / Database)
File: on_result_construction.md

+++ title = "`static void onresultconstruction(T *, U &&) noexcept`" description = "(>= Outcome v2.2.0) Hook invoked by the implicit constructors of `basic_result`." categories = ["observer-policies"] weight = 450 +++ One of the constructor hooks for {{% api "basicresult<T, E, NoValuePolicy>" %}}, generally invoked by the implicit constructors of `basicresult`. See each constructor's documentation to see which specific hook it invokes. Requires: Always available. Guarantees: Never throws an exception.