cwielenb/CNCF-Dataset huggingface dataset:
Project: Chef InSpec (Provisioning / Security & Compliance)
File: cassandradb_session.md

+++ title = "cassandradb_session resource" draft = false gh_repo = "inspec" platform = "os" [menu] [menu.inspec] title = "cassandradb_session" identifier = "inspec/resources/os/cassandradbsession.md cassandradbsession resource" parent = "inspec/resources/os" +++ Use the `cassandradb_session` Chef InSpec audit resource to test Cassandra Query Language (CQL) commands run against a Cassandra database. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} A `cassandradb_session` resource block declares the username, password, host, and port to use for the session, and then the command to be run: describe cassandradb_session(user: 'USERNAME', password: 'PASSWORD', host: 'localhost', port: 9042).query('QUERY') do its('value') { should eq('EXPECTED') } end where `cassandradb_session` declares a username, password, host and port to run the query. `query('QUERY')` contains the query to be run. `its('value') { should eq('expected') }` compares the results of the query against the expected result in the test. The `cassandradb_session` InSpec resource accepts `user`, `password`, `host`, and `port` parameters. In Particular: Default value: `cassandra`. Default value: `cassandra`. The following examples show how to use this Chef InSpec audit resource. ```ruby cql = cassandradbsession(user: 'MYUSER', password: 'PASSWORD', host: 'localhost', port: 9042) describe cql.query("SELECT cluster_name FROM system.local") do its('output') { should match /Test Cluster/ } end ``` ```ruby cql = cassandradbsession(user: 'MYUSER', password: 'PASSWORD', host: 'localhost', port: 9042) describe cql.query("use SAMPLEDB; SELECT name FROM SAMPLETABLE") do its('output') { should match /Test Name/ } end ``` {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: Copa (Provisioning / Security & Compliance)
File: pull_request_template.md

<!-- Please include the type of change in the PR title as "<type>: <summary>" Valid <type> include: build, ci, docs, feat, fix, perf, refactor, test See https://github.com/project-copacetic/copacetic/blob/master/CONTRIBUTING.md#pull-requests) for guidelines. --> Describe the changes in this pull request using active verbs such as Add, Remove, Replace ... Closes #<issueID_>
Project: ClickHouse (App Definition and Development / Database)
File: v20.9.5.5-stable.md

Backported in : Fix bug with MySQL database. When MySQL server used as database engine is down some queries raise Exception, because they try to get tables from disabled server, while it's unnecessary. For example, query `SELECT ... FROM system.parts` should work only with MergeTree tables and don't touch MySQL database at all. (). Backported in : Fixed the inconsistent behaviour when a part of return data could be dropped because the set for its filtration wasn't created. (). Backported in : Fix processing of very large entries in replication queue. Very large entries may appear in ALTER queries if table structure is extremely large (near 1 MB). This fixes . (). Backported in : Fix DROP TABLE for Distributed (racy with INSERT). (). Backported in : Fix rapid growth of metadata when using MySQL Master -> MySQL Slave -> ClickHouse MaterializeMySQL Engine, and `slaveparallelworker` enabled on MySQL Slave, by properly shrinking GTID sets. This fixes . (). Backported in : Now when parsing AVRO from input the LowCardinality is removed from type. Fixes . (). Backported in : Fixed . (). Backported in : Fix rare silent crashes when query profiler is on and ClickHouse is installed on OS with glibc version that has (supposedly) broken asynchronous unwind tables for some functions. This fixes . This fixes . ().
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_delete-backup.md

title: kbcli cluster delete-backup Delete a backup. ``` kbcli cluster delete-backup [flags] ``` ``` kbcli cluster delete-backup cluster-name --name backup-name ``` ``` -A, --all-namespaces If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace. --auto-approve Skip interactive approval before deleting --force If true, immediately remove resources from API and bypass graceful deletion. Note that immediate deletion of some resources may result in inconsistency or data loss and requires confirmation. --grace-period int Period of time in seconds given to the resource to terminate gracefully. Ignored if negative. Set to 1 for immediate shutdown. Can only be set to 0 when --force is true (force deletion). (default -1) -h, --help help for delete-backup --name strings Backup names --now If true, resources are signaled for immediate shutdown (same as --grace-period=1). -l, --selector string Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. ``` ``` --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: ClickHouse (App Definition and Development / Database)
File: covarpop.md

slug: /en/sql-reference/aggregate-functions/reference/covarpop sidebar_position: 36 Syntax: `covarPop(x, y)` Calculates the value of `((x - x)(y - y)) / n`. :::note This function uses a numerically unstable algorithm. If you need in calculations, use the `covarPopStable` function. It works slower but provides a lower computational error. :::
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: cgroupns.md

Set the cgroup namespace mode for the container. host: use the host's cgroup namespace inside the container. container:id: join the namespace of the specified container. private: create a new cgroup namespace. ns:path: join the namespace at the specified path. If the host uses cgroups v1, the default is set to host. On cgroups v2, the default is private.
Project: KICS (Provisioning / Security & Compliance)
File: dd7d70aa-a6ec-460d-b5d2-38b40253b16f.md

title: BOM - GCP PD hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: dd7d70aa-a6ec-460d-b5d2-38b40253b16f Query name: BOM - GCP PD Platform: Terraform Severity: <span style="color:#CCCCCC">Trace</span> Category: Bill Of Materials URL: A list of Persistent Disk resources found. Persistent Disk is Google's local durable storage service, fully integrated with Google Cloud products, Compute Engine and Google Kubernetes Engine.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1 12 44 60 76 28" resource "googlecomputedisk" "positive1" { name = "test-disk" type = "pd-ssd" zone = "us-central1-a" image = "debian-9-stretch-v20200805" labels = { environment = "dev" } physicalblocksize_bytes = 4096 } resource "googlecomputedisk" "positive2" { name = "test-disk" type = "pd-ssd" zone = "us-central1-a" image = "debian-9-stretch-v20200805" labels = { environment = "dev" } physicalblocksize_bytes = 4096 diskencryptionkey { sha256 = "A" } } resource "googlecomputedisk" "positive3" { name = "test-disk" type = "pd-ssd" zone = "us-central1-a" image = "debian-9-stretch-v20200805" labels = { environment = "dev" } physicalblocksize_bytes = 4096 diskencryptionkey { raw_key = "" sha256 = "A" } } resource "googlecomputedisk" "positive4" { name = "test-disk" type = "pd-ssd" zone = "us-central1-a" image = "debian-9-stretch-v20200805" labels = { environment = "dev" } physicalblocksize_bytes = 4096 diskencryptionkey { kmskeyself_link = "" sha256 = "A" } } resource "googlecomputedisk" "negative1" { name = "test-disk" type = "pd-ssd" zone = "us-central1-a" image = "debian-9-stretch-v20200805" labels = { environment = "dev" } physicalblocksize_bytes = 4096 diskencryptionkey { kmskeyself_link = "disk-crypto-key" sha256 = "A" } } resource "googlecomputedisk" "negative2" { name = "test-disk" type = "pd-ssd" zone = "us-central1-a" image = "debian-9-stretch-v20200805" labels = { environment = "dev" } physicalblocksize_bytes = 4096 diskencryptionkey { raw_key = "SGVsbG8gZnJvbSBHb29nbGUgQ2xvdWQgUGxhdGZvcm0=" sha256 = "A" } } ``` ```tf title="Negative test num. 1 - tf file" resource "googlebigquerydataset" "negative1" { datasetid = "exampledataset" friendly_name = "test" description = "This is a test description" location = "EU" defaulttableexpiration_ms = 3600000 labels = { env = "default" } access { role = "OWNER" userbyemail = googleserviceaccount.bqowner.email } access { role = "READER" domain = "hashicorp.com" } } ```
Project: ArangoDB (App Definition and Development / Database)
File: as_failure_lvalue.md

+++ title = "`auto as_failure() const &`" description = "Return the output from free function `failure()` containing a copy of any errored state." categories = ["observers"] weight = 910 +++ Return the output from free function {{% api "auto failure(T &&, ...)" %}} containing a copy of any errored state. The error state is accessed using {{% api "const errortype &assumeerror() const & noexcept" %}}. Requires: Always available. Complexity: Whatever that of `error_type`'s copy constructor is. Guarantees: None.
Project: ShardingSphere (App Definition and Development / Database)
File: parser-test.en.md

+++ title = "SQL Parser Test" weight = 1 +++ Not like Integration test, SQL parse test does not need a specific database environment, just define the sql to parse, and the assert data: As mentioned `sql-case-id` in Integration test, test-case-id could be shared in different module to test, and the file is in `shardingsphere-test-it-parser` module, at `test/it/parser/src/main/resources/sql/supported/${SQL-TYPE}/*.xml` The assert data is at `test/it/parser/src/main/resources/case/${SQL-TYPE}/*.xml` in that xml file, it could assert against the table name, token or sql condition and so on. For example: ```xml <parser-result-sets> <parser-result sql-case-id="insertwithmultiple_values"> <tables> <table name="t_order" /> </tables> <tokens> <table-token start-index="12" table-name="t_order" length="7" /> </tokens> <sharding-conditions> <and-condition> <condition column-name="orderid" table-name="torder" operator="EQUAL"> <value literal="1" type="int" /> </condition> <condition column-name="userid" table-name="torder" operator="EQUAL"> <value literal="1" type="int" /> </condition> </and-condition> <and-condition> <condition column-name="orderid" table-name="torder" operator="EQUAL"> <value literal="2" type="int" /> </condition> <condition column-name="userid" table-name="torder" operator="EQUAL"> <value literal="2" type="int" /> </condition> </and-condition> </sharding-conditions> </parser-result> </parser-result-sets> ``` When these configs are ready, launch the test engine in `test/it/parser` to test SQL parse.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-machine.1.md

% podman-machine 1 podman\-machine - Manage Podman's virtual machine podman machine subcommand `podman machine` is a set of subcommands that manage Podman's virtual machine. Podman on MacOS and Windows requires a virtual machine. This is because containers are Linux - containers do not run on any other OS because containers' core functionality are tied to the Linux kernel. Podman machine must be used to manage MacOS and Windows machines, but can be optionally used on Linux. All `podman machine` commands are rootless only. NOTE: The podman-machine configuration file is managed under the `$XDGCONFIGHOME/containers/podman/machine/` directory. Changing the `$XDGCONFIGHOME` environment variable while the machines are running can lead to unexpected behavior. | Command | Man Page | Description | ||-|| | info | | Display machine host info | | init | | Initialize a new virtual machine | | inspect | | Inspect one or more virtual machines | | list | | List virtual machines | | os | | Manage a Podman virtual machine's OS | | reset | | Reset Podman machines and environment | | rm | | Remove a virtual machine | | set | | Set a virtual machine setting | | ssh | | SSH into a virtual machine | | start | | Start a virtual machine | | stop | | Stop a virtual machine | , , , , , , , , , , March 2021, Originally compiled by Ashley Cui <acui@redhat.com>
Project: TDengine (App Definition and Development / Database)
File: 50-qstudio.md

sidebar_label: qStudio title: qStudio description: Step-by-Step Guide to Accessing TDengine Data with qStudio qStudio is a free cross-platform SQL data analysis tool that allows easy browsing of tables, variables, functions, and configuration settings in a database. The latest version of qStudio includes built-in support for TDengine. To connect TDengine using qStudio, you need to complete the following preparations: Install qStudio: qStudio supports major operating systems, including Windows, macOS, and Linux. Please ensure you download the correct installation package for your platform from the . Set up TDengine instance: Make sure TDengine is installed and running correctly, and the taosAdapter is installed and running. For detailed information, refer to the taosAdapter User Manual. Launch the qStudio application and select "Server" and then "Add Server..." from the menu. Choose TDengine from the Server Type dropdown. Configure the TDengine connection by entering the host address, port number, username, and password. If TDengine is deployed on the local machine, you can fill in the username and password only. The default username is "root," and the default password is "taosdata." Click "Test" to test the connection's availability. If the TDengine Java client library is not installed on the local machine, qStudio will prompt you to download and install it. Once connected successfully, the screen will display as shown below. If the connection fails, check that the TDengine service and taosAdapter are running correctly, and ensure that the host address, port number, username, and password are correct. Use qStudio to select databases and tables to browse data from the TDengine server. You can also perform operations on TDengine data by executing SQL commands. qStudio supports charting functions based on the data. For more information, please refer to the .
Project: YugabyteDB (App Definition and Development / Database)
File: select_start,ordinary_aggregate_fn_invocation,within_group_aggregate_fn_invocation.grammar.md

```output.ebnf select_start ::= SELECT [ ALL | DISTINCT [ ON { ( expression [ , ... ] ) } ] ] [ * | { { expression | fnoverwindow | ordinaryaggregatefn_invocation | withingroupaggregatefninvocation } [ [ AS ] name ] } [ , ... ] ] ordinaryaggregatefn_invocation ::= name ( { [ ALL | DISTINCT ] expression [ , ... ] | * } [ ORDER BY order_expr [ , ... ] ] ) [ FILTER ( WHERE boolean_expression ) ] withingroupaggregatefninvocation ::= name ( { expression [ , ... ] } ) WITHIN GROUP ( ORDER BY order_expr [ , ... ] ) [ FILTER ( WHERE boolean_expression ) ] ```
Project: ClickHouse (App Definition and Development / Database)
File: v21.3.15.4-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix extremely long backoff for background tasks when the background pool is full. Fixes . (). Backported in : Fix possible crash in `pointInPolygon` if the setting `validate_polygons` is turned off. (). 21.3 Docker unbundled fix ().
Project: Sonobuoy (Provisioning / Security & Compliance)
File: 03-systemd-logs.md

title: Systemd-logs link: https://github.com/vmware-tanzu/sonobuoy-plugins/tree/main/systemd-logs Gather log information from systemd, by chrooting into the nodes filesystem and running journalctl. Used by Sonobuoy for gathering host logs in a Kubernetes cluster.
Project: Meshery (Provisioning / Automation & Configuration)
File: helm-controller.md

layout: integration title: Helm Controller subtitle: Collaborative and visual infrastructure as code for Helm Controller image: /assets/img/integrations/helm-controller/icons/color/helm-controller-color.svg permalink: extensibility/integrations/helm-controller docURL: https://docs.meshery.io/installation/kubernetes/helm description: integrations-category: App Definition and Development integrations-subcategory: Application Definition & Image Build registrant: Artifact Hub components: name: bucket colorIcon: assets/img/integrations/helm-controller/components/bucket/icons/color/bucket-color.svg whiteIcon: assets/img/integrations/helm-controller/components/bucket/icons/white/bucket-white.svg description: name: git-repository colorIcon: assets/img/integrations/helm-controller/components/git-repository/icons/color/git-repository-color.svg whiteIcon: assets/img/integrations/helm-controller/components/git-repository/icons/white/git-repository-white.svg description: name: helm-chart colorIcon: assets/img/integrations/helm-controller/components/helm-chart/icons/color/helm-chart-color.svg whiteIcon: assets/img/integrations/helm-controller/components/helm-chart/icons/white/helm-chart-white.svg description: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] 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: KICS (Provisioning / Security & Compliance)
File: 12933609-c5bf-44b4-9a41-a6467c3b685b.md

title: BOM - AWS RDS hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 12933609-c5bf-44b4-9a41-a6467c3b685b Query name: BOM - AWS RDS Platform: Terraform Severity: <span style="color:#CCCCCC">Trace</span> Category: Bill Of Materials URL: A list of RDS resources found. Amazon Relational Database Service (Amazon RDS) is a collection of managed services that makes it simple to set up, operate, and scale databases in the cloud.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1 35 23" resource "awsrdsclusterinstance" "clusterinstances" { count = 2 identifier = "aurora-cluster-demo-${count.index}" clusteridentifier = awsrds_cluster.default.id instance_class = "db.r4.large" engine = awsrdscluster.default.engine engineversion = awsrdscluster.default.engineversion publicly_accessible = false } resource "awsrdscluster" "default" { cluster_identifier = "aurora-cluster-demo" engine = "aurora-mysql" engineversion = "5.7.mysqlaurora.2.03.2" availability_zones = ["us-west-2a", "us-west-2b", "us-west-2c"] database_name = "mydb" master_username = "foo" master_password = "bar" backupretentionperiod = 5 preferredbackupwindow = "07:00-09:00" } resource "awsdbinstance" "default" { allocated_storage = 10 db_name = "mydb" engine = "mysql" engine_version = "5.7" instance_class = "db.t3.micro" username = "foo" password = "foobarbaz" parametergroupname = "default.mysql5.7" skipfinalsnapshot = true } resource "awsdbinstance" "sample3" { allocated_storage = 10 db_name = "mydb" engine_version = "5.7" instance_class = "db.t3.micro" username = "foo" password = "foobarbaz" parametergroupname = "default.mysql5.7" replicatesourcedb = awsdbinstance.default.id skipfinalsnapshot = true } ``` ```tf title="Negative test num. 1 - tf file" module "kafka" { source = "cloudposse/msk-apache-kafka-cluster/aws" version = "0.7.2" namespace = "eg" stage = "prod" name = "app" vpc_id = "vpc-XXXXXXXX" zone_id = "Z14EN2YD427LRQ" security_groups = ["sg-XXXXXXXXX", "sg-YYYYYYYY"] subnet_ids = ["subnet-XXXXXXXXX", "subnet-YYYYYYYY"] kafka_version = "2.4.1" numberofbrokernodes = 2 # this has to be a multiple of the # of subnetids brokerinstancetype = "kafka.m5.large" } ```
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: split.md

Split transform plugin Split a field to more than one field. | name | type | required | default value | ||--|-|| | separator | string | yes | | | split_field | string | yes | | | output_fields | array | yes | | The list of fields that need to be kept. Fields not in the list will be deleted The field to be split The result fields after split Transform plugin common parameters, please refer to for details The data read from source is a table like this: | name | age | card | |-|--|| | Joy Ding | 20 | 123 | | May Ding | 20 | 123 | | Kin Dom | 20 | 123 | | Joy Dom | 20 | 123 | We want split `name` field to `first_name` and `second name`, we can add `Split` transform like this ``` transform { Split { sourcetablename = "fake" resulttablename = "fake1" separator = " " split_field = "name" outputfields = [firstname, second_name] } } ``` Then the data in result table `fake1` will like this | name | age | card | firstname | lastname | |-|--|||--| | Joy Ding | 20 | 123 | Joy | Ding | | May Ding | 20 | 123 | May | Ding | | Kin Dom | 20 | 123 | Kin | Dom | | Joy Dom | 20 | 123 | Joy | Dom | Add Split Transform Connector