cwielenb/CNCF-Dataset huggingface dataset:
Project: SPIRE (Provisioning / Key Management)
File: PULL_REQUEST_TEMPLATE.md

<!-- If this is your first PR, please read our contributor guidelines https://github.com/spiffe/spiffe/blob/master/CONTRIBUTING.md https://github.com/spiffe/spire/blob/main/CONTRIBUTING.md Please remember to include a DCO on every commit (`git commit -s`) https://github.com/apps/dco --> Pull Request check list [ ] Commit conforms to CONTRIBUTING.md? [ ] Proper tests/regressions included? [ ] Documentation updated? Affected functionality <!-- Please provide a description of the affected functionality --> Description of change <!-- Please provide a description of the change --> Which issue this PR fixes <!-- optional. `fixes #<issue number>` format will close an issue when this PR is merged -->
Project: Artifact Hub (App Definition and Development / Application Definition & Image Build)
File: ROADMAP.md

At a high level the roadmap is focused on the following 3 categories: Add support for more Cloud Native artifacts from CNCF projects Improve documentation to consolidate useful information spread across issues, discussions and Slack conversations Continue to improve users' experience to make it easier to find artifacts and explore their content Changes in these categories happen in an agile manner with constant development but without having a long backlog.
Project: Pulsar (App Definition and Development / Streaming & Messaging)
File: pip-293.md

There is a config in ServiceConfiguration called `disableBrokerInterceptors` introduced by , which seems to disable the broker interceptor, but is commented for testing only. Actually, whether to enable the interceptor depends on whether the broker is loaded into the interceptors. kept the same implementation. But has changed the behavior, it uses `disableBrokerInterceptors` to judge whether to enable the interceptor, which caused an NPE issue mentioned in . This `disableBrokerInterceptors` config is very confusing, so we decide to delete it. Delete config `disableBrokerInterceptors`. No backward & forward compatibility issue Mailing List discussion thread: https://lists.apache.org/thread/vqf5qcwv3rh2y1r62gw0dnpn0xznq9p0 Mailing List voting thread: https://lists.apache.org/thread/o11otjlywgd0s8dsv7dg9s8msswdfspp
Project: Artifact Hub (App Definition and Development / Application Definition & Image Build)
File: kubearmor_policies_repositories.md

KubeArmor policies repositories are expected to be hosted in GitHub, GitLab or Bitbucket repos. When adding your repository to Artifact Hub, the url used must follow the following format: `https://github.com/user/repo[/path/to/packages]` `https://gitlab.com/user/repo[/path/to/packages]` `https://bitbucket.org/user/repo[/path/to/packages]` By default the `master` branch is used, but it's possible to specify a different one from the UI. Please NOTE that the repository URL used when adding the repository to Artifact Hub must NOT contain the git hosting platform specific parts, like tree/branch, just the path to your packages like it would show in the filesystem. The path to packages provided can contain one or more packages. Each package version must be on a separate folder. You can have multiple policies in a single package, or create a package for each policy, it's completely up to you. In the same way, you can decide if you want to provide one or multiple versions of your policies packages. The structure of a repository with multiple packages and versions could look something like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 1.0.0 README.md artifacthub-pkg.yml more policy3.yaml policy1.yaml policy2.yaml 2.0.0 README.md artifacthub-pkg.yml policy1.yaml package2 1.0.0 README.md artifacthub-pkg.yml policy1.yaml ``` This structure is flexible, and in some cases where you only have a package and a version it can be greatly simplified. In the case of a single package with a single version available at a time (the publisher doesn't want to make previous ones available, for example), the structure could look like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 README.md artifacthub-pkg.yml policy1.yaml policy2.yaml ``` In the previous case, even the `package1` directory could be omitted. The reason is that both packages names and versions are read from the `artifacthub-pkg.yml` metadata file, so directories names are not used at all. Each package version needs an `artifacthub-pkg.yml` metadata file. Please see the file for more details. Policies files must have the `.yaml` extension. If you want to exclude some paths in your package from the indexing, you can do it using the `ignore` field in your , which uses `.gitignore` syntax. The repository metadata file shown above can be used to setup features like or . This file must be located at `/path/to/packages`. Once you have added your repository, you are all set up. As you add new versions of your policies or even new policies packages to your git repository, they'll be automatically indexed and listed in Artifact Hub.
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_data_drop_postgres.md

title: Kubectl-Dba Data Drop Postgres menu: docs_{{ .version }}: identifier: kubectl-dba-data-drop-postgres name: Kubectl-Dba Data Drop Postgres parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Delete data from postgres database Use this cmd to delete inserted data in a postgres object ``` kubectl-dba data drop postgres [flags] ``` ``` kubectl dba drop pg -n demo sample-postgres ``` ``` -h, --help help for postgres ``` ``` --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/runner/.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 --default-seccomp-profile-type string Default seccomp profile --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 --password string Password for basic authentication to the API server --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 --username string Username for basic authentication to the API server ``` - Drop data from a database
Project: KICS (Provisioning / Security & Compliance)
File: 862fe4bf-3eec-4767-a517-40f378886b88.md

title: Kinesis Not Encrypted With KMS hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 862fe4bf-3eec-4767-a517-40f378886b88 Query name: Kinesis Not Encrypted With KMS Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: AWS Kinesis Streams and metadata should be protected with KMS<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1 34 41" resource "awskinesisstream" "positive1" { name = "terraform-kinesis-test" shard_count = 1 retention_period = 48 shardlevelmetrics = [ "IncomingBytes", "OutgoingBytes", ] tags = { Environment = "test" } } resource "awskinesisstream" "positive2" { name = "terraform-kinesis-test" shard_count = 1 retention_period = 48 shardlevelmetrics = [ "IncomingBytes", "OutgoingBytes", ] tags = { Environment = "test" } encryption_type = "NONE" } resource "awskinesisstream" "positive3" { name = "terraform-kinesis-test" shard_count = 1 retention_period = 48 shardlevelmetrics = [ "IncomingBytes", "OutgoingBytes", ] tags = { Environment = "test" } encryption_type = "KMS" } ``` ```tf title="Negative test num. 1 - tf file" resource "awskinesisstream" "negative1" { name = "terraform-kinesis-test" shard_count = 1 retention_period = 48 shardlevelmetrics = [ "IncomingBytes", "OutgoingBytes", ] tags = { Environment = "test" } encryption_type = "KMS" kmskeyid = "alias/aws/kinesis" } ```
Project: KICS (Provisioning / Security & Compliance)
File: 575a2155-6af1-4026-b1af-d5bc8fe2a904.md

title: IAM Policy Grants Full Permissions hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 575a2155-6af1-4026-b1af-d5bc8fe2a904 Query name: IAM Policy Grants Full Permissions Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: IAM policy should not grant full permissions to resources from the get-go, instead of granting permissions gradually as necessary.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="20" resource "awsiamuser" "positive1" { name = "${local.resource_prefix.value}-user" force_destroy = true tags = { Name = "${local.resource_prefix.value}-user" Environment = local.resource_prefix.value } } resource "awsiamaccess_key" "positive2" { user = awsiamuser.user.name } resource "awsiamuser_policy" "positive3" { name = "excess_policy" user = awsiamuser.user.name policy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Action": [ "*" ], "Effect": "Allow", "Resource": "*" } ] } EOF } output "username" { value = awsiamuser.user.name } output "secret" { value = awsiamaccesskey.user.encryptedsecret } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="3" resource "awsiampolicy" "s3-permission" { name = "s3-permission" policy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Action": [ "*" ], "Effect": "Allow", "Resource": "*" } ] } EOF } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "negative1" { name = "${local.resource_prefix.value}-user" force_destroy = true tags = { Name = "${local.resource_prefix.value}-user" Environment = local.resource_prefix.value } } resource "awsiamaccess_key" "negative2" { user = awsiamuser.user.name } resource "awsiamuser_policy" "negative3" { name = "excess_policy" user = awsiamuser.user.name policy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Action": [ "ec2:*", "s3:*", "lambda:*", "cloudwatch:*" ], "Effect": "Allow", "Resource": "SomeResource" } ] } EOF } output "username" { value = awsiamuser.user.name } output "secret" { value = awsiamaccesskey.user.encryptedsecret } ``` ```tf title="Negative test num. 2 - tf file" resource "awsiampolicy" "s3-permission" { name = "s3-permission" policy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Action": [ "ec2:*", "s3:*", "lambda:*", "cloudwatch:*" ], "Effect": "Allow", "Resource": "SomeResource" } ] } EOF } ``` ```tf title="Negative test num. 3 - tf file" resource "awsiampolicy" "s3-permission" { name = "s3-permission" policy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Action": [ "*" ], "Effect": "Allow", "Resource": "arn:aws:iam::aws:policy/AdministratorAccess" } ] } EOF } ```
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: USERS.md

Please add your company name and initial use case (optional) below. - Streaming ML inference and to prepare data for ML model training in real-time. - Digital Signal Processing Communication Systems. We receive RF energy and use numaflows to transform the RF to individual bits into intelligible data. - Numaflow powers real time notifications, stream processing ecosystem at Atlan. Numaflow is used to extract, transform, and load cryptocurrency blocks and mempool transactions in data lakes, as well as for activity alerts.
Project: Druid (App Definition and Development / Database)
File: kubernetes.md

id: kubernetes title: "kubernetes" <!-- ~ Licensed to the Apache Software Foundation (ASF) under one ~ or more contributor license agreements. See the NOTICE file ~ distributed with this work for additional information ~ regarding copyright ownership. The ASF licenses this file ~ to you 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. --> Apache Druid distribution is also available as image from . For example, you can obtain latest release using the command below. ``` $ docker pull apache/druid ``` can be used to manage a Druid cluster on . Druid clusters deployed on Kubernetes can function without Zookeeper using .
Project: StarRocks (App Definition and Development / Database)
File: degrees.md

displayed_sidebar: "English" Converts the angle in radians `x` to degrees. ```SQL DEGREES(x); ``` `x`: the angle in radians. DOUBLE is supported. Returns a value of the DOUBLE data type. ```Plaintext mysql> select degrees(3.1415926535898); +--+ | degrees(3.1415926535898) | +--+ | 180.0000000000004 | +--+ 1 row in set (0.07 sec) ```
Project: KICS (Provisioning / Security & Compliance)
File: 97cb0688-369a-4d26-b1f7-86c4c91231bc.md

title: ECS Cluster with Container Insights Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 97cb0688-369a-4d26-b1f7-86c4c91231bc Query name: ECS Cluster with Container Insights Disabled Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: ECS Cluster should enable container insights<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsecscluster" "foo" { name = "white-hart" } ``` ```tf title="Negative test num. 1 - tf file" resource "awsecscluster" "foo" { name = "white-hart" setting { name = "containerInsights" value = "enabled" } } ```
Project: FOSSA (Provisioning / Security & Compliance)
File: rpm-container.md

The RedHat Package Manager (rpm). This analysis is only executed when container scanning. Each RPM installation may use one of several backends: BerkeleyDB backend: Find file named `Packages` under `var/lib/rpm`. NDB backend: Find file named `Packages.db` under `/rpm/`. Sqlite backend: Find file named `Packages.sqlite` or `rpmdb.sqlite` under `var/lib/rpm`. Parse and analyze, reporting package name, package version, architecture, and optionally epoch. Each of these backends share a common format for storing actual packages, but the method used to retrieve the list of packages is unique to each backend. Explicitly specify an analysis target in `.fossa.yml` file. The example below excludes all other analysis targets: ```yaml version: 3 targets: only: type: ndb type: berkeleydb type: sqlitedb ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_storage_bucket_iam_policy.md

+++ title = "googlestoragebucketiampolicy resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlestoragebucketiampolicy" identifier = "inspec/resources/gcp/googlestoragebucketiampolicy.md googlestoragebucketiampolicy resource" parent = "inspec/resources/gcp" +++ A `googlestoragebucketiampolicy` is used to test a Google Bucket Iam Policy resource ```ruby describe googlestoragebucketiampolicy(bucket: "bucket") do it { should exist } end googlestoragebucketiampolicy(bucket: "bucket").bindings.each do |binding| describe binding do its('role') { should eq 'roles/editor'} its('members') { should include 'user:testuser@example.com'} end end ``` Properties that can be accessed from the `googlestoragebucketiampolicy` resource: `iambindingroles` : The list of roles that exist on the policy. `bindings` : Associates a list of members to a role. `role` : Role that is assigned to members. For example, roles/viewer, roles/editor, or roles/owner. `members` : Specifies the identities requesting access for a Cloud Platform resource. `audit_configs` : Specifies cloud audit logging configuration for this policy. `service` : Specifies a service that will be enabled for audit logging. For example, `storage.googleapis.com`, `cloudsql.googleapis.com`. `allServices` is a special value that covers all services. `auditlogconfigs` : The configuration for logging of each type of permission. `log_type` : The log type that this config enables. For example, ADMINREAD, DATAWRITE or DATA_READ `exempted_members` : Specifies the identities that do not cause logging for this type of permission. Ensure the is enabled for the current project.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: cogroupbykey.md

title: "CoGroupByKey" <!-- 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. --> {{< localstorage language language-py >}} {{< button-pydoc path="apache_beam.transforms.util" class="CoGroupByKey" >}} Aggregates all input elements by their key and allows downstream processing to consume all values associated with the key. While `GroupByKey` performs this operation over a single input collection and thus a single type of input values, `CoGroupByKey` operates over multiple input collections. As a result, the result for each key is a tuple of the values associated with that key in each input collection. See more information in the . In the following example, we create a pipeline with two `PCollection`s of produce, one with icons and one with durations, both with a common key of the produce name. Then, we apply `CoGroupByKey` to join both `PCollection`s using their keys. `CoGroupByKey` expects a dictionary of named keyed `PCollection`s, and produces elements joined by their keys. The values of each output element are dictionaries where the names correspond to the input dictionary, with lists of all the values found for that key. {{< highlight language="py" py="sdks/python/apache_beam/examples/snippets/transforms/aggregation/cogroupbykey.py" >}} {{< codesample "sdks/python/apachebeam/examples/snippets/transforms/aggregation/cogroupbykey.py" cogroupbykey >}} {{< /highlight >}} {{< paragraph class="notebook-skip" >}} Output: {{< /paragraph >}} {{< highlight class="notebook-skip" >}} {{< codesample "sdks/python/apachebeam/examples/snippets/transforms/aggregation/cogroupbykey_test.py" plants >}} {{< /highlight >}} to combine elements. takes one input collection. {{< button-pydoc path="apache_beam.transforms.util" class="CoGroupByKey" >}}
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.178.md

layout: release date: 2023-11-18 tag: v0.6.178 [Model] Add connection definition for `kubernetes` model @MUzairS15 (#9368) [chore] Bump MeshKit v0.6.85 @theBeginner86 (#9380) Added MAINTAINERS.md @ankushbhardwaj408 (#9365) make isAnnotation update dynamic @MUzairS15 (#9366) [Extensions] Enhance Meshery Docker Extension UI @senali-d (#9377) fix width of connection chip @sudhanshutech (#9386) Reuse connections chip @sudhanshutech (#9382) Color of FavIcon in the footer is changed to keppel green @VivekBaldha0712 (#9039) fixed prettier error @captain-Akshay (#9381) [bug] Fix URL import @theBeginner86 (#9378) Bump the npmandyarn at /ui security update group in /ui with 1 update @dependabot (#9234) Bump the npmandyarn at /ui security update group in /ui with 1 update @dependabot (#9234) [Docs] Update connections.md @leecalcote (#9373) Thank you to our contributors for making this release possible: @senali-d, @MUzairS15, @VivekBaldha0712, @Yashsharma1911, @ankushbhardwaj408, @captain-Akshay, @dependabot, @l5io, @leecalcote, @sudhanshutech, @theBeginner86 and l5io
Project: GreptimeDB (App Definition and Development / Database)
File: v0.4.0.md

| | | | | - | | CPU | AMD Ryzen 7 7735HS (8 core 3.2GHz) | | Memory | 32GB | | Disk | SOLIDIGM SSDPFKNU010TZ | | OS | Ubuntu 22.04.2 LTS | | | | | - | -- | | Machine | ecs.g7.4xlarge | | CPU | 16 core | | Memory | 64GB | | Disk | 100G | | OS | Ubuntu 22.04 | | | | | - | -- | | Machine | ecs.g8y.4xlarge | | CPU | 16 core | | Memory | 64GB | | Disk | 100G | | OS | Ubuntu 22.04 ARM | | Environment | Ingest raterows/s | | | | | Local | 365280.60 | | Aliyun g7.4xlarge | 341368.72 | | Aliyun g8y.4xlarge | 320907.29 | | Query type | Local (ms) | Aliyun g7.4xlarge (ms) | Aliyun g8y.4xlarge (ms) | | | - | - | -- | | cpu-max-all-1 | 50.70 | 31.46 | 47.61 | | cpu-max-all-8 | 262.16 | 129.26 | 152.43 | | double-groupby-1 | 2512.71 | 1408.19 | 1586.10 | | double-groupby-5 | 3896.15 | 2304.29 | 2585.29 | | double-groupby-all | 5404.67 | 3337.61 | 3773.91 | | groupby-orderby-limit | 3786.98 | 2065.72 | 2312.57 | | high-cpu-1 | 71.96 | 37.29 | 54.01 | | high-cpu-all | 9468.75 | 7595.69 | 8467.46 | | lastpoint | 13379.43 | 11253.76 | 12949.40 | | single-groupby-1-1-1 | 20.72 | 12.16 | 13.35 | | single-groupby-1-1-12 | 28.53 | 15.67 | 21.62 | | single-groupby-1-8-1 | 72.23 | 37.90 | 43.52 | | single-groupby-5-1-1 | 26.75 | 15.59 | 17.48 | | single-groupby-5-1-12 | 45.41 | 22.90 | 31.96 | | single-groupby-5-8-1 | 107.96 | 59.76 | 69.58 |
Project: Chef InSpec (Provisioning / Security & Compliance)
File: default_gateway.md

+++ title = "default_gateway resource" draft = false gh_repo = "inspec" platform = "unix" [menu] [menu.inspec] title = "default_gateway" identifier = "inspec/resources/os/defaultgateway.md defaultgateway resource" parent = "inspec/resources/os" +++ Use the default_gateway Chef InSpec audit resource to test the assigned IP address and interface for the default route. This resource is distributed with Chef InSpec. A `default_gateway` Chef InSpec audit resource allows to test the assigned IP address and interface for the default route. ```ruby describe default_gateway do its("ipaddress") { should eq '172.26.0.1' } its("interface") { should eq 'eth0' } end ``` where `'ipaddress' and 'interface'` are properties of this resource `172.26.0.1` is the expected value for `'ipaddress'` `eth0` is the expected value for `'interface'` Properties of the resources: `ipaddress` and `interface`. The `ipaddress` property tests the assigned IP address for the default route. The `interface` property tests the assigned network interface for the default route. The following examples show how to use this Chef InSpec audit resource. `ipaddress` fetches the assigned IP address for the default route and by making an comparison using the `eq` matcher. ```ruby describe default_gateway do its("ipaddress") { should eq '172.26.0.1' } end ``` `interface` fetches the assigned network interface for the default route and by making an comparison using the `eq` matcher. ```ruby describe default_gateway do its("interface") { should eq 'eth0' } end ```