cwielenb/CNCF-Dataset huggingface dataset:
Project: OAuth2 Proxy (Provisioning / Key Management)
File: linkedin.md

id: linkedin title: LinkedIn For LinkedIn, the registration steps are: Create a new project: https://www.linkedin.com/secure/developer In the OAuth User Agreement section: In default scope, select rbasicprofile and remailaddress. In "OAuth 2.0 Redirect URLs", enter `https://internal.yourcompany.com/oauth2/callback` Fill in the remaining required fields and Save. Take note of the Consumer Key / API Key and Consumer Secret / Secret Key
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: feature-request.md

name: Feature Request about: Suggest a feature title: '' labels: '' assignees: '' <!-- A clear and concise description of what the problem is. Example: I have an issue when ... --> <!-- A clear and concise description of what you want to happen. Add any considered drawbacks. --> <!-- If your request relates to a particular operator type, uncomment one or more of the following lines corresponding to the language of that type --> <!-- /language go --> <!-- /language ansible For ansible operator related feature requests, please create the issue in https://github.com/operator-framework/ansible-operator-plugins --> <!-- /language helm -->
Project: StarRocks (App Definition and Development / Database)
File: bitmap_subset_in_range.md

displayed_sidebar: "English" Intercepts elements from a Bitmap value within the range of `startrange` and `endrange` (exclusive). The output elements are a subset of the Bitmap value. This function is mainly used for scenarios such as paginated queries. It is supported from v3.1. ```Haskell BITMAP bitmapsubsetinrange(BITMAP src, BIGINT startrange, BIGINT end_range) ``` `src`: the Bitmap value from which to obtain elements. `start_range`: the start range to intercept elements. It must be a BIGINT value. If the specified start range exceeds the maximum length of the BITMAP value, NULL is returned. See Example 4. `endrange`: the end range to intercept elements. It must be a BIGINT value. If `endrange` equals or is less than `start range`, NULL is returned. See Example 3. Returns a value of the BITMAP type. NULL is returned if any of the input parameters is invalid. The subset elements include `startrange` but exclude `endrange`. See Example 5. In the following examples, the input of bitmapsubsetinrange() is the output of . For example, `bitmapfromstring('1,1,3,1,5,3,5,7,7,9')` returns `1, 3, 5, 7, 9`. bitmapsubsetinrange() takes this BITMAP value as the input. Example 1: Obtain subset elements from the BITMAP value with elements values in the range of 1 to 4. The values within this range are 1 and 3. ```Plaintext select bitmaptostring(bitmapsubsetinrange(bitmapfrom_string('1,1,3,1,5,3,5,7,7,9'), 1, 4)) value; +-+ | value | +-+ | 1,3 | +-+ ``` Example 2: Obtain subset elements from the BITMAP value with elements value in the range 1 to 100. The end value exceeds the maximum length of the BITMAP value and all the matching elements are returned. ```Plaintext select bitmaptostring(bitmapsubsetinrange(bitmapfrom_string('1,1,3,1,5,3,5,7,7,9'), 0, 100)) value; +--+ | value | +--+ | 1,3,5,7,9 | +--+ ``` Example 3: NULL is returned because the end range `3` is less than the start range `4`. ```Plaintext select bitmaptostring(bitmapsubsetinrange(bitmapfrom_string('1,1,3,1,5,3,5,7,7,9'), 4, 3)) value; +-+ | value | +-+ | NULL | +-+ ``` Example 4: The start range 10 exceeds the maximum length (5) of the BITMAP value `1,3,5,7,9`. NULL is returned. ```Plain select bitmaptostring(bitmapsubsetinrange(bitmapfrom_string('1,1,3,1,5,3,5,7,7,9'), 10, 15)) value; +-+ | value | +-+ | NULL | +-+ ``` Example 5: The returned subset includes the start value `1` but excludes the end value `3`. ```plaintext select bitmaptostring(bitmapsubsetinrange(bitmapfrom_string('1,1,3,1,5,4,5,6,7,9'), 1, 3)) value; +-+ | value | +-+ | 1 | +-+ ```
Project: NebulaGraph (App Definition and Development / Database)
File: bug-report.md

name: Bug Report about: I want to report a bug. title: '' labels: type/bug assignees: '' Please check the FAQ documentation before raising an issue <!-- Please check the documentation and old issues before raising an issue in case someone has asked the same question that you are asking. --> Describe the bug (__required__) <!-- A clear and concise description of what the bug is. --> Your Environments (__required__) OS: `uname -a` Compiler: `g++ --version` or `clang++ --version` CPU: `lscpu` Commit id (e.g. `a3ffc7d8`) How To Reproduce(__required__) Steps to reproduce the behavior: Step 1 Step 2 Step 3 Expected behavior <!-- A clear and concise description of what you expected to happen. --> Additional context <!-- Provide logs and configs, or any other context to trace the problem. -->
Project: userver (App Definition and Development / Streaming & Messaging)
File: 404.md

<div style="text-align: center; font-size: 200%; line-height: 1.5;"> Check that you typed the address correctly, go back to your previous page or try using our site search to find something specific. </div> \htmlonly <div style="text-align: center"> <a href="../../d6/d2f/mdenindex.html"> <img src='../../Stiker-5.svg' alt='userver logo annoyed'/> </a> </div> \endhtmlonly
Project: KICS (Provisioning / Security & Compliance)
File: bc1f9009-84a0-490f-ae09-3e0ea6d74ad6.md

title: DOCDB Cluster Not Encrypted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: bc1f9009-84a0-490f-ae09-3e0ea6d74ad6 Query name: DOCDB Cluster Not Encrypted Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: AWS DOCDB Cluster storage should be encrypted<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1 19" resource "awsdocdbcluster" "docdb" { cluster_identifier = "my-docdb-cluster" engine = "docdb" master_username = "foo" master_password = "mustbeeightchars" backupretentionperiod = 5 preferredbackupwindow = "07:00-09:00" skipfinalsnapshot = true } resource "awsdocdbcluster" "docdb_2" { cluster_identifier = "my-docdb-cluster" engine = "docdb" master_username = "foo" master_password = "mustbeeightchars" backupretentionperiod = 5 preferredbackupwindow = "07:00-09:00" skipfinalsnapshot = true storage_encrypted = false } ``` ```tf title="Negative test num. 1 - tf file" resource "awsdocdbcluster" "docdb" { cluster_identifier = "my-docdb-cluster" engine = "docdb" master_username = "foo" master_password = "mustbeeightchars" backupretentionperiod = 5 preferredbackupwindow = "07:00-09:00" skipfinalsnapshot = true storage_encrypted = true } ```
Project: YDB (App Definition and Development / Database)
File: as_container.md

Creates containers of the applicable types. For container literals, is also supported. Specifics: The container elements are passed in arguments. Hence, the number of elements in the resulting container is equal to the number of arguments passed, except when the dictionary keys repeat. `AsTuple` and `AsStruct` can be called without arguments, and also the arguments can have different types. The field names in `AsStruct` are set using `AsStruct(fieldvalue AS fieldname)`. Creating a list requires at least one argument if you need to output the element types. To create an empty list with the given type of elements, use the function . You can create an empty list as an `AsList()` call without arguments. In this case, this expression will have the `EmptyList` type. Creating a dictionary requires at least one argument if you need to output the element types. To create an empty dictionary with the given type of elements, use the function . You can create an empty dictionary as an `AsDict()` call without arguments, in this case, this expression will have the `EmptyDict` type. Creating a set requires at least one argument if you need to output element types. To create an empty set with the given type of elements, use the function . You can create an empty set as an `AsSet()` call without arguments, in this case, this expression will have the `EmptySet` type. `AsList` outputs the common type of elements in the list. A type error is raised in the case of incompatible types. `AsDict` separately outputs the common types for keys and values. A type error is raised in the case of incompatible types. `AsSet` outputs common types for keys. A type error is raised in the case of incompatible types. `AsListStrict`, `AsDictStrict`, `AsSetStrict` require the same type for their arguments. `AsDict` and `AsDictStrict` expect `Tuple` of two elements as arguments (key and value, respectively). If the keys repeat, only the value for the first key remains in the dictionary. `AsSet` and `AsSetStrict` expect keys as arguments. Examples ```yql SELECT AsTuple(1, 2, "3") AS `tuple`, AsStruct( 1 AS a, 2 AS b, "3" AS c ) AS `struct`, AsList(1, 2, 3) AS `list`, AsDict( AsTuple("a", 1), AsTuple("b", 2), AsTuple("c", 3) ) AS `dict`, AsSet(1, 2, 3) AS `set` ```
Project: Carvel (App Definition and Development / Application Definition & Image Build)
File: README_CodeCommit.md

The following is a sample Lambda function that receives Amazon CodeCommit event records input and prints them to `os.Stdout`.) ```go import ( "fmt" "github.com/aws/aws-lambda-go/events" ) func handleRequest(evt events.CodeCommitEvent) { for _, record := range evt.Records { fmt.Println(record) } } ```
Project: ArangoDB (App Definition and Development / Database)
File: assume_value_lvalue_const.md

+++ title = "`const valuetype &assumevalue() const & noexcept`" description = "Narrow contract const lvalue reference observer of any value present. Constexpr propagating, never throws." categories = ["observers"] weight = 610 +++ Narrow contract const lvalue reference observer of any value present. `NoValuePolicy::narrowvaluecheck()` is first invoked, then the reference to the value is returned. The convention is that hard undefined behaviour occurs if no value is actually present, however `NoValuePolicy::narrowvaluecheck()` can do something to avoid that. Note that if `value_type` is `void`, only a `const` overload returning `void` is present. Requires: Always available. Complexity: Depends on `NoValuePolicy::narrowvaluecheck()`. Guarantees: An exception is never thrown.
Project: StackRox (Provisioning / Security & Compliance)
File: diff_output.md

| diff-type | source | destination | dir1 | dir2 | workloads-diff-info | |--|--|-|||| | added | payments/gateway[Deployment] | payments/visa-processor-v2[Deployment] | No Connections | TCP 8080 | workload payments/visa-processor-v2[Deployment] added | | added | {ingress-controller} | frontend/blog[Deployment] | No Connections | TCP 8080 | workload frontend/blog[Deployment] added | | added | {ingress-controller} | zeroday/zeroday[Deployment] | No Connections | TCP 8080 | workload zeroday/zeroday[Deployment] added |
Project: Curiefense (Provisioning / Security & Compliance)
File: UPDATING-CHARTS.md

The charts in the `manifests` directory are used in istioctl to generate an installation manifest. The configuration settings contained in values.yaml files and passed through the CLI are validated against a . Whenever making changes in the charts, it's important to follow the below steps. Is this a new parameter being added? If not, go to the next step. Dynamic, runtime config that is used to configure Istio components should go into the . Values.yaml is being deprecated and adding to it is discouraged. MeshConfig is the official API which follows API management practices and is dynamic (does not require component restarts). Exceptions to this rule are configuration items that affect K8s level settings (resources, mounts etc.) The values.yaml in `manifests` are only used for direct Helm based installations, which is being deprecated. If any values.yaml changes are being made, the same changes must be made in the `manifests/profiles/default.yaml` file, which must be in sync with the Helm values in `manifests`. Istioctl uses a to validate the values. Any changes to the schema must be added here, otherwise istioctl users will see errors. Once the schema file is updated, run: ```bash $ make operator-proto ``` This will regenerate the Go structs used for schema validation. Tests of istioctl use the auto-generated manifests to ensure that the istioctl binary has the correct version of the charts. These manifests can be found in . To regenerate the manifests, run: ```bash $ make gen ``` The new charts/values will likely produce different installation manifests. Unit tests that expect a certain command output will fail for this reason. To update the golden output files, run: ```bash $ make refresh-goldens ``` This will generate git diffs in the golden output files. Check that the changes are what you expect. Your PR should pass all the checks if you followed these steps.
Project: YDB (App Definition and Development / Database)
File: intro-exp.md

The main section of the query plan, `tables`, contains information about querying tables. Reads are described in the `reads` section and writes in the `writes` section. The key characteristic of any table query is its type. Types of reads: `FullScan`: Full table scan. All entries on all shards are read. `Scan`: A read of a certain range of entries. `Lookup`: A read by key or key prefix. `MultiLookup`: Multiple reads by key or key prefix. Supported, for example, in JOINs. Types of writes: `Upsert`: Add a single entry. `MultiUpsert`: Add multiple entries. `Erase`: A single delete by key. `MultiErase`: Multiple deletes. Let's take the query plan from the example above. The `lookup_by` parameter shows what columns (key or key prefix) reads are made by. The `scan_by` parameter shows what columns a read of all entries in a certain range of values is made by. The `columns` parameter lists the columns whose values will be read from the table.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.17.md

RabbitMQ `3.9.17` 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 Erlang 24. has more details on Erlang version requirements for RabbitMQ. Release notes can be found on GitHub at . With a lot of busy quorum queues, nodes hosting a moderate number of of leader replicas could experience growing memory footprint of one of the Raft implementation processes. GitHub issue: Re-introduced key file log rotation settings. Some settings were left behind during the migration to the standard runtime logger starting with 3.9.0. Now some key settings have been re-introduced. Contributed by Alex @illotum Valiushko (AWS). GitHub issue: Cleaned up some compiler options that are no longer relevant. Contributed by Pter @gomoripeti Gmri (CloudAMQP). GitHub issue: Nodes now make sure that status table exists after node boot as long as the feature flag is enabled. GitHub issue: "In flight" messages directed to an exchange that has just been deleted will be silently dropped or instead of causing an exception. GitHub issue: `ra` upgraded from `credentials_obfuscation` was upgraded To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.17.tar.xz` instead of the source tarball produced by GitHub.
Project: Pinniped (Provisioning / Key Management)
File: install-cli.md

title: Install the Pinniped command-line tool description: Download and set up the `pinniped` command-line tool on macOS, Linux, or Windows clients. cascade: layout: docs menu: docs: name: Install CLI weight: 10 parent: howtos The `pinniped` command-line tool is used to generate Pinniped-compatible kubeconfig files, and is also an important part of the Pinniped-based login flow. It must be installed by administrators setting up a Pinniped cluster as well as by users accessing a Pinniped-enabled cluster. Use to install from the Pinniped : `brew install vmware-tanzu/pinniped/pinniped-cli` Find the appropriate binary for your platform from the : {{< buttonlink filename="pinniped-cli-darwin-amd64" >}}Download {{< latestversion >}} for macOS/amd64{{< buttonicon "download.png" >}}{{< /buttonlink >}} {{< buttonlink filename="pinniped-cli-darwin-arm64" >}}Download {{< latestversion >}} for macOS/arm64{{< buttonicon "download.png" >}}{{< /buttonlink >}} {{< buttonlink filename="pinniped-cli-linux-amd64" >}}Download {{< latestversion >}} for Linux/amd64{{< buttonicon "download.png" >}}{{< /buttonlink >}} {{< buttonlink filename="pinniped-cli-linux-arm64" >}}Download {{< latestversion >}} for Linux/arm64{{< buttonicon "download.png" >}}{{< /buttonlink >}} {{< buttonlink filename="pinniped-cli-windows-amd64.exe" >}}Download {{< latestversion >}} for Windows/amd64{{< buttonicon "download.png" >}}{{< /buttonlink >}} {{< buttonlink filename="pinniped-cli-windows-arm64.exe" >}}Download {{< latestversion >}} for Windows/arm64{{< buttonicon "download.png" >}}{{< /buttonlink >}} You should put the command-line tool somewhere on your `$PATH`, such as `/usr/local/bin` on macOS/Linux. You'll also need to mark the file as executable, e.g. `chmod +x pinniped` on macOS/Linux. To find specific versions or view all available platforms and architectures, visit the . If you are using macOS, you may get an error dialog when you first run `pinniped` that says `pinniped cannot be opened because the developer cannot be verified`. Cancel this dialog, open System Preferences, click Security & Privacy, and click the Allow Anyway button next to the Pinniped message. Run the command again and another dialog appears saying `macOS cannot verify the developer of pinniped. Are you sure you want to open it?`. Click Open to allow the command to proceed. Choose your preferred and use it to replace the version number in the URL below. For example, to install {{< latestversion >}} on Linux/amd64: ```sh curl -Lso pinniped https://get.pinniped.dev/{{< latestversion >}}/pinniped-cli-linux-amd64 \ && chmod +x pinniped \ && sudo mv pinniped /usr/local/bin/pinniped ``` Next, and/or !
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: Slack.md

Slack sink connector Spark<br/> Flink<br/> SeaTunnel Zeta<br/> Used to send data to Slack Channel. Both support streaming and batch mode. For example, if the data from upstream is [`age: 12, name: huan`], the content send to socket server is the following: `{"name":"huan","age":17}` All data types are mapped to string. | Name | Type | Required | Default | Description | |-|--|-||--| | webhooks_url | String | Yes | - | Slack webhook url | | oauth_token | String | Yes | - | Slack oauth token used for the actual authentication | | slack_channel | String | Yes | - | slack channel for data write | | common-options | | no | - | Sink plugin common parameters, please refer to for details | ```hocon sink { SlackSink { webhooks_url = "https://hooks.slack.com/services/xxxxxxxxxxxx/xxxxxxxxxxxx/xxxxxxxxxxxxxxxx" oauth_token = "xoxp-xxxxxxxxxx-xxxxxxxx-xxxxxxxxx-xxxxxxxxxxx" slack_channel = "channel name" } } ``` Add Slack Sink Connector
Project: KICS (Provisioning / Security & Compliance)
File: 0401f71b-9c1e-4821-ab15-a955caa621be.md

title: Pod Misconfigured Network Policy hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 0401f71b-9c1e-4821-ab15-a955caa621be Query name: Pod Misconfigured Network Policy Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: Check if any pod is not being targeted by a proper network policy.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" apiVersion: v1 kind: Pod metadata: name: positive1-pod namespace: positive1-one labels: app: shouldmatch spec: containers: name: nginx image: nginx:1.14.2 ports: containerPort: 80 apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: positive1-netpol labels: policy: no-ingress-no-egress namespace: positive1-anotherone spec: podSelector: matchLabels: app: shouldmatch policyTypes: [] ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="4" apiVersion: v1 kind: Pod metadata: name: positive2-pod namespace: positive2 spec: containers: name: nginx image: nginx:1.14.2 ports: containerPort: 80 apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: positive2-netpol namespace: positive2 spec: podSelector: {} policyTypes: [] ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: negative1-pod namespace: negative1 spec: securityContext: runAsUser: 1000 containers: name: app image: images.my-company.example/app:v4 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: negative1-policy namespace: negative1 spec: podSelector: {} policyTypes: Ingress Egress ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: v1 kind: Pod metadata: name: negative2-pod namespace: negative2-namespace labels: app: negative2-app spec: securityContext: runAsUser: 1000 containers: name: app image: images.my-company.example/app:v4 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: negative2-policy namespace: negative2-othernamespace spec: podSelector: matchLabels: app: negative2-app policyTypes: Ingress egress: to: ipBlock: cidr: 10.0.0.0/24 ports: protocol: TCP port: 5978 ``` ```yaml title="Negative test num. 3 - yaml file" apiVersion: v1 kind: Pod metadata: name: negative3-pod namespace: negative3 spec: containers: name: nginx image: nginx:1.14.2 ports: containerPort: 80 apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: negative3-netpol labels: policy: just-egress namespace: negative3 spec: podSelector: {} egress: to: ipBlock: cidr: 10.0.0.0/24 ports: protocol: TCP port: 5978 ```
Project: Dgraph (App Definition and Development / Database)
File: PULL_REQUEST_TEMPLATE.md

Title format: `Topic(Area): Feature` `Topic` must be one of `build|ci|docs|feat|fix|perf|refactor|chore|test` `Area` must be one of `acl|audit|backup|badger|cdc|dql|export|graphql|indexing|multi-tenancy|raft|restore|upgrade|zero` * Add [BREAKING] if it is a breaking change Body Format: Description: <add description> Fixes: <GitHub Issue> Closes: <JIRA Issue> Docs: <docs PR>
Project: ko (App Definition and Development / Application Definition & Image Build)
File: index.md

ko_meta: true `ko` makes building Go container images easy, fast, and secure by default. `ko` is a simple, fast container image builder for Go applications. It's ideal for use cases where your image contains a single Go application without many dependencies on the OS base image (e.g., no cgo, no OS package dependencies). `ko` builds images by executing `go build` on your local machine, and as such doesn't require `docker` to be installed. This can make it a good fit for lightweight CI/CD use cases. `ko` makes easy, produces by default, and includes support for simple YAML templating which makes it a powerful tool for . and ! `ko` is used and loved by these open source projects: `ko` is a Cloud Native Computing Foundation Sandbox project. <a href="https://cncf.io"><img width=300 src="./images/cncf.svg" alt="CNCF logo" /></a>
Project: StarRocks (App Definition and Development / Database)
File: SHOW_CREATE_DATABASE.md

displayed_sidebar: "English" Shows the SQL command used to create a database. ```sql SHOW CREATE DATABASE <db_name> ``` `db_name`: the database name, required. `Database`: the database name `Create Database`: the SQL command used to create the database ```sql mysql > show create database zj_test; +-++ | Database | Create Database | +-++ | zjtest | CREATE DATABASE `zjtest` | +-++ ```