cwielenb/CNCF-Dataset huggingface dataset:
Project: ShardingSphere (App Definition and Development / Database)
File: count-sharding-rule.en.md

+++ title = "COUNT SHARDING RULE" weight = 15 +++ The `COUNT SHARDING RULE` syntax is used to query the number of sharding rules for specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql CountShardingRule::= 'COUNT' 'SHARDING' 'RULE' ('FROM' databaseName)? databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When `databaseName` is not specified, the default is the currently used `DATABASE`. If `DATABASE` is not used, `No database selected` will be prompted. | Column | Description | |--|-| | rule_name | rule type | | database | the database to which the rule belongs | | count | the number of the rule | Query the number of sharding rules for specified database. ```sql COUNT SHARDING RULE FROM sharding_db; ``` ```sql mysql> COUNT SHARDING RULE FROM sharding_db; +--+-+-+ | rule_name | database | count | +--+-+-+ | shardingtable | shardingdb | 2 | | shardingtablereference | sharding_db | 2 | +--+-+-+ 2 rows in set (0.00 sec) ``` Query the number of sharding rules for current database. ```sql COUNT SHARDING RULE; ``` ```sql mysql> COUNT SHARDING RULE; +--+-+-+ | rule_name | database | count | +--+-+-+ | shardingtable | shardingdb | 2 | | shardingtablereference | sharding_db | 2 | +--+-+-+ 2 rows in set (0.00 sec) ``` `COUNT`, `SHARDING`, `RULE`, `FROM`
Project: Beam (App Definition and Development / Streaming & Messaging)
File: datatonic.md

title: "Datatonic" icon: /images/logos/powered-by/datatonic.png hasLink: "https://www.youtube.com/watch?v=GBKqw03doHE" <!-- 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: Updatecli (Provisioning / Automation & Configuration)
File: ADOPTERS.md

Being able to assess the kind of organizations who adopt Updatecli is important. First for our community, as it helps them to understand how similar organization benefits from the project. But also for the project itself. It allows us to better understand how Updatecli is being used which help us to drive the project in the right direction. This document contains a none exhaustive list of organizations who adopted Updatecli. We are adding public references of Updatecli but feel free to add your organization to the list, with a link to your organization website.
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: ISSUE_TEMPLATE.md

<! Thanks for filing an issue! Before you submit, please read the following: Check the other issue templates if you are trying to submit a bug report, feature request, or question. Search open/closed issues before submitting since someone might have asked the same thing before! For ansible operator related requests, please create the issue in https://github.com/operator-framework/ansible-operator-plugins -->
Project: kube-hunter (Provisioning / Security & Compliance)
File: KHV031.md

vid: KHV031 title: Etcd Remote Write Access Event categories: [Remote Code Execution] severity: critical Etcd (Kubernetes' Database) is writable without authentication. This gives full control of your Kubernetes cluster to an attacker with access to etcd. Ensure your etcd is accepting connections only from the Kubernetes API, using the `--trusted-ca-file` etcd flag. This is usually done by the installer, or cloud platform.
Project: Meshery (Provisioning / Automation & Configuration)
File: minio-operator.md

layout: integration title: MinIO Operator subtitle: Collaborative and visual infrastructure as code for MinIO Operator image: /assets/img/integrations/minio-operator/icons/color/minio-operator-color.svg permalink: extensibility/integrations/minio-operator docURL: https://docs.meshery.io/extensibility/integrations/minio-operator description: integrations-category: App Definition and Development integrations-subcategory: Database registrant: Artifact Hub components: name: tenant colorIcon: assets/img/integrations/minio-operator/components/tenant/icons/color/tenant-color.svg whiteIcon: assets/img/integrations/minio-operator/components/tenant/icons/white/tenant-white.svg description: featureList: [ "AWS S3 Compatibility", "MinIO IAM is built with AWS Identity and Access Management (IAM) compatibility at its core and presents that framework to applications and users no matter the environment.", "MinIO offers Active Active, Multi-Site Replication for Object Storage is a key requirement for mission-critical production environments." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.8.14.md

RabbitMQ `3.8.14` is a maintenance release that restores Erlang 22.3 compatibility for environments that use . This release . is highly recommended for best forward compatibility with future RabbitMQ versions. explains what package repositories and tools can be used to provision a recent version of Erlang `23.x`. See upgrade and compatibility notes first if upgrading from an earlier release series (e.g. `3.7.x`). See the for general documentation on upgrades and for release notes of other releases. When upgrading to this release from `3.7.15` or an older version, extra care has to be taken. Because older RabbitMQ CLI tools can be incompatible with Erlang 22+ releases, RabbitMQ must be upgraded at the same time as Erlang. Alternatively the node can be upgraded to `3.7.18` on Erlang 21.3 first, then Erlang 23.x, then RabbitMQ to the most recent 3.8.x release. Any questions about this release, upgrades or RabbitMQ in general are welcome on the and . failed witn an exception on Erlang 22.3. Nodes running on Erlang 23 are not affected. GitHub issue: A warnings about async I/O threads was replaced with a similar one about dirty I/O schedulers. This keeps the message up with the settings used in modern Erlang releases. GitHub issue: Community-maintained were revisited. Contributed by Michele @mbaldessari Baldessari. GitHub issue: There were no dependency changes. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.8.14.tar.xz` instead of the source tarball produced by GitHub.
Project: Stolon (App Definition and Development / Database)
File: stolonctl_clusterdata_read.md

Retrieve the current cluster data Retrieve the current cluster data ``` stolonctl clusterdata read [flags] ``` ``` -h, --help help for read --pretty pretty print ``` ``` --cluster-name string cluster name --kube-context string name of the kubeconfig context to use --kube-namespace string name of the kubernetes namespace to use --kube-resource-kind string the k8s resource kind to be used to store stolon clusterdata and do sentinel leader election (only "configmap" is currently supported) --kubeconfig string path to kubeconfig file. Overrides $KUBECONFIG --log-level string debug, info (default), warn or error (default "info") --metrics-listen-address string metrics listen address i.e "0.0.0.0:8080" (disabled by default) --store-backend string store backend type (etcdv2/etcd, etcdv3, consul or kubernetes) --store-ca-file string verify certificates of HTTPS-enabled store servers using this CA bundle --store-cert-file string certificate file for client identification to the store --store-endpoints string a comma-delimited list of store endpoints (use https scheme for tls communication) (defaults: http://127.0.0.1:2379 for etcd, http://127.0.0.1:8500 for consul) --store-key string private key file for client identification to the store --store-prefix string the store base prefix (default "stolon/cluster") --store-skip-tls-verify skip store certificate verification (insecure!!!) --store-timeout duration store request timeout (default 5s) ``` - Manage current cluster data
Project: ClickHouse (App Definition and Development / Database)
File: files.md

slug: /en/sql-reference/functions/files sidebar_position: 75 sidebar_label: Files Reads a file as string and loads the data into the specified column. The file content is not interpreted. Also see table function . Syntax ``` sql file(path[, default]) ``` Arguments `path` The path of the file relative to . Supports wildcards ``, `*`, `?`, `{abc,def}` and `{N..M}` where `N`, `M` are numbers and `'abc', 'def'` are strings. `default` The value returned if the file does not exist or cannot be accessed. Supported data types: and . Example Inserting data from files a.txt and b.txt into a table as strings: ``` sql INSERT INTO table SELECT file('a.txt'), file('b.txt'); ```
Project: KICS (Provisioning / Security & Compliance)
File: c3cab8c4-6c52-47a9-942b-c27f26fbd7d2.md

title: Parameter File Type Not In 'formData' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c3cab8c4-6c52-47a9-942b-c27f26fbd7d2 Query name: Parameter File Type Not In 'formData' Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Structure and Semantics URL: The In field of Parameter Object must be 'formData' when type is 'file'<br> ```json title="Positive test num. 1 - json file" hl_lines="12 31" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "parameters": [ { "name": "limit2", "in": "query", "description": "return a file with limit info", "required": true, "type": "file" } ], "operationId": "listVersionsV2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } } } } }, "parameters": { "limitParam": { "name": "limit", "in": "query", "description": "return a file with limit info", "required": true, "type": "file" } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="10 22" swagger: '2.0' info: title: Simple API Overview version: 1.0.0 paths: "/": get: parameters: name: limit2 in: query description: return a file with limit info required: true type: file operationId: listVersionsV2 summary: List API versions responses: '200': description: 200 response parameters: limitParam: name: limit in: query description: return a file with limit info required: true type: file ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "parameters": [ { "name": "limit2", "in": "formData", "description": "return a file with limit info", "required": true, "type": "file" } ], "operationId": "listVersionsV2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } } } } }, "parameters": { "limitParam": { "name": "limit", "in": "formData", "description": "return a file with limit info", "required": true, "type": "file" } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: '2.0' info: title: Simple API Overview version: 1.0.0 paths: "/": get: parameters: name: limit2 in: formData description: return a file with limit info required: true type: file operationId: listVersionsV2 summary: List API versions responses: '200': description: 200 response parameters: limitParam: name: limit in: formData description: return a file with limit info required: true type: file ```
Project: Kubescape (Provisioning / Security & Compliance)
File: architecture.md

Please check back soon for more: until then, enjoy these fine diagrams. <div align="center"> <img src="img/architecture.drawio.svg" width="600" alt="Component architecture"> </div> <div align="center"> <img src="img/ks-cli-arch.png" width="600" alt="cli-diagram"> </div> <div align="center"> <img src="img/ks-operator-arch.png" width="600" alt="operator-diagram"> </div>
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.5.8.md

RabbitMQ `3.5.8` fixes a security vulnerability () in the MQTT plugin. `rabbitdiagnostics:maybestuck/0` no longer prints process' dictionary because it may contain PRNG seed values and other sensitive information. Authentication with correct username but omitted password succeeded when TLS/x509 certificate wasn't provided by the client. CVE allocation for this vulnerability is pending. GitHub issue: To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained. To upgrade a RabbitMQ cluster, follow the instructions . Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-3.5.8.tar.gz`.
Project: Hazelcast Jet (App Definition and Development / Streaming & Messaging)
File: blue-green.md

title: Blue-Green Client description: Configure Blue-Green Client with Hazelcast Jet id: version-4.5-blue-green original_id: blue-green Blue/Green deployment refers to a software technique which can be used to reduce system downtime by deploying two mirrored production environments, referred to as blue (active) and green (idle). One of the environments is running in production while the other is in active standby. The Jet client can be configured to switch to the other cluster in case when a connection to the production environment fails. To configure the client to use blue/green feature, you'll need to have a file called `hazelcast-client-failover.yaml` which is a root config file that references a client configuration file for each cluster. It can be configured as follows: ```yaml hazelcast-client-failover: try-count: 10 clients: hazelcast-client-clusterA.yaml hazelcast-client-clusterB.yaml ``` When acquiring the Jet client instance, `Jet.newJetFailoverClient()` should be used to create the client. Submitting jobs using the failover client with `jet submit` command is not supported at this time. Once the client detects that one of the clusters is down, it will automatically switch to the other one. After switching to cluster B, the state of any running job on cluster A will be undefined. The jobs may continue running on cluster A if the cluster is still alive and the switching happened due to a network problem. If you try to query the state of the job using the Job interface, youll get a `JobNotFoundException`. While you can use the Jet client for any IMDG operation, in Jet context a client is mostly used for submitting jobs to the cluster. After the submission the job lives in the cluster, client is used to query the state of the job. Therefore Blue/Green deployment is not applicable for long-lived jobs, but can be used with short-lived batch jobs which will not cause any problem if run on different clusters at the same time, like queries for example. Hazelcast Jet Client offers many configuration options for detecting failures in the cluster You can also force a client to specifically disconnect from one cluster and connect to the other one through blacklisting. For a list of detailed features and options for Blue/Green configuration options see the .
Project: KICS (Provisioning / Security & Compliance)
File: cfdcabb0-fc06-427c-865b-c59f13e898ce.md

title: Redshift Not Encrypted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: cfdcabb0-fc06-427c-865b-c59f13e898ce Query name: Redshift Not Encrypted Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: AWS Redshift Cluster should be encrypted. Check if 'encrypted' field is false or undefined (default is false)<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1 17" resource "awsredshiftcluster" "positive1" { cluster_identifier = "tf-redshift-cluster" database_name = "mydb" master_username = "foo" master_password = "Mustbe8characters" node_type = "dc1.large" cluster_type = "single-node" } resource "awsredshiftcluster" "positive2" { cluster_identifier = "tf-redshift-cluster" database_name = "mydb" master_username = "foo" master_password = "Mustbe8characters" node_type = "dc1.large" cluster_type = "single-node" encrypted = false } ``` ```tf title="Negative test num. 1 - tf file" resource "awsredshiftcluster" "negative1" { cluster_identifier = "tf-redshift-cluster" database_name = "mydb" master_username = "foo" master_password = "Mustbe8characters" node_type = "dc1.large" cluster_type = "single-node" encrypted = true } ```
Project: Apache Storm (App Definition and Development / Streaming & Messaging)
File: Hooks.md

title: Hooks layout: documentation documentation: true Storm provides hooks with which you can insert custom code to run on any number of events within Storm. You create a hook by extending the class and overriding the appropriate method for the event you want to catch. There are two ways to register your hook: In the open method of your spout or prepare method of your bolt using the method. Through the Storm configuration using the config. These hooks are automatically registered in every spout or bolt, and are useful for doing things like integrating with a custom monitoring system. Storm also provides worker-level hooks that are called during worker startup, before any bolts or spouts are prepared/opened. You can create such a hook by extending (an implementation of ) and overriding the methods you want to implement. You can register your hook via `TopologyBuilder.addWorkerHook`. The `IWorkerHook#start(Map, WorkerUserContext)` lifecycle method exposes which provides a way to set application-level common resources via `setResource(String, Object)` method. This resource can then be retrieved by tasks, both spouts (via `open(Map, TopologyContext, SpoutOutputCollector`) and bolts (via `prepare(Map, TopologyContext, OutputCollector`), by calling `TopologyContext#getResource(String)`. Storm provides ways to share resources across different components via the following ways: taskData: this pertains to the task level data and can be written and read by task and task hooks in their corresponding lifecycle methods (`open` for spout and `prepare` for bolt and task hook). write access: `TopologyContext#setTaskData(String, Object)` read access: `TopologyContext#getTask(String)` executorData: this pertains to executor level data and is shared across tasks and task hooks which are managed by the concerned executor. Similar to above it is accessible to spouts via `open` and to bolts and task hooks via `prepare` lifecycle method. write access: `TopologyContext#setExecutorData` read access: `TopologyContext#getExecutorData(String)` userResources: this pertains to worker level data and is shared across executors, tasks, worker hooks and task hooks which are managed by the concerned worker. Unlike others it can only be written by worker hooks. write access: `WorkerUserContext#setResource(String, Object)` read access: `WorkerTopologyContext#getResouce(String)` or `TopologyContext#getResource(String)`
Project: KICS (Provisioning / Security & Compliance)
File: 57b9893d-33b1-4419-bcea-a717ea87e139.md

title: S3 Bucket ACL Allows Read to Any Authenticated User hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 57b9893d-33b1-4419-bcea-a717ea87e139 Query name: S3 Bucket ACL Allows Read to Any Authenticated User Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: S3 Buckets should not be readable to any authenticated user<br> ```tf title="Positive test num. 1 - tf file" hl_lines="16" provider "aws" { region = "us-east-1" } terraform { required_providers { aws = { source = "hashicorp/aws" version = "~> 3.0" } } } resource "awss3bucket" "positive1" { bucket = "my-tf-test-bucket" acl = "authenticated-read" tags = { Name = "My bucket" Environment = "Dev" } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="6" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "authenticated-read" versioning = { enabled = true } } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="20" provider "aws" { region = "us-east-1" } terraform { required_providers { aws = { source = "hashicorp/aws" version = "4.2.0" } } } resource "awss3bucket" "example1" { bucket = "my-tf-example-bucket" } resource "awss3bucketacl" "examplebucket_acl" { bucket = awss3bucket.example1.id acl = "authenticated-read" } ``` ```tf title="Negative test num. 1 - tf file" provider "aws" { region = "us-east-1" } terraform { required_providers { aws = { source = "hashicorp/aws" version = "~> 3.0" } } } resource "awss3bucket" "negative1" { bucket = "my-tf-test-bucket" acl = "private" tags = { Name = "My bucket" Environment = "Dev" } } ``` ```tf title="Negative test num. 2 - tf file" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" versioning = { enabled = true } } ``` ```tf title="Negative test num. 3 - tf file" provider "aws" { region = "us-east-1" } terraform { required_providers { aws = { source = "hashicorp/aws" version = "4.2.0" } } } resource "awss3bucket" "example0" { bucket = "my-tf-example-bucket" } resource "awss3bucketacl" "examplebucket_acl" { bucket = awss3bucket.example0.id acl = "private" } ```
Project: KICS (Provisioning / Security & Compliance)
File: 050f085f-a8db-4072-9010-2cca235cc02f.md

title: Auto Scaling Group With No Associated ELB hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 050f085f-a8db-4072-9010-2cca235cc02f Query name: Auto Scaling Group With No Associated ELB Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Availability URL: AWS Auto Scaling Groups must have associated ELBs to ensure high availability and improve application performance. This means the attribute 'load_balancers' must be defined and not empty.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" name: elb1 community.aws.ec2_asg: name: special load_balancers: [] availability_zones: [ 'eu-west-1a', 'eu-west-1b' ] launchconfigname: 'lc-1' min_size: 1 max_size: 10 desired_capacity: 5 vpczoneidentifier: [ 'subnet-abcd1234', 'subnet-1a2b3c4d' ] tags: environment: production propagateatlaunch: no ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="2" name: elb2 ec2_asg: name: special availability_zones: [ 'eu-west-1a', 'eu-west-1b' ] launchconfigname: 'lc-1' min_size: 1 max_size: 10 desired_capacity: 5 vpczoneidentifier: [ 'subnet-abcd1234', 'subnet-1a2b3c4d' ] tags: environment: production propagateatlaunch: no ``` ```yaml title="Negative test num. 1 - yaml file" name: elb12 community.aws.ec2_asg: name: special load_balancers: [ 'lb1', 'lb2' ] availability_zones: [ 'eu-west-1a', 'eu-west-1b' ] launchconfigname: 'lc-1' min_size: 1 max_size: 10 desired_capacity: 5 vpczoneidentifier: [ 'subnet-abcd1234', 'subnet-1a2b3c4d' ] tags: environment: production propagateatlaunch: no ``` ```yaml title="Negative test num. 2 - yaml file" name: elb22 ec2_asg: name: special load_balancers: [ 'lb1', 'lb2' ] availability_zones: [ 'eu-west-1a', 'eu-west-1b' ] launchconfigname: 'lc-1' min_size: 1 max_size: 10 desired_capacity: 5 vpczoneidentifier: [ 'subnet-abcd1234', 'subnet-1a2b3c4d' ] tags: environment: production propagateatlaunch: no ```