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

RabbitMQ `3.10.10` is a maintenance release in the `3.10.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.10.0. This release requires Erlang 24.2 and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang 23 support has reached its . This release of RabbitMQ requires Erlang 24.2 or later versions. Nodes will fail to start on older Erlang releases. Erlang 25 is recommended: it offers much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation. Release notes can be found on GitHub at . Partially reverts an unsafe inter-node communication that could affect classic mirrored queue operation ordering. Kudos to @bording for providing an automated way to reproduce the issue. GitHub issue: Classic mirrored queue leader replica issued to much credit to follower replicas, resulting in an uneven load and memory footprint between them. GitHub issue: Intra-cluster communication link metric collector could run into an exception when peer connection has just been re-established, e.g. after a peer node restart. GitHub issue: When a node was , it closed all MQTT client connections cluster-wide instead of just local client connections. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.10.10.tar.xz` instead of the source tarball produced by GitHub.
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: ref-objects.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: ref-objects-example namespace: examples spec: components: name: image-pull-secrets type: ref-objects properties: objects: resource: secret name: image-credential-to-copy policies: name: topology-hangzhou-clusters type: topology properties: clusterLabelSelector: region: hangzhou ``` You can refer to the about ref-objects.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.0-rc-5.md

layout: release date: 2021-03-10 tag: v0.5.0-rc-5 Added edge release for plugins @kumarabd (#2522) Removed residues @kumarabd (#2518) Improvements @kumarabd (#2516) [mesheryctl] Modified system config command to use go-client @hexxdump (#2513) fix for operator panic @kumarabd (#2512) fix for edge release @kumarabd (#2510) ui fix for panics @kumarabd (#2509) reverted to graphql resolvers @kumarabd (#2492) [mesheryctl] added update prompt @aneeshnema (#2505) removed extra line in the file verbose.yml @alonsolopezr (#2508) control plane dashboard @vineethvanga18 (#2506) Hook control plane with graphql @utkarsh-pro (#2504) [mesheryctl] platform: kubernetes support for `system stop` command @navendu-pottekkat (#2497) Update BillboardJS from v1 to v2 @dhruv0000 (#2494) [Docs] Instructions added to run Meshery-Istio in local enviroment @piyushsingariya (#2465) [mesheryctl] fixed system context commands, removed dependency on models/mesheryctl_config.go @aneeshnema (#2491) Minor changes @dhruv0000 (#2493) [mesheryctl] Added adapters flag @metonymic-smokey (#2463) Fixed alignment of Meshery Sidebar with the Header @chinmaym07 (#2459) [UI] Fixes failing Docker build of UI @dhruv0000 (#2462) controlplane queries @vineethvanga18 (#2430) [Docs] Language separation for Functionality index @leecalcote (#2457) [mesheryctl] Create dedicated section for tokens in default config @aneeshnema (#2436) Improve provider capabilities loading @utkarsh-pro (#2452) Improve context view command output @utkarsh-pro (#2443) [UI]: Fixes chip and paper card in /management @Nikhil-Ladha (#2446) Updated response for loadReqBasePath @dhruv0000 (#2418) Fixed: Header Overlapping with sidebar @chinmaym07 (#2445) Fixed error 404 on installation page @Anita-ihuman (#2441) Bump github.com/layer5io/meshkit from 0.2.0 to 0.2.3 @dependabot (#2487) Bump github.com/prometheus/common from 0.15.0 to 0.18.0 @dependabot (#2483) Bump github.com/spf13/cobra from 1.1.1 to 1.1.3 @dependabot (#2486) Bump js-yaml from 3.14.1 to 4.0.0 in /ui @dependabot (#2475) Bump caniuse-lite from 1.0.30001183 to 1.0.30001194 in /ui @dependabot (#2495) Bump react-lazyload from 3.1.0 to 3.2.0 in /ui @dependabot (#2474) Bump @babel/types from 7.12.13 to 7.13.0 in /ui @dependabot (#2477) Bump next from 10.0.6 to 10.0.7 in /provider-ui @dependabot (#2471) Bump cypress from 6.4.0 to 6.5.0 in /provider-ui @dependabot (#2469) Bump eslint from 7.19.0 to 7.21.0 in /provider-ui @dependabot (#2472) Bump @fortawesome/free-solid-svg-icons from 5.15.1 to 5.15.2 in /ui @dependabot (#2476) Bump eslint from 7.19.0 to 7.21.0 in /ui @dependabot (#2473) Bump husky from 4.3.8 to 5.1.2 in /ui @dependabot (#2470) Bump github.com/sirupsen/logrus from 1.7.0 to 1.8.0 @dependabot (#2485) Bump google.golang.org/grpc from 1.35.0 to 1.36.0 @dependabot (#2484) Bump notistack from 1.0.3 to 1.0.5 in /ui @dependabot (#2478) Bump codemirror from 5.59.2 to 5.59.4 in /ui @dependabot (#2468) Added channel docs @metonymic-smokey (#2507) Jomefavourite#2304 @jomefavourite (#2388) Updated Suported Service Meshes table @bartkalanski (#2447)
Project: Beam (App Definition and Development / Streaming & Messaging)
File: universityofweimar.md

title: "University of Weimar" icon: /images/logos/powered-by/universityofweimar.png hasLink: "https://www.uni-weimar.de/de/universitaet/start/" <!-- 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_cluster_volume-expand.md

title: kbcli cluster volume-expand Expand volume with the specified components and volumeClaimTemplates in the cluster. ``` kbcli cluster volume-expand NAME [flags] ``` ``` kbcli cluster volume-expand mycluster --components=mysql --volume-claim-templates=data --storage=10Gi ``` ``` --auto-approve Skip interactive approval before expanding the cluster volume --components strings Component names to this operations --dry-run string[="unchanged"] Must be "client", or "server". If with client strategy, only print the object that would be sent, and no data is actually sent. If with server strategy, submit the server-side request, but no data is persistent. (default "none") -h, --help help for volume-expand --name string OpsRequest name. if not specified, it will be randomly generated -o, --output format Prints the output in the specified format. Allowed values: JSON and YAML (default yaml) --storage string Volume storage size (required) --ttlSecondsAfterSucceed int Time to live after the OpsRequest succeed -t, --volume-claim-templates strings VolumeClaimTemplate names in components (required) ``` ``` --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 ``` - Cluster command.
Project: KICS (Provisioning / Security & Compliance)
File: b1a72f66-2236-4f3b-87ba-0da1b366956f.md

title: SNS Topic Encrypted With AWS Managed Key hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b1a72f66-2236-4f3b-87ba-0da1b366956f Query name: SNS Topic Encrypted With AWS Managed Key Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: SNS (Simple Notification Service) Topic should be encrypted with customer-managed KMS keys instead of AWS managed keys<br> ```tf title="Positive test num. 1 - tf file" hl_lines="3" resource "awssnstopic" "user_updates" { name = "user-updates-topic" kmsmasterkey_id = "alias/aws/sns" } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="11" provider "aws" { region = "us-east-1" } data "awskmskey" "by_alias" { key_id = "alias/aws/sns" } resource "awssnstopic" "test" { name = "sns_ecnrypted" kmsmasterkeyid = data.awskmskey.byalias.arn } ``` ```tf title="Negative test num. 1 - tf file" provider "aws2" { region = "us-east-1" } resource "awssnstopic" "test2" { name = "sns_ecnrypted" kmsmasterkey_id = "alias/MyAlias" } ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: nginx.md

+++ title = "nginx resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "nginx" identifier = "inspec/resources/os/nginx.md nginx resource" parent = "inspec/resources/os" +++ Use the `nginx` Chef InSpec audit resource to test the fields and validity of nginx. Nginx resource extracts and exposes data reported by the command 'nginx -V' {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.37.6 of InSpec. An `nginx` Chef InSpec audit resource block extracts configuration settings that should be tested: describe nginx do its('attribute') { should eq 'value' } end describe nginx('path to nginx') do its('attribute') { should eq 'value' } end where `'attribute'` is a configuration parsed from result of the command 'nginx -V' `'value'` is the value that is expected of the attribute `compilerinfo`, `errorlogpath`, `httpclientbodytemppath`, `httpfastcgitemppath`, `httplogpath`, `httpproxytemppath`, `httpscgitemppath`, `httpuwsgitemppath`, `lockpath`, `modules`, `modulespath`, `opensslversion`, `prefix`, `sbinpath`, `service`, `supportinfo`, `version` `version` returns a string of the version of the running nginx instance describe nginx do its('version') { should eq '1.12.0' } end `modules` returns a array modules in the running nginx instance describe nginx do its('modules') { should include 'my_module' } end `openssl_version` returns a hash with 'version' and 'date' as keys describe nginx do its('openssl_version.date') { should eq '11 Feb 2013' } end `compiler_info` returns a hash with 'compiler' , version' and 'date' as keys describe nginx do its('compiler_info.compiler') { should eq 'gcc' } end `support_info` returns a string containing supported protocols describe nginx do its('support_info') { should match /TLS/ } end
Project: Trivy-Operator (Provisioning / Security & Compliance)
File: README.md

An index of various (informal) design and explanation documents that were created for different purposes. Mainly to brainstorm how trivy-operator works. NOTE This is not an official documentation of trivy-operator. Some design documents may be out of date. | File | Description | |-|--| | [cachingscanresultbyrepo_digest.md] | [DRAFT] Caching Scan Results by Image Reference | | [designtrivyfilesystemscanner.md] | Scan Container Images with Trivy Filesystem Scanner | | [designvulnerabilityscaninsame_ns.md] | Schedule vulnerability scan jobs in the same namespace as scanned workload | | [designscanbyimagedigest.png] | Design of vulnerability scanning by image digest (ContainerStatus vs PodSpec). | | [designvulnerabilityscanning_2.0.png] | Design of most efficient vulnerability scanning that you can imagine. | | [designnamespacesecurity_report.pdf] | Design of a security report generated by trivy-operator CLI for a given namespace. |
Project: Checkov (Provisioning / Security & Compliance)
File: Docker.md

layout: default published: true title: Docker nav_order: 7 ```coffeescript docker pull bridgecrew/checkov docker run --tty --volume /user/tf:/tf --workdir /tf bridgecrew/checkov --directory /tf ``` If you are using Python 3.6 (which is the default version in Ubuntu 18.04) Checkov will not work and it will fail with `ModuleNotFoundError: No module named 'dataclasses'`. In this case, you can use the Docker version instead.\n\nIn certain cases, when redirecting `docker run --tty` output to a file - for example, if you want to save the Checkov JUnit output to a file - will cause extra control characters to be printed. This can break file parsing. If you encounter this, remove the --tty flag. Docker images are keyless signed with `cosign` and attested with a `CycloneDX` formatted SBOM. ```shell COSIGN_EXPERIMENTAL=1 cosign verify bridgecrew/checkov | jq . ``` ```shell COSIGN_EXPERIMENTAL=1 cosign verify-attestation --type cyclonedx bridgecrew/checkov | jq -r .payload | base64 -D | jq . ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_project_iam_custom_roles.md

+++ title = "googleprojectiamcustomroles resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleprojectiamcustomroles" identifier = "inspec/resources/gcp/googleprojectiamcustomroles.md googleprojectiamcustomroles resource" parent = "inspec/resources/gcp" +++ A `googleprojectiamcustomroles` is used to test a Google CustomRole resource ```ruby describe googleprojectiamcustomroles(project: 'chef-gcp-inspec') do its('names') { should include "projects/project-id/roles/role-id" } end ``` Properties that can be accessed from the `googleprojectiamcustomroles` resource: See the resource for more information. `names` : an array of `googleprojectiamcustomrole` name `titles` : an array of `googleprojectiamcustomrole` title `descriptions` : an array of `googleprojectiamcustomrole` description `included_permissions` : an array of `googleprojectiamcustomrole` included_permissions `stages` : an array of `googleprojectiamcustomrole` stage `deleteds` : an array of `googleprojectiamcustomrole` deleted This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: KICS (Provisioning / Security & Compliance)
File: 857f8808-e96a-4ba8-a9b7-f2d4ec6cad94.md

title: Automatic Minor Upgrades Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 857f8808-e96a-4ba8-a9b7-f2d4ec6cad94 Query name: Automatic Minor Upgrades Disabled Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: RDS instance should have automatic minor upgrades enabled, which means the attribute 'autominorversion_upgrade' must be set to true.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10 12" name: community - create minimal aurora instance in default VPC and default subnet group community.aws.rds_instance: engine: aurora dbinstanceidentifier: ansible-test-aurora-db-instance instance_type: db.t2.small password: "{{ password }}" username: "{{ username }}" cluster_id: ansible-test-cluster autominorversion_upgrade: false name: community - Create a DB instance using the default AWS KMS encryption key community.aws.rds_instance: id: test-encrypted-db state: present engine: mariadb storage_encrypted: True dbinstanceclass: db.t2.medium username: "{{ username }}" password: "{{ password }}" allocatedstorage: "{{ allocatedstorage }}" ``` ```yaml title="Negative test num. 1 - yaml file" name: negative - create minimal aurora instance in default VPC and default subnet group community.aws.rds_instance: engine: aurora dbinstanceidentifier: ansible-test-aurora-db-instance instance_type: db.t2.small password: '{{ password }}' username: '{{ username }}' cluster_id: ansible-test-cluster autominorversion_upgrade: true name: negative - Create a DB instance using the default AWS KMS encryption key community.aws.rds_instance: id: test-encrypted-db state: present engine: mariadb storage_encrypted: true dbinstanceclass: db.t2.medium username: '{{ username }}' password: '{{ password }}' allocatedstorage: '{{ allocatedstorage }}' autominorversion_upgrade: yes name: negative - Create a DB instance using the default AWS KMS encryption key community.aws.rds_instance: id: test-encrypted-db state: present engine: mariadb storage_encrypted: true dbinstanceclass: db.t2.medium username: '{{ username }}' password: '{{ password }}' allocatedstorage: '{{ allocatedstorage }}' autominorversion_upgrade: true ```
Project: Nocalhost (App Definition and Development / Application Definition & Image Build)
File: bug-report.md

name: Bug Report about: Report a bug encountered while using nocalhost title: '' labels: '' assignees: '' <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--> What happened: What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: OS (e.g: `Macos 10.15.5 (19F96)` or `Windows 10`): nhctl version (use `nchtl version` command): helm version (use `helm version` command): kubectl version (use `kubectl version` command): Others:
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_infra_delete.md

title: kbcli infra delete delete kubernetes cluster. ``` kbcli infra delete [flags] ``` ``` kbcli infra delete -c cluster.yaml ``` ``` -c, --config string Specify infra cluster config file. [option] --debug set debug mode --delete-cri delete cri --etcd strings Specify etcd nodes -h, --help help for delete --master strings Specify master nodes --name string Specify kubernetes cluster name --nodes strings List of machines on which kubernetes is installed. [require] -p, --password string Specify the password for the account to execute sudo. [option] --private-key string The PrimaryKey for ssh to the remote machine. [option] --private-key-path string Specify the file PrimaryKeyPath of ssh to the remote machine. default ~/.ssh/id_rsa. -t, --timeout int Specify the ssh timeout.[option] (default 30) -u, --user string Specify the account to access the remote server. [require] --worker strings Specify worker nodes ``` ``` --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 ``` - infra command
Project: StarRocks (App Definition and Development / Database)
File: bitmap_from_string.md

displayed_sidebar: "English" Converts a string into a BITMAP. The string is composed of a set of UINT64 numbers separated by commas. For example, the "0, 1, 2" string will be converted into a Bitmap, in which bits 0, 1 and 2 are set. If the input field is invalid, NULL will be returned. This function deduplicates the input string during the conversion. It must be used with other functions, such as to return results on terminals. ```Haskell BITMAP BITMAPFROMSTRING(VARCHAR input) ``` Returns a BITMAP value. If the input string is invalid, NULL is returned. If the input string is empty, an empty value is returned. ```Plain Text -- The input is empty and an empty value is returned. MySQL > select bitmaptostring(bitmap_empty()); +-+ | bitmaptostring(bitmap_empty()) | +-+ | | +-+ -- `0,1,2` is returned. MySQL > select bitmaptostring(bitmapfromstring("0, 1, 2")); +-+ | bitmaptostring(bitmapfromstring('0, 1, 2')) | +-+ | 0,1,2 | +-+ -- `-1` is an invalid input and NULL is returned. MySQL > select bitmaptostring(bitmapfromstring("-1, 0, 1, 2")); +--+ | bitmapfromstring('-1, 0, 1, 2') | +--+ | NULL | +--+ -- 2^64 is an invalid input and NULL is returned. MySQL > select bitmaptostring(bitmapfromstring("0, 18446744073709551616")); +--+ | bitmaptostring(bitmapfromstring('0, 18446744073709551616')) | +--+ | NULL | +--+ -- The input string is deduplicated. MySQL > select bitmaptostring(bitmapfromstring("0, 1, 1")); +-+ | bitmaptostring(bitmapfromstring('0, 1, 1')) | +-+ | 0,1 | +-+ ``` BITMAPFROMSTRING,BITMAP