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

RabbitMQ `3.7.7` a maintenance release. This release introduces compatibility with . This release has no known incompatibilities with earlier `3.7.x` releases. When upgrading to this release and upgrading Erlang to 21.0 at the same time, extra care has to be taken. Since CLI tools from any earlier RabbitMQ release will fail on Erlang 21, RabbitMQ must be upgraded before Erlang. See upgrade and compatibility notes if upgrading from an earlier release. See the for general documentation on upgrades and for release notes of other releases. This release is compatible with , the newest major Erlang runtime release. GitHub issue: Windows installer will now take default location differences between Erlang versions into account. GitHub issue: It is now possible to configure Web browser session timeout. Default is still 8 hours. GitHub issue: Direct connections downstream were not closed in some cases. Contributed by Ricardo Gonalves. GitHub issue: It wasn't possible to set `authldap.dnlookup_bind` to the value of `anon` in the new style config format. GitHub issue: The following combination of settings was rejected by the plugin, even though they are reasonable and were recommended by the docs: ``` ini clusterformation.consul.svcaddr_auto = true clusterformation.consul.svcaddr_nic = en0 ``` GitHub issue: Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-3.7.7.tar.gz`.
Project: Kyverno (Provisioning / Security & Compliance)
File: kyverno_oci_pull.md

Pulls policie(s) that are included in an OCI image from OCI registry and saves them to a local directory. Pulls policie(s) that are included in an OCI image from OCI registry and saves them to a local directory. NOTE: This is an experimental command, use `KYVERNO_EXPERIMENTAL=true` to enable it. For more information visit https://kyverno.io/docs/kyverno-cli/#pulling ``` kyverno oci pull [dir] [flags] ``` ``` kyverno oci pull . -i <imgref> ``` ``` -h, --help help for pull -i, --image string image reference to push to or pull from ``` ``` --adddirheader If true, adds the file directory to the header of the log messages --alsologtostderr log to standard error as well as files (no effect when -logtostderr=true) --logbacktraceat traceLocation when logging hits line file:N, emit a stack trace (default :0) --log_dir string If non-empty, write log files in this directory (no effect when -logtostderr=true) --log_file string If non-empty, use this log file (no effect when -logtostderr=true) --logfilemax_size uint Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800) --logtostderr log to standard error instead of files (default true) --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true) --skip_headers If true, avoid header prefixes in the log messages --skiplogheaders If true, avoid headers when opening log files (no effect when -logtostderr=true) --stderrthreshold severity logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2) -v, --v Level number for the log level verbosity --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging ``` - Pulls/pushes images that include policie(s) from/to OCI registries.
Project: LinuxKit (Provisioning / Automation & Configuration)
File: image-cache.md

linuxkit builds each runtime OS image from a combination of Docker images. These images are pulled from a registry and cached locally. linuxkit does not use the docker image cache to store these images. This is for two key reasons. First, docker does not provide support for different architecture versions. For example, if you want to pull down `docker.io/library/alpine:3.13` by manifest, with its signature, but get the `arm64` version while you are on an `amd64` device, it is not supported. Second, and more importantly, this requires a running docker daemon. Since the very essence of linuxkit is removing daemons and operating systems where unnecessary, just laying down bits in a file, removing docker from the image build process is valuable. It also simplifies many use cases, like CI, where a docker daemon may be unavailable. LinuxKit pulls images down from a registry and stores them in a local cache. It stores the root manifest or index of the image, the manifest, and all of the layers for the requested architecture. It does not pull down layers, manifest or config for all available architectures, only the requested one. If none is requested, it defaults to the architecture on which you are running. By default, LinuxKit caches images in `~/.linuxkit/cache/`. It can be changed via a command-line option. The structure of the cache directory matches the . Image names are kept in `index.json` in the `org.opencontainers.image.ref.name`. For example" ```json { "schemaVersion": 2, "manifests": [ { "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json", "size": 1638, "digest": "sha256:9a839e63dad54c3a6d1834e29692c8492d93f90c59c978c1ed79109ea4fb9a54", "annotations": { "org.opencontainers.image.ref.name": "docker.io/library/alpine:3.13" } } ] } ``` For each image that linuxkit needs to read, it does the following. Note that if the `--pull` option is provided, it always will pull, independent of what is in the cache. Check in the cache for the image name in the cache `index.json`. If it does not find it, pull it down and store it in cache. Read the root hash from `index.json`. Find the root blob in the `blobs/` directory via the hash and read it. Proceed to read the manifest, config and layers. The read process is smart enough to check each blob in the local cache before downloading it from a registry.
Project: Clair (Provisioning / Security & Compliance)
File: CONTRIBUTING.md

Clair is and accepts contributions via GitHub pull requests. This document outlines some of the conventions on development workflow, commit message formatting, contact points and other resources to make it easier to get your contribution accepted. By contributing to this project you agree to the Developer Certificate of Origin . This document was created by the Linux Kernel community and is a simple statement that you, as a contributor, have the legal right to make the contribution. See the file for details. The project currently uses a mailing list and IRC channel: Email: IRC: # IRC channel on freenode.org Please avoid emailing maintainers directly. They are very busy and read the mailing lists. Fork the repository on GitHub Read the for build and test instructions Play with the project, submit bugs, submit patches! This is a rough outline of what a contributor's workflow looks like: Create a topic branch from where you want to base your work (usually main). Make commits of logical units. Make sure your commit messages are in the proper format (see below). Push your changes to a topic branch in your fork of the repository. Make sure the tests pass, and add any new tests as appropriate. Submit a pull request to the original repository. Thanks for your contributions! We follow a rough convention for commit messages that is designed to answer two questions: what changed and why. The subject line should feature the what and the body of the commit should describe the why. ``` scripts: add the test-cluster command this uses tmux to setup a test cluster that you can easily kill and start for debugging. Fixes #38 ``` The format can be described more formally as follows: ``` <subsystem>: <what changed> <BLANK LINE> <why this change was made> <BLANK LINE> <footer> ``` The first line is the subject and should be no longer than 70 characters, the second line is always blank, and other lines should be wrapped at 80 characters. This allows the message to be easier to read on GitHub as well as in various git tools.
Project: KICS (Provisioning / Security & Compliance)
File: 940ddce2-26bd-4e31-a9b4-382714f73231.md

title: Nifcloud RDB Undefined Description To DB Security Group hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 940ddce2-26bd-4e31-a9b4-382714f73231 Query name: Nifcloud RDB Undefined Description To DB Security Group Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: Missing description for db security group<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "nifclouddbsecurity_group" "positive" { group_name = "example" availability_zone = "east-11" } ``` ```tf title="Negative test num. 1 - tf file" resource "nifclouddbsecurity_group" "negative" { group_name = "example" availability_zone = "east-11" description = "Allow from app traffic" } ```
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: sup_log_keys.md

+++ title = "Supervisor Log Codes" description = "Supervisor log code key reference" gh_repo = "habitat" [menu] [menu.habitat] title = "Supervisor Log Codes" identifier = "habitat/reference/sup-log-key" parent = "habitat/reference" +++ When running services with the Chef Habitat Supervisor you'll see log output similar to this: ```output redis.default(SR): Initializing redis.default(SV): Starting redis.default(O): ``` The letters in parentheses are called "log keys" and signify what type of log message is being shown. This can be useful for log filtering. They are mostly organized by the part of the Chef Habitat Supervisor code base that they are running from, so they often are of value to somebody troubleshooting problems in the Chef Habitat Supervisor source code. The meanings of the keys are as follows: | Key | Description | |--|-| | CE | Census | | CFG | Global configuration | | CS | Create service: When a service is being started | | ER | Errors | | FW | Generic file watcher | | HG | Messages from the HTTP gateway | | MN | Main | | MR | Manager | | O | Standard output | | PH | Package hooks | | PK | Package | | PT | Path | | PW | Peer file watcher | | SC | Service configuration | | SH | Starting a shell with `hab sup sh` | | SI | Unix signals | | SOT | Structured output | | SR | Service runtime | | SU | Service updater | | SV | Supervisor | | SY | "sys" utility | | UCW | User-config watcher | | UR | Users utility | | UT | Utilities |
Project: KICS (Provisioning / Security & Compliance)
File: db0ec4c4-852c-46a2-b4f3-7ec13cdb12a8.md

title: CloudWatch Logs Destination With Vulnerable Policy hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: db0ec4c4-852c-46a2-b4f3-7ec13cdb12a8 Query name: CloudWatch Logs Destination With Vulnerable Policy Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Access Control URL: CloudWatch Logs destination policy should avoid wildcard in 'principals' and 'actions'<br> ```tf title="Positive test num. 1 - tf file" hl_lines="22" data "awsiampolicydocument" "testdestination_policy" { statement { effect = "Allow" principals { type = "AWS" identifiers = [ data.awscalleridentity.current.id, ] } actions = [ "logs:*", ] } } resource "awscloudwatchlogdestinationpolicy" "testdestinationpolicy" { destinationname = awscloudwatchlogdestination.test_destination.name accesspolicy = data.awsiampolicydocument.testdestinationpolicy.json } ``` ```tf title="Negative test num. 1 - tf file" data "awsiampolicydocument" "testdestination_policy2" { statement { effect = "Allow" principals { type = "AWS" identifiers = [ "123456789012", ] } actions = [ "logs:PutSubscriptionFilter", ] resources = [ awscloudwatchlogdestination.testdestination.arn, ] } } resource "awscloudwatchlogdestinationpolicy" "testdestinationpolicy2" { destinationname = awscloudwatchlogdestination.test_destination.name accesspolicy = data.awsiampolicydocument.testdestinationpolicy2.json } ```
Project: YDB (App Definition and Development / Database)
File: auth-sa-file.md

```typescript import { Driver, getSACredentialsFromJson, IamAuthService } from 'ydb-sdk'; export async function connect(endpoint: string, database: string, serviceAccountFilename: string) { const saCredentials = getSACredentialsFromJson(serviceAccountFilename); const authService = new IamAuthService(saCredentials); const driver = new Driver({endpoint, database, authService}); const timeout = 10000; if (!await driver.ready(timeout)) { console.log(`Driver has not become ready in ${timeout}ms!`); process.exit(1); } console.log('Driver connected') return driver } ```
Project: YugabyteDB (App Definition and Development / Database)
File: flushdb.md

title: FLUSHDB linkTitle: FLUSHDB description: FLUSHDB menu: preview: parent: api-yedis weight: 2065 aliases: /preview/api/redis/flushdb /preview/api/yedis/flushdb type: docs `FLUSHDB` This command deletes all keys from a database. This functionality can be disabled by setting the yb-tserver `--yedisenableflush` flag to `false`. Returns status string. ```sh $ SET yuga1 "America" ``` ``` "OK" ``` ```sh $ SET yuga2 "Africa" ``` ``` "OK" ``` ```sh $ GET yuga1 ``` ``` "America" ``` ```sh $ GET yuga2 ``` ``` "Africa" ``` ```sh $ FLUSHDB ``` ``` "OK" ``` ```sh $ GET yuga1 ``` ``` (null) ``` ```sh $ GET yuga2 ``` ``` (null) ``` , ,
Project: StarRocks (App Definition and Development / Database)
File: corr.md

displayed_sidebar: "English" Returns the Pearson correlation coefficient between two expressions. This function is supported from v2.5.10. It can also be used as a window function. ```Haskell CORR(expr1, expr2) ``` `expr1` and `expr2` must evaluate to TINYINT, SMALLINT, INT, BIGINT, LARGEINT, FLOAT, DOUBLE, or DECIMAL. If `expr1` and `expr2` are table columns, this function calculates the correlation coefficient of these two columns. Returns a DOUBLE value. The formula is as follows, where `n` represents the row count of the table: <!--$$ \frac{\sum{i=1}^{n}((xi - \bar{x})(yi - \bar{y}))}{\sqrt{\sum{i=1}^{n}((xi - \bar{x})^2) \cdot \sum{i=1}^{n}((y_i - \bar{y})^2)}} $$--> A data row is counted only when the two columns in this row are non-null values. Otherwise, this data row is eliminated from the result. 0 is returned if `n` is 1. NULL is returned in any input is NULL. Suppose table `agg` has the following data: ```plaintext mysql> select * from agg; ++-+-+ | no | k | v | ++-+-+ | 1 | 10.00 | NULL | | 2 | 10.00 | 11.00 | | 2 | 20.00 | 22.00 | | 2 | 25.00 | NULL | | 2 | 30.00 | 35.00 | ++-+-+ ``` Calculate the correlation coefficient of the `k` and `v` columns: ```plaintext mysql> select no,CORR(k,v) from agg group by no; ++--+ | no | corr(k, v) | ++--+ | 1 | NULL | | 2 | 0.9988445981121532 | ++--+ ```
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: cli-overview.md

id: cli-overview title: Overview description: Overview of the Backstage CLI A goal of Backstage is to provide a delightful developer experience in and around the project. Creating new and should be simple, iteration speed should be fast, and the overhead of maintaining custom tooling should be minimal. As a part of accomplishing this goal, Backstage provides its own build system and tooling, delivered primarily through the . When creating an app using , you receive a project that's already prepared with a typical setup and package scripts for executing the most common commands. Under the hood the CLI uses for bundling, for building packages, for testing, and for linting. It also includes tooling for working within Backstage apps, for example for keeping the app up to date and verifying static configuration. For a more in-depth look into the tooling, see the page, and for a list of commands, see the page. While the Backstage tooling is opinionated in how it works, it is also possible to use your own tooling either partially or fully. For example, the CLI provides a command for building a plugin package for publishing, but the output is a quite standard combination of transpiled JavaScript and TypeScript type declarations. The usage of the command from the CLI can therefore be augmented or replaced with other tools if necessary. The Backstage CLI intentionally does not provide many hooks for overriding or customizing the build process. This is to allow for evolution of the CLI without having to take a wide API surface into account. This allows us to iterate and improve the tooling, as well as to more easily keep the system up to date.
Project: kpt (Provisioning / Automation & Configuration)
File: TEMPLATE.md

title: "`cmd`" linkTitle: "cmd" type: docs description: > One line description of the command <!--mdtogo:Short One line description of the command --> Short description of the command. The command should be referred to verbatim and not be capitalized, for example `get`, `update`, `fn`. The documentation for each command should be focused and concise. Any fundamental concepts or concerns cutting across many command should be covered in the kpt book and the reference docs should provide deep links to the relevant content. Args, flags, and env vars should be listed in alphabetical order. <!--mdtogo:Long--> ``` kpt <cmd group> <cmd> <ARGS> [flags] ``` ``` EXAMPLE_ARG: Description of the arg. This should include information about whether the ARG is required and if it is not, what would be the default value. It should use correct grammar, including capitalization and punctuation. ``` ``` --example-flag: Description of the flag, including the default value. It should use correct grammar, including capitalization and punctuation. ``` ``` EXAMPLEENVVAR: Description of the env variable. It should use correct grammar, including capitalization and punctuation. ``` <!--mdtogo--> <!--mdtogo:Examples--> ```shell kpt <cmd group> <cmd> ... ``` <!--mdtogo-->
Project: StarRocks (App Definition and Development / Database)
File: cos.md

displayed_sidebar: "English" Computes the cosine of the argument. ```Haskell DOUBLE cos(DOUBLE arg) ``` `arg`: You can specify only a numeric value. This function converts the numeric value into a DOUBLE value before it computes the cosine of the value. Returns a value of the DOUBLE data type. If you specify a non-numeric value, this function returns `NULL`. ```Plain mysql> select cos(-1); +--+ | cos(-1) | +--+ | 0.5403023058681398 | +--+ mysql> select cos(0); +--+ | cos(0) | +--+ | 1 | +--+ mysql> select cos(1); +--+ | cos(1) | +--+ | 0.5403023058681398 | +--+ mysql> select cos(""); ++ | cos('') | ++ | NULL | ++ ``` COS
Project: Beam (App Definition and Development / Streaming & Messaging)
File: nest.md

title: "Nest" icon: /images/logos/powered-by/nest.png hasLink: "https://nest.com/" <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_backup_describe.md

title: kbcli backup describe Describe a backup ``` kbcli backup describe [flags] ``` ``` kbcli backup describe mybackup ``` ``` -h, --help help for describe ``` ``` --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 ``` - Backup command.
Project: Meshery (Provisioning / Automation & Configuration)
File: PULL_REQUEST_TEMPLATE.md

Notes for Reviewers This PR fixes # [ ] Yes, I signed my commits. <!-- Thank you for contributing to Meshery! Contributing Conventions: Include descriptive PR titles with [<component-name>] prepended. Build and test your changes before submitting a PR. Sign your commits By following the community's contribution conventions upfront, the review process will be accelerated and your PR merged more quickly. -->
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: rabbitmq-overview-10991.md

An alternative to RabbitMQ Management Overview RabbitMQ Understand the state of any RabbitMQ cluster at a glance. Includes all metrics displayed on RabbitMQ Management Overview page. This dashboard includes detailed explanation for all metrics displayed, with links to relevant official docs and guides. All metrics are node-specific making it trivial to visualise cluster imbalances (a.k.a. cluster hotspots). Some graph panels include sensible default thresholds. Metrics displayed: Node identity, including RabbitMQ & Erlang/OTP version Node memory & disk available before publishers blocked (alarm triggers) Node file descriptors & TCP sockets available Ready & pending messages Incoming message rates: published / routed to queues / confirmed / unconfirmed / returned / dropped Outgoing message rated: delivered with auto or manual acks / acknowledged / redelivered Polling operation with auto or manual acks, as well as empty ops Queues, including declaration & deletion rates Channels, including open & close rates Connections, including open & close rates Filter by: RabbitMQ Cluster Requires `rabbitmq-prometheus` to be enabled, a built-in plugin since Learn more about To get it working locally with RabbitMQ in 3 simple steps, follow this