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

title: ybm CLI api-key resource headerTitle: ybm api-key linkTitle: api-key description: YugabyteDB Managed CLI reference api-key resource. headcontent: Manage API keys menu: preview_yugabyte-cloud: identifier: managed-cli-api-key parent: managed-cli-reference weight: 20 type: docs Use the `api-key` resource to create and manage YugabyteDB Managed account . ```text Usage: ybm api-key [command] [flags] ``` Create an API key in YugabyteDB Managed: ```sh ybm api-key create \ --name developer \ --duration 6 --unit Months \ --description "Developer API key" \ --role-name Developer ``` List API keys in YugabyteDB Managed: ```sh ybm api-key list ``` Create an API key. | Flag | Description | | : | : | | --name | Required. Name for the API key. | | --duration | Required. The duration for which the API Key will be valid. 0 denotes that the key will never expire. | | --unit | Required. The time unit for the duration for which the API Key will be valid. `Hours`, `Days`, or `Months`. | | &#8209;&#8209;description | Description for the API key. | | --role-name | The name of the role to assign to the API Key. If not provided, the Admin role is assigned. | List the API keys in your YugabyteDB Managed account. | Flag | Description | | : | : | | --name | Return only API keys with the specified name. | | --status | Return only API keys with the specified status. `ACTIVE`, `EXPIRED`, or `REVOKED`. | Revoke a specified API key. | Flag | Description | | : | : | | --name | Required. Name of the API key to revoke. |
Project: KICS (Provisioning / Security & Compliance)
File: 816ea8cf-d589-442d-a917-2dd0ce0e45e3.md

title: SQS Policy Allows All Actions hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 816ea8cf-d589-442d-a917-2dd0ce0e45e3 Query name: SQS Policy Allows All Actions Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: SQS policy allows ALL (*) actions<br> ```tf title="Positive test num. 1 - tf file" hl_lines="8" resource "awssqsqueue" "positive1" { name = "examplequeue" } resource "awssqsqueue_policy" "positive2" { queueurl = awssqs_queue.q.id policy = <<POLICY { "Version": "2012-10-17", "Id": "sqspolicy", "Statement": [ { "Sid": "First", "Effect": "Allow", "Principal": "*", "Action": "*", "Resource": "${awssqsqueue.q.arn}", "Condition": { "ArnEquals": { "aws:SourceArn": "${awssnstopic.example.arn}" } } } ] } POLICY } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="12" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" versioning = { enabled = true } policy = <<POLICY { "Version": "2012-10-17", "Id": "sqspolicy", "Statement": [ { "Sid": "First", "Effect": "Allow", "Principal": "*", "Action": "*", "Resource": "${awssqsqueue.q.arn}", "Condition": { "ArnEquals": { "aws:SourceArn": "${awssnstopic.example.arn}" } } } ] } POLICY serversideencryption_configuration { rule { applyserversideencryptionby_default { kmsmasterkeyid = awskms_key.mykey.arn sse_algorithm = "aws:kms" } } } } ``` ```tf title="Negative test num. 1 - tf file" resource "awssqsqueue" "negative1" { name = "examplequeue" } resource "awssqsqueue_policy" "negative2" { queueurl = awssqs_queue.q.id policy = <<POLICY { "Version": "2012-10-17", "Id": "sqspolicy", "Statement": [ { "Sid": "First", "Effect": "Allow", "Principal": "*", "Action": "sqs:SendMessage", "Resource": "${awssqsqueue.q.arn}", "Condition": { "ArnEquals": { "aws:SourceArn": "${awssnstopic.example.arn}" } } } ] } POLICY } ``` ```tf title="Negative test num. 2 - tf file" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" versioning = { enabled = true } policy = <<POLICY { "Version": "2012-10-17", "Id": "sqspolicy", "Statement": [ { "Sid": "First", "Effect": "Allow", "Principal": "*", "Action": "sqs:SendMessage", "Resource": "${awssqsqueue.q.arn}", "Condition": { "ArnEquals": { "aws:SourceArn": "${awssnstopic.example.arn}" } } } ] } POLICY serversideencryption_configuration { rule { applyserversideencryptionby_default { kmsmasterkeyid = awskms_key.mykey.arn sse_algorithm = "aws:kms" } } } } ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_sql_users.md

+++ title = "googlesqlusers resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlesqlusers" identifier = "inspec/resources/gcp/googlesqlusers.md googlesqlusers resource" parent = "inspec/resources/gcp" +++ A `googlesqlusers` is used to test a Google User resource ```ruby describe googlesqlusers(project: 'chef-gcp-inspec', database: 'my-database') do its('user_names') { should include 'user-name' } end ``` describe googlesqlusers(project: 'chef-inspec-gcp', database: 'database-instance') do its('count') { should be <= 100} end describe googlesqlusers(project: 'chef-inspec-gcp') do its('user_names') { should include "us-east1-b" } end describe googlesqlusers(project: 'chef-inspec-gcp') do its('userstatuses') { shouldnot include "DOWN" } end googlesqldatabaseinstances(project: 'chef-inspec-gcp').instancenames.each do |instance_name| describe googlesqlusers(project: 'chef-inspec-gcp', database: instance_name) do it { should exist } end end Properties that can be accessed from the `googlesqlusers` resource: See the resource for more information. `user_hosts` : an array of `googlesqluser` host `user_names` : an array of `googlesqluser` name `user_instances` : an array of `googlesqluser` instance `passwords` : an array of `googlesqluser` password This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: ArangoDB (App Definition and Development / Database)
File: fail_to_compile_observers.md

+++ title = "`failtocompile_observers`" description = "Policy class defining that a static assertion should occur upon compilation of the wide value, error or exception observation. Inherits publicly from `base`." +++ Upon attempting to compile the wide observer policy functions, the following static assertion occurs which fails the build: Attempt to wide observe value, error or exception for a result/outcome given an EC or E type which is not void, and for whom trait::has_error_code_v<EC>, trait::has_exception_ptr_v<EC>, and trait::has_exception_ptr_v<E> are all false. Please specify a NoValuePolicy to tell result/outcome what to do, or else use a more specific convenience type alias such as unchecked<T, E> to indicate you want the wide observers to be narrow, or checked<T, E> to indicate you always want an exception throw etc. This failure to compile was introduced after the Boost peer review of v2.0 of Outcome due to feedback that users were too often surprised by the default selection of the {{% api "all_narrow" %}} policy if the types were unrecognised. It was felt this introduced too much danger in the default configuration, so to ensure that existing code based on Outcome broke very loudly after an upgrade, the above very verbose static assertion was implemented. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::policy` Header: `<boost/outcome/policy/failtocompile_observers.hpp>`
Project: ClickHouse (App Definition and Development / Database)
File: v20.6.5.8-stable.md

Backported in : Slightly optimize very short queries with LowCardinality. (). Backported in : Fix wrong error for long queries. It was possible to get syntax error other than `Max query size exceeded` for correct query. (). Backported in : Removed wrong auth access check when using ClickHouseDictionarySource to query remote tables. (). Backported in : Fix missing or excessive headers in `TSV/CSVWithNames` formats. This fixes . (). Backported in : Fixed the deadlock in textlog. It is a part of . This fixes . (). Backported in : Fix wrong code in function `netloc`. This fixes . (). Backported in : Fix premature `ON CLUSTER` timeouts for queries that must be executed on a single replica. Fixes , Fixes , Fixes , Fixes . (). Backported in : Fixed the behaviour when sometimes cache-dictionary returned default value instead of present value from source. (). Backported in : Fix visible data clobbering by progress bar in client in interactive mode. This fixes and and and fixes . (). Backported in : Fixes /replicas_status endpoint response status code when verbose=1. (). Backported in : Fix logging Settings.Names/Values when logqueriesmintype > QUERYSTART. (). Backported in : Fix race condition between DETACH and background merges. Parts may revive after detach. This is continuation of that did not fix the issue but introduced a test that started to fail in very rare cases, demonstrating the issue. (). Backported in : Add range check for h3KRing function. This fixes . (). Backported in : Fix step overflow in range(). (). Backported in : Fix reading from MergeTree table with INDEX of type SET fails when comparing against NULL. This fixes . (). Backported in : Fix topK/topKWeighted merge (with non-default parameters). (). Backported in : Fixed potential deadlock when renaming `Distributed` table. (). Backported in : Fix wrong results in select queries with `DISTINCT` keyword in case `optimizeduplicateorderbyand_distinct` setting is enabled. (). Backported in : Fixed wrong mount point in extra info for `Poco::Exception: no space left on device`. (). Backported in : Fix pointInPolygon with const 2d array as polygon. (). Backported in : Fix creation of tables with named tuples. This fixes . (). Backported in : Fix crash when INERT INTO Kafka engine table from an empty result set with a subquery. ... (). Backported in : Fixed incorrect sorting order if LowCardinality column. This fixes . (). Backported in : Fix segfault in `clickhouse-odbc-bridge` during schema fetch from some external sources. This PR fixes . (). Backported in : Fix crash during `ALTER` query for table which was created `AS table_function`. Fixes . ().
Project: KICS (Provisioning / Security & Compliance)
File: b6a7e0ae-aed8-4a19-a993-a95760bf8836.md

title: DynamoDB Table Not Encrypted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b6a7e0ae-aed8-4a19-a993-a95760bf8836 Query name: DynamoDB Table Not Encrypted Platform: Pulumi Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: AWS DynamoDB Tables should have serverSideEncryption enabled<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="17 7" name: aws-eks runtime: yaml description: An EKS cluster resources: example: type: aws:dynamodb:Table properties: name: aws-eks runtime: yaml description: An EKS cluster resources: example: type: aws:dynamodb:Table properties: serverSideEncryption: enabled: false ``` ```yaml title="Negative test num. 1 - yaml file" name: aws-eks runtime: yaml description: An EKS cluster resources: example: type: aws:dynamodb:Table properties: serverSideEncryption: enabled: true ```
Project: KICS (Provisioning / Security & Compliance)
File: 6a647814-def5-4b85-88f5-897c19f509cd.md

title: Redshift Not Encrypted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6a647814-def5-4b85-88f5-897c19f509cd Query name: Redshift Not Encrypted Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: AWS Redshift Cluster should be encrypted. Check if 'encrypted' field is false or undefined (default is false)<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="2 19 29" name: Basic cluster provisioning example community.aws.redshift: identifier: tf-redshift-cluster command: create db_name: mydb username: foo password: Mustbe8characters node_type: dc1.large cluster_type: single-node name: Basic cluster provisioning example2 community.aws.redshift: identifier: tf-redshift-cluster command: create db_name: mydb username: foo password: Mustbe8characters node_type: dc1.large cluster_type: single-node encrypted: false name: Basic cluster provisioning example3 community.aws.redshift: identifier: tf-redshift-cluster command: create db_name: mydb username: foo password: Mustbe8characters node_type: dc1.large cluster_type: single-node encrypted: no ``` ```yaml title="Negative test num. 1 - yaml file" name: Basic cluster provisioning example community.aws.redshift: identifier: tf-redshift-cluster command: create db_name: mydb username: foo password: Mustbe8characters node_type: dc1.large cluster_type: single-node encrypted: true name: Basic cluster provisioning example2 community.aws.redshift: identifier: tf-redshift-cluster command: create db_name: mydb username: foo password: Mustbe8characters node_type: dc1.large cluster_type: single-node encrypted: yes ```
Project: Cerbos (Provisioning / Security & Compliance)
File: pull_request_template.md

<!-- Thank you for contributing Cerbos! Please describe the changes made in this PR here and provide any other useful information for reviewers. Make sure that you included some automated tests (e.g unit tests) to verify your changes. If there is a requirement for user input for testing, please include the instructions as well. --> Fixes #<!-- Link the relevant issue here --> <!-- See https://github.com/cerbos/cerbos/blob/main/CONTRIBUTING.md#submitting-pull-requests for more information. --> [ ] The PR title has the correct prefix [ ] PR is linked to the corresponding issue
Project: YugabyteDB (App Definition and Development / Database)
File: savepoint_release.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="308" height="50" viewbox="0 0 308 50"><path class="connector" d="M0 22h15m75 0h30m89 0h20m-124 0q5 0 5 5v8q0 5 5 5h99q5 0 5-5v-8q0-5 5-5m5 0h10m54 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="75" height="25" rx="7"/><text class="text" x="25" y="22">RELEASE</text><rect class="literal" x="120" y="5" width="89" height="25" rx="7"/><text class="text" x="130" y="22">SAVEPOINT</text><a xlink:href="../../../syntaxresources/grammardiagrams#name"><rect class="rule" x="239" y="5" width="54" height="25"/><text class="text" x="249" y="22">name</text></a><polygon points="304,29 308,29 308,15 304,15" style="fill:black;stroke-width:0"/></svg>
Project: Crunchy Postgres Operator (App Definition and Development / Database)
File: support---question-and-answer.md

name: Support about: "Learn how to interact with the PGO community" If you believe you have found have found a bug, please open up If you have a feature request, please open up a You can find information about general PGO at: For questions that are neither bugs nor feature requests, please be sure to [ ] Provide information about your environment (see below for more information). [ ] Provide any steps or other relevant details related to your question. [ ] Attach logs, where applicable. Please do not attach screenshots showing logs unless you are unable to copy and paste the log data. for legibility. Besides Pod logs, logs may also be found in the `/pgdata/pg<MAJOR_VERSION>/log` directory on your Postgres instance. If you are looking for , please view the page for where you can ask questions. Please provide the following details: Platform: (`Kubernetes`, `OpenShift`, `Rancher`, `GKE`, `EKS`, `AKS` etc.) Platform Version: (e.g. `1.20.3`, `4.7.0`) PGO Image Tag: (e.g. `ubi8-5.x.y-0`) Postgres Version (e.g. `15`) Storage: (e.g. `hostpath`, `nfs`, or the name of your storage class)
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: troubleshoting.md

title: Troubleshooting KubeDB Installation description: Troubleshooting guide for KubeDB installation menu: docs_{{ .version }}: identifier: install-kubedb-troubleshoot name: Troubleshooting parent: installation-guide weight: 40 product_name: kubedb menuname: docs{{ .version }} sectionmenuid: setup If you are installing KubeDB on a GKE cluster, you will need cluster admin permissions to install KubeDB operator. Run the following command to grant admin permision to the cluster. ```bash $ kubectl create clusterrolebinding "cluster-admin-$(whoami)" \ --clusterrole=cluster-admin \ --user="$(gcloud config get-value core/account)" ``` In addition, if your GKE cluster is a , you will need to either add an additional firewall rule that allows master nodes access port `8443/tcp` on worker nodes, or change the existing rule that allows access to ports `443/tcp` and `10250/tcp` to also allow access to port `8443/tcp`. The procedure to add or modify firewall rules is described in the official GKE documentation for private clusters mentioned before. To detect KubeDB version, exec into the operator pod and run `kubedb version` command. ```bash $ POD_NAMESPACE=kubedb $ PODNAME=$(kubectl get pods -n $PODNAMESPACE -l app.kubernetes.io/name=kubedb-community -o jsonpath={.items[0].metadata.name}) $ kubectl exec $PODNAME -c operator -n $PODNAMESPACE -- /operator version Version = v0.20.0 VersionStrategy = tag GitTag = v0.20.0 GitBranch = HEAD CommitHash = c24b636ea015b1f4e7be84ec206f123501fa148a CommitTimestamp = 2021-08-23T11:15:37 GoVersion = go1.16.7 Compiler = gcc Platform = linux/amd64 ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: support_derived_platforms.md

| Platform | Architecture | Version | Parent platform | | | | | | | AlmaLinux | `x86_64`, `aarch64` | `8.x` | CentOS | | Rocky Linux | `x86_64`, `aarch64` | `8.x` | CentOS | Chef InSpec Target Mode (`inspec --target`) may be functional on additional platforms, versions, and architectures but arent validated by Chef.
Project: KubeArmor (Provisioning / Security & Compliance)
File: kubearmor_apparmor_implementation_overview.md

Kubearmor support enforcing policies on systems running apparmor. Upon the detection of a new Pod or a new policy, KubeArmor will launch a policy matching process that works as follow: If a new pod is detected, KubeArmor will only search for policies that matches that perticular pod. If a new policy is detected, KubeArmor will search for all pods that the policy include. When all policies are identified, KubeArmor combines all policies into a single policy. If two policies are conflicting KubeArmor will resolve this conflict. Once we have a single policy, KubeArmor will generate and load the corresponding AppArmor profile(s). KubeArmor makes a heavy use of apparmor domain transition in order to honor `fromSource` rules. The domain transion is made possible using the `px` permission in apparmor. The above figure illustrate how we decide that we need to perform a domain transition for a certain binary. Pods with additional capabilities are supported across all runtimes, hence apparmor profiles can be set here. We provide more capabilities than docker default profile to make them work. On containerd runtime, we are able to use apparmor profiles to secure privileged pods. However on cri-o and docker runtimes, they do not allow us to set any apparmor profile for privileged pods.
Project: TDengine (App Definition and Development / Database)
File: 10-hive-mq-broker.md

title: HiveMQ Broker Writing sidebar_label: HiveMQ Broker description: This document describes how to integrate TDengine with the HiveMQ broker. is an MQTT broker that provides community and enterprise editions. HiveMQ is mainly for enterprise emerging machine-to-machine M2M communication and internal transport, meeting scalability, ease of management, and security features. HiveMQ provides an open-source plug-in development kit. MQTT data can be saved to TDengine via TDengine extension for HiveMQ. For more information, see .
Project: MongoDB (App Definition and Development / Database)
File: s390x_build_from_source.md

Bazel doesn't release to the S390X architecture. To address this, MongoDB maintains our own Bazel build that we perform on our S390X development systems. Bazel usually comes with a built-in JDK. However, the tooling used to build the built-in JDK doesn't support S390X. To get around this, an external JDK must be present on both the system compiling the Bazel executable itself as well as the host running Bazel as a build system. On the MongoDB S390X Evergreen static hosts and dev hosts, the OpenJDK 11 installation exists at: /usr/lib/jvm/java-11-openjdk-11.0.11.0.9-0.el8_3.s390x To compile with on these platforms, the developer must set JAVA_HOME before invoking Bazel. curl -O -L https://github.com/bazelbuild/bazel/releases/download/6.4.0/bazel-6.4.0-dist.zip unzip bazel-6.4.0-dist.zip JAVAHOME=/usr/lib/jvm/java-11-openjdk-11.0.11.0.9-0.el83.s390x ./compile.sh
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-exp-relationship-view.md

layout: default title: mesheryctl-exp-relationship-view permalink: reference/mesheryctl/exp/relationship/view redirect_from: reference/mesheryctl/exp/relationship/view/ type: reference display-title: "false" language: en command: exp subcommand: relationship view relationships of a model by its name view a relationship queried by the model name <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp relationship view [flags] </div> </pre> View relationships of a model <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp relationship view [model-name] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for view -o, --output-format string (optional) format to display in [json| yaml] (default "yaml") </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -v, --verbose verbose output </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-volume-prune.1.md

% podman-volume-prune 1 podman\-volume\-prune - Remove all unused volumes podman volume prune [options] Removes unused volumes. By default all unused volumes are removed, the --filter flag can be used to filter specific volumes. Users are prompted to confirm the removal of all the unused volumes. To bypass the confirmation, use the --force flag. Provide filter values. The filters argument format is of `key=value`. If there is more than one filter, then pass multiple OPTIONS: --filter foo=bar --filter bif=baz. Supported filters: | Filter | Description | |:--:|| | dangling | [Bool] Only remove volumes not referenced by any containers | | driver | [String] Only remove volumes with the given driver | | label | [String] Only remove volumes, with (or without, in the case of label!=[...] is used) the specified labels. | | name | [String] Only remove volume with the given name | | opt | [String] Only remove volumes created with the given options | | scope | [String] Only remove volumes with the given scope | | until | [DateTime] Only remove volumes created before given timestamp. | | after/since | [Volume] Filter by volumes created after the given VOLUME (name or tag) | The `label` filter accepts two formats. One is the `label`=key or `label`=key=value, which removes volumes with the specified labels. The other format is the `label!`=key or `label!`=key=value, which removes volumes without the specified labels. The `until` filter can be Unix timestamps, date formatted timestamps, or Go duration strings (e.g. 10m, 1h30m) computed relative to the machines time. Do not prompt for confirmation. Print usage statement Prune all unused volumes. ``` $ podman volume prune ``` Prune all volumes. Note: this command will also remove all containers that are using a volume. ``` $ podman volume prune --force ``` Prune all volumes that contain the specified label. ``` $ podman volume prune --filter label=mylabel=mylabelvalue ``` , November 2018, Originally compiled by Urvashi Mohnani <umohnani@redhat.com>