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

RabbitMQ `3.9.7` is a maintenance release in the `3.9.x` release series. Please refer to the Upgrading to 3.9 section from if upgrading from a version prior to 3.9.0. This release requires at least Erlang 23.2, and supports the latest Erlang 24 version, 24.0.5 at the time of release. has more details on Erlang version requirements for RabbitMQ. Release notes are kept under . Contributors are encouraged to update them together with their changes. This helps with release automation and a more consistent release schedule. All bytecode is now compiled using the `+deterministic` compiler flag. This should eliminate the capture of some irrelevant build environment attributes in produced artifacts, improve consistency between builds, and reduce the file level diff between release artifacts. GitHub issue: Classic queue shutdown now uses a much higher timeout (up to 10 minutes instead of 30 seconds). In environments with many queues (especially mirrored queues) and many consumers this means that the chance of queue indices rebuilding after node restart is now substantially lower. GitHub issue: Quorum queues no longer leak memory and disk space when a consumer is repeatedly added and cancelled on an empty queue. GitHub issue: More configurability for metrics exposed via the Prometheus endpoint. GitHub issue: Shovel URIs could be logged with credentials in some scenarios. GitHub issue: , contributed by @thuandb (AWS) observer_cli has been upgraded from `1.6.2` to `1.7.1` To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.7.tar.xz` instead of the source tarball produced by GitHub.
Project: StarRocks (App Definition and Development / Database)
File: DESC_STORAGE_VOLUME.md

displayed_sidebar: "English" Describes a storage volume. This feature is supported from v3.1. CAUTION Only users with the USAGE privilege on a specific storage volume can perform this operation. ```SQL DESC[RIBE] STORAGE VOLUME <storagevolumename> ``` | Parameter | Description | | - | - | | storagevolumename | The name of the storage volume to describe. | | Return | Description | | - | | | Name | The name of the storage volume. | | Type | The type of the remote storage system. Valid values: `S3` and `AZBLOB`. | | IsDefault | Whether the storage volume is the default storage volume. | | Location | The location of the remote storage system. | | Params | The credential information used to access the remote storage system. | | Enabled | Whether the storage volume is enabled. | | Comment | The comment on the storage volume. | Example 1: Describe the storage volume `mys3volume`. ```Plain MySQL > DESCRIBE STORAGE VOLUME mys3volume\G row * Name: mys3volume Type: S3 IsDefault: false Location: s3://defaultbucket/test/ Params: {"aws.s3.accesskey":"xxxxxxxxxx","aws.s3.secretkey":"yyyyyyyyyy","aws.s3.endpoint":"https://s3.us-west-2.amazonaws.com","aws.s3.region":"us-west-2","aws.s3.useinstanceprofile":"true","aws.s3.useawssdkdefaultbehavior":"false"} Enabled: false Comment: 1 row in set (0.00 sec) ```
Project: YugabyteDB (App Definition and Development / Database)
File: pttl.md

title: PTTL linkTitle: PTTL description: PTTL menu: preview: parent: api-yedis weight: 2235 aliases: /preview/api/redis/pttl /preview/api/yedis/pttl type: docs `PTTL key` Similar to TTL this command returns the remaining time to live of a key that has a timeout set, with the sole difference that TTL returns the amount of remaining time in seconds while PTTL returns it in milliseconds. Returns TTL in milliseconds, encoded as integer response. ```sh $ SET yugakey "Yugabyte" ``` ``` "OK" ``` ```sh $ EXPIRE yugakey 10 ``` ``` (integer) 1 ``` ```sh $ PTTL yugakey ``` ``` (integer) 9995 ``` , , ,
Project: ArangoDB (App Definition and Development / Database)
File: hook_outcome_copy_construction2.md

+++ title = "`void hookoutcomecopy_construction(T *, U &&, V &&) noexcept`" description = "(Until v2.2.0) ADL discovered free function hook invoked by the converting copy constructors of `basic_outcome`." +++ Removed in Outcome v2.2.0, unless {{% api "BOOSTOUTCOMEENABLELEGACYSUPPORT_FOR" %}} is set to less than `220` to enable emulation. Use {{% api "onoutcomecopy_construction(T *, U &&, V &&) noexcept" %}} instead in new code. One of the constructor hooks for {{% api "basicoutcome<T, EC, EP, NoValuePolicy>" %}}, generally invoked by the converting copy constructors of `basicoutcome` (NOT the standard copy constructor) which consume two arguments. See each constructor's documentation to see which specific hook it invokes. Overridable: By Argument Dependent Lookup. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::hooks` Header: `<boost/outcome/basic_outcome.hpp>`
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: pomerium-authz.md

title: Pomerium Access Proxy labels: layer: network category: proxy software: pomerium blogs: https://www.pomerium.io/posts/2020/04/16/release-0-7/ code: https://github.com/pomerium/pomerium Pomerium is an identity-aware proxy that enables secure access to internal applications. OPA implements authorization under the hood.
Project: Meshery (Provisioning / Automation & Configuration)
File: 09-29-2022-17-42-09_8c17f987.md

timestamp: "2022-09-29 17:42:05 UTC Thu" meshery-component: meshery-consul meshery-component-version: v0.6.2 meshery-server-version: "v0.6.9" k8s-distro: minikube k8s-version: "v1.20.11" service-mesh: Consul service-mesh-version: "v0.48.0" tests: consul-client: null consul-server: null overall-status: "failing"
Project: Distribution (Provisioning / Container Registry)
File: ADOPTERS.md

Docker Hub https://hub.docker.com/ GitLab Container Registry https://docs.gitlab.com/ee/user/packages/container_registry/ GitHub Container Registry https://docs.github.com/en/free-pro-team@latest/packages/guides/about-github-container-registry Harbor, CNCF Graduated project https://goharbor.io/ VMware Harbor Registry https://docs.pivotal.io/partners/vmware-harbor/index.html DigitalOcean Container Registry https://www.digitalocean.com/products/container-registry/
Project: ArangoDB (App Definition and Development / Database)
File: implicit_error_converting_constructor.md

+++ title = "`basic_result(S &&)`" description = "Implicit `errortype` constructor. Available if `predicate::enableerrorconvertingconstructor<S>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "implicit-constructors", "converting-constructors"] weight = 190 +++ Implicit `errortype` constructor. Calls {{% api "void onresult_construction(T *, U &&) noexcept" %}} with `this` and `S`. Requires: `predicate::enableerrorconverting_constructor<S>` is true. Complexity: Same as for `error_type`'s copy or move constructor. Constexpr, triviality and noexcept of underlying operations is propagated.
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.2.0.4-alpha.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Minor | protoc maven plugin doesn't work on mvn 3.0.2* Committed to 2.0.4-alpha branch | Major | MiniMRCluster should use a random component when creating an actual cluster* Committed to branch-2.0.4. Modified changes.txt in trunk, branch-2 and branch-2.0.4 accordingly.
Project: KICS (Provisioning / Security & Compliance)
File: 722b0f24-5a64-4cca-aa96-cfc26b7e3a5b.md

title: Unknown Port Exposed To Internet hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 722b0f24-5a64-4cca-aa96-cfc26b7e3a5b Query name: Unknown Port Exposed To Internet Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: AWS Security Group should not have an unknown port exposed to the entire Internet<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="9 13" name: example ec2 group amazon.aws.ec2_group: name: example description: an example EC2 group vpc_id: 12345 region: eu-west-1 rules: proto: tcp from_port: 8001 to_port: 8002 cidr_ip: 0.0.0.0/0 proto: tcp from_port: 2222 to_port: 2226 cidr_ipv6: ::/0 ``` ```yaml title="Negative test num. 1 - yaml file" name: example ec2 group amazon.aws.ec2_group: name: example description: an example EC2 group vpc_id: 12345 region: eu-west-1 rules: proto: tcp from_port: 80 to_port: 80 cidr_ip: 0.0.0.0/0 proto: tcp from_port: 22 to_port: 22 cidr_ip: 10.0.0.0/8 ```
Project: Harbor (Provisioning / Container Registry)
File: 1-14-LDAP-admin-role-general.md

Test 1-14 - LDAP Mode Admin Role General Functions ======= To verify that Harbor's UI of a user with system admin role works properly in LDAP mode. User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against an AD or LDAP server. (auth_mode is set to ldap_auth* .) An Active Directory (AD) or LDAP server has been set up and it has a few users available for testing. NOTE: The below non-admin user M should NOT be the same as the non-admin user in Test 1-07. Assign an non-admin user M with system admin role and act as an admin user. Repeat all steps in Test 1-07. A user with system admin role can perform all operations the same as the admin user. Same as Test 1-07. None
Project: ClickHouse (App Definition and Development / Database)
File: v21.11.6.7-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix skipping columns while writing protobuf. This PR fixes , see the comment #issuecomment-980595318. (). Backported in : Fix bug when remove unneeded columns in subquery. If there is an aggregation function in query without group by, do not remove if it is unneeded. (). Backported in : Fix crash when function `dictGet` with type is used for dictionary attribute when type is `Nullable`. Fixes . (). Backported in : Fix recursive user defined functions crash. Closes . (). Backported in : Fixed `Directory ... already exists and is not empty` error when detaching part. (). Backported in : Fix `CAST` from `Nullable` with `castkeepnullable` (`PARAMETEROUTOF_BOUND` error before for i.e. `toUInt32OrDefault(toNullable(toUInt32(1)))`). (). Backported in : Dictionaries fix cases when `{condition}` does not work for custom database queries. (). Backported in : Fix 'APPLY lambda' parsing which could lead to client/server crash. (). Backported in : Number of active replicas might be determined incorrectly when inserting with quorum if setting `replicatedcanbecome_leader` is disabled on some replicas. It's fixed. (). Backported in : XML dictionaries identifiers, used in table create query, can be qualified to `default_database` during upgrade to newer version. Closes . (). Backported in : Fixed crash with SIGFPE in aggregate function `avgWeighted` with `Decimal` argument. Fixes . (). Backported in : Fix `ALTER ... MATERIALIZE COLUMN ...` queries in case when data type of default expression is not equal to the data type of column. (). Backported in : Fixed the behavior when mutations that have nothing to do are stuck (with enabled setting `emptyresultforaggregationbyemptyset`). (). NO CL ENTRY: 'Manual backport of into 21.11'. (). Fix data race in `removePartAndEnqueueFetch(...)` (). Fix possible Pipeline stuck in case of StrictResize processor. ().
Project: Meshery (Provisioning / Automation & Configuration)
File: running.md

layout: default title: Troubleshooting Errors while running Meshery abstract: Troubleshooting Meshery errors when running make run-fast / meshery system start permalink: guides/troubleshooting/meshery-server redirect_from: guides/troubleshooting/running type: guides category: troubleshooting language: en Error: ``` mesheryctl system start : : cannot start Meshery: rendered manifests contain a resource that already exists. Unable to continue with install: ServiceAccount "meshery-operator" in namespace "meshery" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "meshery"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "meshery" ``` (Fix) Clean the cluster using : <pre class="codeblock-pre"><div class="codeblock"> <div class="clipboardjs"> kubectl delete ns meshery kubectl delete clusterroles.rbac.authorization.k8s.io meshery-controller-role meshery-operator-role meshery-proxy-role meshery-metrics-reader kubectl delete clusterrolebindings.rbac.authorization.k8s.io meshery-controller-rolebinding meshery-operator-rolebinding meshery-proxy-rolebinding </div></div> </pre> Issue Reference : Error: ``` FATA[0000] constraints not implemented on sqlite, consider using DisableForeignKeyConstraintWhenMigrating, more details https://github.com/go-gorm/gorm/wiki/GORM-V2-Release-Note-Draft#all-new-migrator exit status 1 make: * [Makefile:76: server] Error 1 ``` Fix: Flush the database by deleting the `.meshery/config` `make server`
Project: KICS (Provisioning / Security & Compliance)
File: 96e8183b-e985-457b-90cd-61c0503a3369.md

title: Global Accelerator Flow Logs Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 96e8183b-e985-457b-90cd-61c0503a3369 Query name: Global Accelerator Flow Logs Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Global Accelerator should have flow logs enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsglobalacceleratoraccelerator" "positive1" { name = "Example" ipaddresstype = "IPV4" enabled = true } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="6" resource "awsglobalacceleratoraccelerator" "positive2" { name = "Example" ipaddresstype = "IPV4" enabled = true attributes { flowlogss3_bucket = "example-bucket" flowlogss3_prefix = "flow-logs/" } } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="7" resource "awsglobalacceleratoraccelerator" "positive3" { name = "Example" ipaddresstype = "IPV4" enabled = true attributes { flowlogsenabled = false } } ``` ```tf title="Negative test num. 1 - tf file" resource "awsglobalacceleratoraccelerator" "negative1" { name = "Example" ipaddresstype = "IPV4" enabled = true attributes { flowlogsenabled = true flowlogss3_bucket = "example-bucket" flowlogss3_prefix = "flow-logs/" } } ```
Project: KICS (Provisioning / Security & Compliance)
File: 522d4a64-4dc9-44bd-9240-7d8a0d5cb5ba.md

title: Permissive Access to Create Pods hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 522d4a64-4dc9-44bd-9240-7d8a0d5cb5ba Query name: Permissive Access to Create Pods Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: The permission to create pods in a cluster should be restricted because it allows privilege escalation.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="51 67 35 13" resource "kubernetes_role" "example1" { metadata { name = "terraform-example1" labels = { test = "MyRole" } } rule { api_groups = [""] resources = ["pods"] resource_names = ["foo"] verbs = ["create", "list", "watch"] } rule { api_groups = ["apps"] resources = ["deployments"] verbs = ["get", "list"] } } resource "kubernetes_role" "example2" { metadata { name = "terraform-example2" labels = { test = "MyRole" } } rule { api_groups = [""] resources = ["*"] resource_names = ["foo"] verbs = ["create", "list", "watch"] } } resource "kubernetes_role" "example3" { metadata { name = "terraform-example3" labels = { test = "MyRole" } } rule { api_groups = [""] resources = ["pods"] resource_names = ["foo"] verbs = ["*", "list", "watch"] } } resource "kubernetes_role" "example4" { metadata { name = "terraform-example4" labels = { test = "MyRole" } } rule { api_groups = [""] resources = ["*"] resource_names = ["foo"] verbs = ["*", "list", "watch"] } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="9 45 21 33" resource "kubernetesclusterrole" "example1" { metadata { name = "terraform-example1" } rule { api_groups = [""] resources = ["namespaces", "pods"] verbs = ["create", "list", "watch"] } } resource "kubernetesclusterrole" "example2" { metadata { name = "terraform-example2" } rule { api_groups = [""] resources = ["namespaces", "*"] verbs = ["create", "list", "watch"] } } resource "kubernetesclusterrole" "example3" { metadata { name = "terraform-example3" } rule { api_groups = [""] resources = ["namespaces", "*"] verbs = ["*", "list", "watch"] } } resource "kubernetesclusterrole" "example4" { metadata { name = "terraform-example4" } rule { api_groups = [""] resources = ["namespaces", "pods"] verbs = ["*", "list", "watch"] } } ``` ```tf title="Negative test num. 1 - tf file" resource "kubernetes_role" "example" { metadata { name = "terraform-example" labels = { test = "MyRole" } } rule { api_groups = [""] resources = ["pods"] resource_names = ["foo"] verbs = ["get", "list", "watch"] } rule { api_groups = ["apps"] resources = ["deployments"] verbs = ["get", "list"] } } ``` ```tf title="Negative test num. 2 - tf file" resource "kubernetesclusterrole" "example" { metadata { name = "terraform-example" } rule { api_groups = [""] resources = ["namespaces", "pods"] verbs = ["get", "list", "watch"] } } ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: json.md

+++ title = "json resource" draft = false gh_repo = "inspec" platform = "os" [menu] [menu.inspec] title = "json" identifier = "inspec/resources/os/json.md json resource" parent = "inspec/resources/os" +++ Use the `json` Chef InSpec audit resource to test data in a JSON file. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `json` resource block declares the data to be tested. Assume the following JSON file: { "name" : "hello", "meta" : { "creator" : "John Doe" }, "array": [ "zero", "one" ] } This file can be queried using: describe json('/path/to/name.json') do its('name') { should eq 'hello' } its(['meta','creator']) { should eq 'John Doe' } its(['array', 1]) { should eq 'one' } end where `name` is a configuration setting in a JSON file `should eq 'foo'` tests a value of `name` as read from a JSON file versus the value declared in the test The `json` resource can also be used with JSON formatted output from a command. Using the same JSON as the previous example, it can be queried using: describe json({ command: 'retrieve_data.py --json'}) do its('name') { should eq 'hello' } its(['meta','creator']) { should eq 'John Doe' } its(['array', 1]) { should eq 'one' } end Finally, content can be passed directly to the resource: describe json({ content: '{\"item1\": { \"status\": \"available\" } }' }) do its(['item1', 'status']) { should cmp 'available' } end The following examples show how to use this Chef InSpec audit resource. The `name` matcher tests the value of the filename as read from a JSON file versus the value declared in the test: its('name') { should eq '/tmp/example.json' } describe json('policyfile.lock.json') do its(['cookbook_locks', 'omnibus', 'version']) { should eq('2.2.0') } end Our example API has a `/health` endpoint, which looks like this: { "service": { "port": 3000, "status": "ok" } } Example test: describe json(content: http('http://localhost:3000/health').body) do its(['service', 'port']) { should eq 3000 } its(['service', 'status']) { should eq 'ok' } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: KubeZoo (Provisioning / Automation & Configuration)
File: GOVERNANCE.md

The governance model adopted in KubeZoo is influenced by many CNCF projects. Open: KubeZoo is open source community. See (TODO: add Contributor License Agreement). 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. The KubeZoo is aligned with the CNCF Code of Conduct. See community membership (TODO: add community membership). Decisions are made based on consensus between maintainers. Proposals and ideas can either be submitted for agreement via a github issue or PR, or by sending an email to (TODO: register an email for the org). 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 KubeZoo project. Some contents in this documents have been borrowed from , , and projects.
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: edge-tuning.md

We need to have an edge level setting to drop the messages if the `buffer.isFull == true`. Even if the UDF or UDSink drops a message due to some internal error in the user-defined code, the processing latency will spike up causing a natural back pressure. A kill switch to drop messages can help alleviate/avoid any repercussions on the rest of the DAG. This setting is an edge-level setting and can be enabled by `onFull` and the default is `retryUntilSuccess` (other option is `discardLatest`). This is a data loss scenario but can be useful in cases where we are doing user-introduced experimentations, like A/B testing, on the pipeline. It is totally okay for the experimentation side of the DAG to have data loss while the production is unaffected. Setting `onFull` to `discardLatest` will drop the message on the floor if the edge is full. ```yaml edges: from: a to: b onFull: discardLatest ``` The default setting for `onFull` in `retryUntilSuccess` which will make sure the message is retried until successful. ```yaml edges: from: a to: b onFull: retryUntilSuccess ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_logout.md

title: kbcli logout Log out of the KubeBlocks Cloud ``` kbcli logout [flags] ``` ``` -h, --help help for logout -r, --region string Specify the region [jp] to log in. (default "jp") ``` ``` --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 ```