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

+++ title = "mysql_conf resource" draft = false gh_repo = "inspec" platform = "os" [menu] [menu.inspec] title = "mysql_conf" identifier = "inspec/resources/os/mysqlconf.md mysqlconf resource" parent = "inspec/resources/os" +++ Use the `mysql_conf` Chef InSpec audit resource to test the contents of the configuration file for MySQL, typically located at `/etc/mysql/my.cnf` or `/etc/my.cnf`. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `mysql_conf` resource block declares one (or more) settings in the `my.cnf` file, and then compares the setting in the configuration file to the value stated in the test: describe mysql_conf('path') do its('setting') { should eq 'value' } end describe mysql_conf do its('mysqld.port') { should cmp 3306 } end describe mysql_conf do its(['mariadb', 'max-connections']) { shouldnot benil } end where `'setting'` specifies a setting in the `my.cnf` file, such as `max_connections` when checking a setting within sections, such as `[mysqld]`, the section name must be included `('path')` is the non-default path to the `my.cnf` file `should eq 'value'` is the value that is expected This resource supports any settings listed in a `my.cnf` file as properties. For example, `max_connections`. its('max_connections') { should eq '505' } The following examples show how to use this Chef InSpec audit resource. describe mysql_conf do its('max_connections') { should eq '505' } its('maxuserconnections') { should eq '500' } end describe mysql_conf do its('slowquerylogfile') { should eq 'hostnameslow.log' } its('slowquerylog') { should eq '0' } its('logqueriesnotusingindexes') { should eq '1' } its('longquerytime') { should eq '0.5' } its('minexaminedrow_limit') { should eq '100' } end describe mysql_conf do its('port') { should eq '3306' } its('socket') { should eq '/var/run/mysqld/mysql.sock' } end describe mysql_conf do its('port') { should eq '3306' } its('socket') { should eq '/var/run/mysqld/mysql.sock' } its('maxallowedpacket') { should eq '12M' } its('defaultstorageengine') { should eq 'InnoDB' } its('charactersetserver') { should eq 'utf8' } its('collationserver') { should eq 'utf8general_ci' } its('max_connections') { should eq '505' } its('maxuserconnections') { should eq '500' } its('threadcachesize') { should eq '505' } end describe mysql_conf.params('mysqld') do its('safe-user-create') { should eq('1') } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: KICS (Provisioning / Security & Compliance)
File: 40430747-442d-450a-a34f-dc57149f4609.md

title: Google Compute Subnetwork Logging Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 40430747-442d-450a-a34f-dc57149f4609 Query name: Google Compute Subnetwork Logging Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: This query checks if logs are enabled for a Google Compute Subnetwork resource.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "googlecomputesubnetwork" "positive1" { name = "log-test-subnetwork" ipcidrrange = "10.2.0.0/16" region = "us-central1" network = googlecomputenetwork.custom-test.id } ``` ```tf title="Negative test num. 1 - tf file" resource "googlecomputesubnetwork" "negative1" { name = "log-test-subnetwork" ipcidrrange = "10.2.0.0/16" region = "us-central1" network = googlecomputenetwork.custom-test.id log_config { aggregationinterval = "INTERVAL10_MIN" flow_sampling = 0.5 metadata = "INCLUDEALLMETADATA" } } ```
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-12329.en.md

Add `broker.routing.batch_sync` configuration that enables separate process pool used to synchronize subscriptions with the global routing table in a batched manner. It's especially useful on nodes interconnected with the cluster through links with non-negligible latency, but might help in other scenarios by ensuring that the broker pool has less chance being overloaded.
Project: ShardingSphere (App Definition and Development / Database)
File: sharding-rule.en.md

+++ title = "Sharding" weight = 1 +++ Configure data source information ```sql REGISTER STORAGE UNIT ds_0 ( HOST="127.0.0.1", PORT=3306, DB="ds_1", USER="root", PASSWORD="root" ),ds_1 ( HOST="127.0.0.1", PORT=3306, DB="ds_2", USER="root", PASSWORD="root" ); ``` Create sharding rule ```sql CREATE SHARDING TABLE RULE t_order( STORAGEUNITS(ds0,ds_1), SHARDINGCOLUMN=orderid, TYPE(NAME="hash_mod",PROPERTIES("sharding-count"="4")), KEYGENERATESTRATEGY(COLUMN=order_id,TYPE(NAME="snowflake")) ); ``` Create sharding table ```sql CREATE TABLE `t_order` ( `order_id` int NOT NULL, `user_id` int NOT NULL, `status` varchar(45) DEFAULT NULL, PRIMARY KEY (`order_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 ``` Drop sharding table ```sql DROP TABLE t_order; ``` Drop sharding rule ```sql DROP SHARDING TABLE RULE t_order; ``` Unregister storage unit ```sql UNREGISTER STORAGE UNIT ds0, ds1; ``` Drop distributed database ```sql DROP DATABASE foo_db; ```
Project: KICS (Provisioning / Security & Compliance)
File: a77f4d07-c6e0-4a48-8b35-0eeb51576f4f.md

title: Always Pull Images Admission Control Plugin Not Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a77f4d07-c6e0-4a48-8b35-0eeb51576f4f Query name: Always Pull Images Admission Control Plugin Not Set Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Build Process URL: When using kube-apiserver command, the '--enable-admission-plugins' flag should have 'AlwaysPullImages' plugin and the plugin should be correctly configured in AdmissionControl Config file<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--enable-admission-plugins=AlwaysAdmit"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--enable-admission-plugins=AlwaysPullImages", "--admission-control-config-file=path/to/plugin/config/file.yaml"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver","--enable-admission-plugins=AlwaysPullImages", "--admission-control-config-file=path/to/plugin/config/file.yaml"] args: [] restartPolicy: OnFailure ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_describe-backup.md

title: kbcli cluster describe-backup Describe a backup. ``` kbcli cluster describe-backup BACKUP-NAME [flags] ``` ``` kbcli cluster describe-backup backup-default-mycluster-20230616190023 ``` ``` -h, --help help for describe-backup ``` ``` --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: qualify.md

slug: /en/sql-reference/statements/select/qualify sidebar_label: QUALIFY Allows filtering window functions results. It is similar to the clause, but the difference is that `WHERE` is performed before window functions evaluation, while `QUALIFY` is performed after it. It is possible to reference window functions results from `SELECT` clause in `QUALIFY` clause by their alias. Alternatively, `QUALIFY` clause can filter on results of additional window functions that are not returned in query results. `QUALIFY` cant be used if there are no window functions to evaluate. Use `WHERE` instead. Example: ``` sql SELECT number, COUNT() OVER (PARTITION BY number % 3) AS partition_count FROM numbers(10) QUALIFY partition_count = 4 ORDER BY number; ``` ``` text numberpartition_count 0 4 3 4 6 4 9 4 ```
Project: Trivy (Provisioning / Security & Compliance)
File: trivy_module_install.md

Install a module ``` trivy module install [flags] REPOSITORY ``` ``` -h, --help help for install ``` ``` --cache-dir string cache directory (default "/path/to/cache") -c, --config string config path (default "trivy.yaml") -d, --debug debug mode --enable-modules strings [EXPERIMENTAL] module names to enable --generate-default-config write the default config to trivy-default.yaml --insecure allow insecure server connections --module-dir string specify directory to the wasm modules that will be loaded (default "$HOME/.trivy/modules") -q, --quiet suppress progress bar and log output --timeout duration timeout (default 5m0s) -v, --version show version ``` - Manage modules
Project: Beam (App Definition and Development / Streaming & Messaging)
File: logos.md

title: "Beam Logos" aliases: /project/logos/ /material/ /contribute/logos/ <!-- 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. --> This page contains project material for the Apache Beam project. You can download containing all of the logos or download the logos individually. These can be resized easily and are suitable for print or web use. Click on the logo to download it. {{< colors/svg >}} These are available in a number of fixed sizes and are optimized for web use. {{< colors/png >}} The Apache Beam project uses predefined colors and fonts. has more information.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.0-beta-4.md

layout: release date: 2023-12-06 tag: v0.7.0-beta-4 M uzair s15/connection/by pass verification @MUzairS15 (#9577) fix registry crash @aabidsofi19 (#9582) [Connection] - Fix search and ui updates @senali-d (#9580) Connection Icon @senali-d (#9572) Bump golang.org/x/oauth2 from 0.13.0 to 0.15.0 in /scripts/component_generation @dependabot (#9523) Update meshmap.yml @MUzairS15 (#9570) Rm improper release file @theBeginner86 (#9567) Thank you to our contributors for making this release possible: @MUzairS15, @aabidsofi19, @dependabot, @leecalcote, @senali-d and @theBeginner86
Project: ArangoDB (App Definition and Development / Database)
File: implicit_exception_converting_constructor.md

+++ title = "`basic_outcome(P &&)`" description = "Implicit `exceptiontype` constructor. Available if `predicate::enableexceptionconvertingconstructor<P>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "implicit-constructors", "converting-constructors"] weight = 201 +++ Implicit `exceptiontype` constructor. Calls {{% api "void onoutcome_construction(T *, U &&) noexcept" %}} with `this` and `P`. Requires: `predicate::enableexceptionconverting_constructor<P>` is true. Complexity: Same as for `exception_type`'s copy or move constructor. Constexpr, triviality and noexcept of underlying operations is propagated.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.16.md

RabbitMQ `3.9.16` is a maintenance release in the `3.9.x` release series. Please refer to the Upgrading to 3.9 section from if upgrading from a version prior to 3.9.0. This release requires at least Erlang 23.2, and supports Erlang 24. has more details on Erlang version requirements for RabbitMQ. Release notes are kept under . Contributors are encouraged to update them together with their changes. This helps with release automation and a more consistent release schedule. Quorum queues: better forward compatibility with (currently in preview) RabbitMQ 3.10. GitHub issue: Significantly faster queue re-import from on subsequent node restarts. Initial definition import still takes the same amount of time as before. GitHub issue: Significantly faster exchange re-import from on subsequent node restarts. Initial definition import still takes the same amount of time as before. GitHub issue: RabbitMQ nodes will now filter out certain log messages related to connections, channels, and queue leader replicas receiving internal protocol messages sent to this node before a restart. These messages usually raise more questions and cause confusion than help. It is still possible to detect relevant underlying events (node or connection failures) from other log messages. GitHub issue: `rabbitmq-upgrade awaitonlinesynchronized_mirror` is now a no-op in single node clusters GitHub issue: One metric that was exposed via CLI tools and management plugin's HTTP API was not exposed via Prometheus scraping API. Contributed by @gomoripeti. GitHub issue: `osiris` upgraded from `observer-cli` was upgraded To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.16.tar.xz` instead of the source tarball produced by GitHub.
Project: GreptimeDB (App Definition and Development / Database)
File: v0.3.2.md

| | | | | | | CPU | AMD Ryzen 7 7735HS (8 core 3.2GHz) | | Memory | 32GB | | Disk | SOLIDIGM SSDPFKNU010TZ | | OS | Ubuntu 22.04.2 LTS | | Write buffer size | Ingest raterows/s | | | | | 512M | 139583.04 | | 32M | 279250.52 | | Query type | v0.3.2 write buffer 32M (ms) | v0.3.2 write buffer 512M (ms) | v0.3.1 write buffer 32M (ms) | | | | | | | cpu-max-all-1 | 921.12 | 241.23 | 553.63 | | cpu-max-all-8 | 2657.66 | 502.78 | 3308.41 | | double-groupby-1 | 28238.85 | 27367.42 | 52148.22 | | double-groupby-5 | 33094.65 | 32421.89 | 56762.37 | | double-groupby-all | 38565.89 | 38635.52 | 59596.80 | | groupby-orderby-limit | 23321.60 | 22423.55 | 53983.23 | | high-cpu-1 | 1167.04 | 254.15 | 832.41 | | high-cpu-all | 32814.08 | 29906.94 | 62853.12 | | lastpoint | 192045.05 | 153575.42 | NA | | single-groupby-1-1-1 | 63.97 | 87.35 | 92.66 | | single-groupby-1-1-12 | 666.24 | 326.98 | 781.50 | | single-groupby-1-8-1 | 225.29 | 137.97 |281.95 | | single-groupby-5-1-1 | 70.40 | 81.64 | 86.15 | | single-groupby-5-1-12 | 722.75 | 356.01 | 805.18 | | single-groupby-5-8-1 | 285.60 | 115.88 | 326.29 |
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: json-patch.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: busybox spec: components: name: busybox type: webservice properties: image: busybox cmd: ["sleep", "86400"] labels: pod-label-key: pod-label-value to-delete-label-key: to-delete-label-value traits: type: json-patch properties: operations: op: add path: "/spec/replicas" value: 3 op: replace path: "/spec/template/metadata/labels/pod-label-key" value: pod-label-modified-value op: remove path: "/spec/template/metadata/labels/to-delete-label-key" op: add path: "/spec/template/spec/containers/1" value: name: busybox-sidecar image: busybox:1.34 command: ["sleep", "864000"] ```
Project: KICS (Provisioning / Security & Compliance)
File: b4f65d13-a609-4dc1-af7c-63d2e08bffe9.md

title: Google Container Node Pool Auto Repair Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b4f65d13-a609-4dc1-af7c-63d2e08bffe9 Query name: Google Container Node Pool Auto Repair Disabled Platform: Crossplane Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Google Container Node Pool Auto Repair should be enabled. This service periodically checks for failing nodes and repairs them to ensure a smooth running state.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="27 6" apiVersion: container.gcp.crossplane.io/v1beta1 kind: NodePool metadata: name: cluster-np spec: forProvider: autoscaling: autoprovisioned: false enabled: true maxNodeCount: 5 minNodeCount: 3 clusterRef: name: eutuxia-cluster initialNodeCount: 3 config: machineType: n1-standard-1 locations: "us-central1-a" apiVersion: container.gcp.crossplane.io/v1beta1 kind: NodePool metadata: name: cluster-np spec: forProvider: management: autoRepair: false autoscaling: autoprovisioned: false enabled: true maxNodeCount: 5 minNodeCount: 3 clusterRef: name: eutuxia-cluster initialNodeCount: 3 config: machineType: n1-standard-1 locations: "us-central1-a" ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: container.gcp.crossplane.io/v1beta1 kind: NodePool metadata: name: cluster-np spec: forProvider: management: autoRepair: true autoscaling: autoprovisioned: false enabled: true maxNodeCount: 5 minNodeCount: 3 clusterRef: name: eutuxia-cluster initialNodeCount: 3 config: machineType: n1-standard-1 locations: "us-central1-a" ```
Project: Meshery (Provisioning / Automation & Configuration)
File: traefik-mesh-past-results.md

layout: past-results-layout title: Meshery-Traefik-Mesh Past Results permalink: installation/compatibility-matrix/meshery-traefik-mesh-past-results abstract: a complete compatibility matrix and project test status dashboard. language: en display-title: "false" list: exclude service-mesh: "meshery-traefik-mesh" subheading: Meshery-Traefik-Mesh
Project: YugabyteDB (App Definition and Development / Database)
File: alter_database,alter_database_option.grammar.md

```output.ebnf alter_database ::= ALTER DATABASE name [ [ WITH ] alterdatabaseoption [ ... ] | RENAME TO name | OWNER TO { new_owner | CURRENT_USER | SESSION_USER } | SET configuration_parameter { TO | = } { value | DEFAULT } | SET configuration_parameter FROM CURRENT | RESET configuration_parameter | RESET ALL ] alterdatabaseoption ::= ALLOW_CONNECTIONS allowconn | CONNECTION LIMIT connlimit | IS_TEMPLATE istemplate ```
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: README.md

This package provides a Storybook build for Backstage. See https://backstage.io/storybook/. To run the storybook locally, call `yarn storybook` in repo root. This will show the default set of stories that we publish to https://backstage.io/storybook If you want to show stories other than the default set, you can pass one or more package paths as an argument when calling storybook, for example: ```sh yarn storybook plugins/search ``` This separate storybook package exists because of dependency conflicts with `@backstage/cli`. It uses `nohoist` to avoid the conflicts, and since you can only use that in private packages it has to be separated out of `@backstage/core-components`.
Project: Kyverno (Provisioning / Security & Compliance)
File: kyverno_completion_powershell.md

Generate the autocompletion script for powershell Generate the autocompletion script for powershell. To load completions in your current shell session: kyverno completion powershell | Out-String | Invoke-Expression To load completions for every new session, add the output of the above command to your powershell profile. ``` kyverno completion powershell [flags] ``` ``` -h, --help help for powershell --no-descriptions disable completion descriptions ``` ``` --adddirheader If true, adds the file directory to the header of the log messages --alsologtostderr log to standard error as well as files (no effect when -logtostderr=true) --logbacktraceat traceLocation when logging hits line file:N, emit a stack trace (default :0) --log_dir string If non-empty, write log files in this directory (no effect when -logtostderr=true) --log_file string If non-empty, use this log file (no effect when -logtostderr=true) --logfilemax_size uint Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800) --logtostderr log to standard error instead of files (default true) --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true) --skip_headers If true, avoid header prefixes in the log messages --skiplogheaders If true, avoid headers when opening log files (no effect when -logtostderr=true) --stderrthreshold severity logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2) -v, --v Level number for the log level verbosity --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging ``` - Generate the autocompletion script for the specified shell