cwielenb/CNCF-Dataset huggingface dataset:
Project: Nocalhost (App Definition and Development / Application Definition & Image Build)
File: TROUBLESHOOTING.md

The most common reason for this issue is improper use of struct tags (eg. `yaml` or `json`). Viper uses under the hood for unmarshaling values which uses `mapstructure` tags by default. Please refer to the library's documentation for using other struct tags. Viper installation seems to fail a lot lately with the following (or a similar) error: ``` cannot find package "github.com/hashicorp/hcl/tree/hcl1" in any of: /usr/local/Cellar/go/1.15.7_1/libexec/src/github.com/hashicorp/hcl/tree/hcl1 (from $GOROOT) /Users/user/go/src/github.com/hashicorp/hcl/tree/hcl1 (from $GOPATH) ``` As the error message suggests, Go tries to look up dependencies in `GOPATH` mode (as it's commonly called) from the `GOPATH`. Viper opted to use to manage its dependencies. While in many cases the two methods are interchangeable, once a dependency releases new (major) versions, `GOPATH` mode is no longer able to decide which version to use, so it'll either use one that's already present or pick a version (usually the `master` branch). The solution is easy: switch to using Go Modules. Please refer to the on how to do that. tl;dr* `export GO111MODULE=on`
Project: KICS (Provisioning / Security & Compliance)
File: 3561130e-9c5f-485b-9e16-2764c82763e5.md

title: IAM User Has Too Many Access Keys hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3561130e-9c5f-485b-9e16-2764c82763e5 Query name: IAM User Has Too Many Access Keys Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Any IAM User should not have more than one access key since it increases the risk of unauthorized access and compromise credentials<br> ```tf title="Positive test num. 1 - tf file" hl_lines="2 7" resource "awsiamaccess_key" "positive1" { user = awsiamuser.lb.name pgpkey = "keybase:somepersonthatexists" } resource "awsiamaccess_key" "positive2" { user = awsiamuser.lb.name pgpkey = "keybase:somepersonthatexists" } resource "awsiamuser" "lb" { name = "loadbalancer" path = "/system/" } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "userExample" { name = "loadbalancer" path = "/system/" tags = { tag-key = "tag-value" } } resource "awsiamaccess_key" "negative1" { user = awsiamuser.userExample.name pgpkey = "keybase:somepersonthatexists" } ```
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_onprem_instance-types_describe.md

Describe instance type of a YugabyteDB Anywhere on-premises provider Describe instance types of a YugabyteDB Anywhere on-premises provider ``` yba provider onprem instance-types describe [flags] ``` ``` --instance-type-name string [Required] Instance type name. -h, --help help for describe ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Optional] The name of the provider for the action. Required for create, delete, describe, instance-types and nodes. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage YugabyteDB Anywhere onprem instance types
Project: Chef InSpec (Provisioning / Security & Compliance)
File: rabbitmq_config.md

+++ title = "rabbitmq_config resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "rabbitmq_config" identifier = "inspec/resources/os/rabbitmqconfig.md rabbitmqconfig resource" parent = "inspec/resources/os" +++ Use the `rabbitmq_config` Chef InSpec audit resource to test configuration data for the RabbitMQ daemon located at `/etc/rabbitmq/rabbitmq.config` on Linux and Unix platforms. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.20.0 of InSpec. A `rabbitmq_config` resource block declares the RabbitMQ configuration data to be tested: describe rabbitmqconfig.params('rabbit', 'ssllisteners') do it { should cmp 5671 } end where `params` is the list of parameters configured in the RabbitMQ config file `{ should cmp 5671 }` tests the value of `rabbit.ssl_listeners` as read from `rabbitmq.config` versus the value declared in the test The following examples show how to use this Chef InSpec audit resource. describe rabbitmqconfig.params('rabbit', 'tcplisteners') do it { should eq [5672] } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.8.26.md

RabbitMQ `3.8.26` is a maintenance release. All users are recommended to upgrade to this release. RabbitMQ releases are distributed via , , and . This release and . explains what package repositories and tools can be used to provision modern Erlang versions. See the for general documentation on upgrades and for release notes of other releases. If upgrading from a`3.7.x` release, see upgrade and compatibility notes first. If upgrading from a `3.6.x` or older , first upgrade to and then to this version. Any questions about this release, upgrades or RabbitMQ in general are welcome on the and . Release notes are kept under . Contributors are encouraged to update them together with their changes. This helps with release automation and more consistent release schedule. Signing keys specified in `rabbitmq.conf` were not translated correctly, resulting in exceptions during permission checks. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.8.26.tar.xz` instead of the source tarball produced by GitHub.
Project: YDB (App Definition and Development / Database)
File: max_min_by.md

Return the value of the first argument for the table row where the second argument is minimum/maximum. You can optionally specify the third argument N that affects behavior if the table has multiple rows with the same minimum or maximum value: If N is omitted, the value of one of the rows is returned, and the other rows are discarded. If N is specified, the list is returned with all values, but their number can't exceed N. All values after the number are discarded. When choosing N, we recommend that you don't exceed several hundreds or thousands to avoid issues with the limited memory available on {{ backend_name }} clusters. If your task needs absolutely all values, and their number is measured in dozens of thousands or more, then instead of those aggregate functions better use `JOIN` on the source table with a subquery doing `GROUP BY + MIN/MAX` on the desired columns of this table. {% note warning "Attention" %} If the second argument is always NULL, the aggregation result is NULL. {% endnote %} When you use , a `Tuple` containing a value and a key is passed as the first argument. Examples ```yql SELECT MIN_BY(value, LENGTH(value)), MAX_BY(value, key, 100) FROM my_table; ``` ```yql $minbyfactory = AggregationFactory("MIN_BY"); $maxbyfactory = AggregationFactory("MAX_BY", 100); SELECT AGGREGATEBY(AsTuple(value, LENGTH(value)), $minby_factory), AGGREGATEBY(AsTuple(value, key), $maxby_factory) FROM my_table; ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.7.md

layout: release date: 2022-09-15 tag: v0.6.7 language: en Avoid addition of whitespacing during de-prettification @Revolyssup (#6219) Remove dry-run @MUzairS15 (#6195) Perform deprettification after validation @Revolyssup (#6187) Fix the depreciated commands and pre-requisites to setup local dev env @measutosh (#6184) Feat: Add Component Generation Capability @sudo-NithishKarthik (#6173) [Helm] Restructure Helm Charts @CyrineG (#6212) [mesheryctl] Lifecycle: Remove use of K8s manifest in `system update` @alphaX86 (#6197) Fix failing mesheryctl system context unit tests @nishantwrp (#6189) User Friendly Error msg @harkiratsm (#5661) chore: Updated titles in all pages for consistency @Nikhil-Ladha (#6165) rjsf: expand and collapse object fields templates @Abhishek-kumar09 (#6214) Fixed Spinner Animation Issues @sahilsuman933 (#6213) Fix inconsistency between K8s context switcher and Settings page @MUzairS15 (#6205) Add share option @MUzairS15 (#6128) [Cypress] [WIP] Fix E2E and integration Tests for UI @Chadha93 (#6135) [Extension] Dependency: getApp MUI icon @leecalcote (#6207) Added custom loading Animated Spinner @sahilsuman933 (#6179) [Helm] Restructure Helm Charts @CyrineG (#6212) fixed the link for meshery-architecture svg @vaibhav135 (#6118) [Docs] Implementing opengraph protocol @legendarykamal (#6166) Adding websocket port to list of ports - fix for #6200 @vishnus17 (#6203) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @CyrineG, @MUzairS15, @Nikhil-Ladha, @Revolyssup, @alphaX86, @harkiratsm, @l5io, @leecalcote, @legendarykamal, @measutosh, @nishantwrp, @sahilsuman933, @sudo-NithishKarthik, @vaibhav135, @vishnus17 and @warunicorn19
Project: SPIRE (Provisioning / Key Management)
File: plugin_server_upstreamauthority_awssecret.md

The `awssecret` plugin loads root CA credentials from AWS SecretsManager, using them to generate intermediate signing certificates for the server's signing authority. The intermediate certificates are minted against CSRs generated by the ServerCA plugin. The plugin accepts the following configuration options: | Configuration | Description | |-|-| | region | AWS Region that the AWS Secrets Manager is running in | | certfilearn | ARN of the "upstream" CA certificate that will be used for signing. If more than one certificate is present, they will be added to the chain in order of appearance, where the first certificate will be the one used for signing. | | keyfilearn | ARN of the "upstream" CA key file | | bundlefilearn | ARN of roots to include in the trust bundle. If `certfilearn` contains a self-signed root CA certificate this field can be left unset. Otherwise, `bundlefilearn` must include one or more root CA certificates | | accesskeyid | AWS access key ID | | secretaccesskey | AWS secret access key | | secret_token | AWS secret token | | assumerolearn | ARN of role to assume | Only the region, certfilearn, and keyfilearn must be configured. You optionally configure the remaining fields depending on how you choose to give SPIRE Server access to the ARNs. | If SPIRE Server Accesses the ARNs | then these additional fields are mandatory | |-|-| | by providing an access key id and secret access key | `accesskeyid`, `secretaccesskey` | | by using temporary credentials for an IAM account (NOTE: It is the server user's responsibility to provide a new valid token whenever the server is started) | `accesskeyid`, `secretaccesskey`, `secret_token` | | via an EC2 instance that has an attached role with read access to the ARNs | none | | by configuring the UpstreamAuthority plugin to assume another IAM role that has access to the secrets (NOTE: The IAM user for which the access key id and secret access key must have permissions to assume the other IAM role, or the role attached to the EC2 instance must have this capability. | `accesskeyid`, `secretaccesskey`, `secrettoken`, `assumerole_arn` | Because the plugin fetches the secrets from the AWS secrets manager only at startup, automatic rotation of secrets is not advised. SPIRE Server requires that you employ a distinct Amazon Resource Name (ARN) for the CA certificate and the CA key. For more information on the AWS Secrets Manager, see the documentation. A sample configuration: ```hcl UpstreamAuthority "awssecret" { plugin_data { region = "us-west-2", certfilearn = "cert", keyfilearn = "key", bundlefilearn = "bundle", accesskeyid = "ACCESSKEYID", secretaccesskey = "SECRETACCESSKEY", secrettoken = "SECRETTOKEN" assumerolearn = "role" } } ```
Project: KICS (Provisioning / Security & Compliance)
File: 44d434ca-a9bf-4203-8828-4c81a8d5a598.md

title: RDS Instance TDE Status Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 44d434ca-a9bf-4203-8828-4c81a8d5a598 Query name: RDS Instance TDE Status Disabled Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: tde_status parameter should be Enabled for supported RDS instances<br> ```tf title="Positive test num. 1 - tf file" hl_lines="6" resource "aliclouddbinstance" "default" { engine = "MySQL" engine_version = "5.6" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" tde_status = "Disabled" parameters = [{ name = "innodblargeprefix" value = "ON" },{ name = "connect_timeout" value = "50" }] } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "aliclouddbinstance" "default" { engine = "MySQL" engine_version = "8" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" parameters = [{ name = "innodblargeprefix" value = "ON" },{ name = "connect_timeout" value = "50" }] } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="6" resource "aliclouddbinstance" "default" { engine = "SQLServer" engineversion = "2019std_ha" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" tde_status = "Disabled" parameters = [] } ``` <details><summary>Positive test num. 4 - tf file</summary> ```tf hl_lines="1" resource "aliclouddbinstance" "default" { engine = "SQLServer" engineversion = "2016ent_ha" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" parameters = [] } ``` </details> ```tf title="Negative test num. 1 - tf file" resource "aliclouddbinstance" "default" { engine = "MySQL" engine_version = "5.6" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" tde_status = "Enabled" parameters = [{ name = "innodblargeprefix" value = "ON" },{ name = "connect_timeout" value = "50" }] } ``` ```tf title="Negative test num. 2 - tf file" resource "aliclouddbinstance" "default" { engine = "MySQL" engine_version = "8" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" tde_status = "Enabled" parameters = [{ name = "innodblargeprefix" value = "ON" },{ name = "connect_timeout" value = "50" }] } ``` ```tf title="Negative test num. 3 - tf file" resource "aliclouddbinstance" "default" { engine = "SQLServer" engineversion = "2019std_ha" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" tde_status = "Enabled" parameters = [] } ``` <details><summary>Negative test num. 4 - tf file</summary> ```tf resource "aliclouddbinstance" "default" { engine = "SQLServer" engineversion = "2016ent_ha" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" tde_status = "Enabled" parameters = [] } ``` </details> <details><summary>Negative test num. 5 - tf file</summary> ```tf resource "aliclouddbinstance" "default" { engine = "SQLServer" engineversion = "2012web" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" parameters = [] } ``` </details>
Project: Artifact Hub (App Definition and Development / Application Definition & Image Build)
File: kyverno_policies_repositories.md

Kyverno 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 metadata for one or more packages. Each package version must be on a separate folder, and it's up to you to decide if you want to publish one or multiple versions of your package. The structure of a repository with multiple policies 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 2.0.0 README.md artifacthub-pkg.yml package2 1.0.0 README.md artifacthub-pkg.yml ``` This structure is flexible, and in some cases it can be greatly simplified. Nested directories are also supported. 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 ``` 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. The repository metadata file shown above can be used to setup features like or . This file must be located at `/path/to/packages`. In order to locate the Kyverno policy within a given folder, Artifact Hub assumes the policy is named the same as the folder in which it occurs. For example, a policy YAML file named `require-labels.yaml` is expected to be in a folder named `require-labels`. Once you have added your repository, you are all set up. As you add new versions of your policies packages or even new packages to your git repository, they'll be automatically indexed and listed in Artifact Hub.
Project: CDK for Kubernetes (CDK8s) (Provisioning / Automation & Configuration)
File: ecosystem-interoperability.md

As we know, there are many out there, and you might want to incorporate cdk8s along side other libraries in the same application. !!! example For example, you can use cdk8s to define charts in an AWS CDK application, and . This ability, or interoperability, is based on the , which is the underlying technology on which all CDK libraries are built upon. All CDK libraries participating in the same application, must use the same major version of , which currently has both a `3.x` and a `10.x` major version lines. In order to incorporate `cdk8s` in applications that use either version line, we need to maintain two major versions of `cdk8s`, one for each version of `constructs`. Version `1.x` can be used along side libraries that depend on `constructs` version 3.x. > For example: . Version `2.x` can be used along side libraries that depend on `constructs` version 10.x. > For example: .
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: marktag4.md

=== "Tab1Title" Tab1Contents ==Markymark== === "Tab2Title" Tab2Contents ==Merkymerk== ==Mirkymirk== That should render has a `<mark>...</mark>`. This file allows testing the case where we mix tabs and marks, with some marks nested in the tabs, and the tabs at the very top of the file. Do not change that last part, as it is an important part of the test. ==Morkymork==
Project: kube-hunter (Provisioning / Security & Compliance)
File: KHV003.md

vid: KHV003 title: Azure Metadata Exposure categories: [Information Disclosure] severity: high Microsoft Azure provides an internal HTTP endpoint that exposes information from the cloud platform to workloads running in a VM. The endpoint is accessible to every workload running in the VM. An attacker that is able to execute a pod in the cluster may be able to query the metadata service and discover additional information about the environment. Starting in the 2020.10.15 Azure VHD Release, AKS restricts the pod CIDR access to that internal HTTP endpoint.
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: update-k8s-dependencies.md

To correctly update k8s dependencies we have to first bump all replace directives of `k8s.io/*` in Then (if necessary) delete generated code that potentially references deprecated or eliminated stuff (like the mock client) and, on cascade, fix the files[1] that include these (remember which files are affected because at the end you will have to revert the changes you made to restore them). Delete generated code is not a problem because it will be regenerated. Run `make deps-update` to update dependencies. Run `make && make generate` to regenerate the code. Don't forget to restore the files edited in [1].
Project: Apollo (Provisioning / Automation & Configuration)
File: thank-you.md

<hr /> <img src="en/images/community/ctrip.jpeg" alt="ctrip" style="height: 50px"> The Apollo project was born in Ctrip framework R&D department, and received encouragement and support from various parties during the initial development process. Thanks Ctrip for the contribution to the Apollo community. <hr /> <img src="en/images/community/jetbrains.svg" alt="jetbrains" style="height: 80px; margin-right: 20px"> <img src="en/images/community/intellij-idea.svg" alt="intellij-idea" style="width: 75px" > The Apollo team uses when working on the open source projects. Many thanks to for sponsoring our Open Source projects with a license. <hr /> <img src="en/images/community/docsify.svg" alt="docsify" style="height: 80px"> The Apollo team uses to produce its documentation website. <hr /> <img src="en/images/community/jprofiler.png" alt="jprofiler"> The Apollo team uses to locate performance problems on the open source projects. Many thanks to for sponsoring our Open Source projects with a license. <hr />