cwielenb/CNCF-Dataset huggingface dataset:
Project: YugabyteDB (App Definition and Development / Database)
File: cr-show-t4.md

title: crshowt4.sql linkTitle: crshowt4.sql headerTitle: crshowt4.sql description: crshowt4.sql - Part of the code kit for the "Analyzing a normal distribution" section within the YSQL window functions documentation. menu: v2.18: identifier: cr-show-t4 parent: analyzing-a-normal-distribution weight: 30 type: docs Save this script as `crshowt4.sql`. ```plpgsql -- Function to report on some useful overall measures of t4. create or replace function show_t4() returns table(t varchar) language plpgsql as $body$ declare count_star constant int not null := (select count(*) from t4); mindpscore constant numeric not null := (select min(dp_score) from t4); maxdpscore constant numeric not null := (select max(dp_score) from t4); avgdpscore constant numeric not null := (select avg(dp_score) from t4); devdpscore constant numeric not null := (select stddev(dp_score) from t4); minintscore constant numeric not null := (select min(int_score) from t4); maxintscore constant numeric not null := (select max(int_score) from t4); avgintscore constant numeric not null := (select avg(int_score) from t4); devintscore constant numeric not null := (select stddev(int_score) from t4); begin assert (minintscore = 0) and (minintscore::numeric = mindpscore) and (maxintscore = 100) and (maxintscore::numeric = maxdpscore) and ((avgintscore*100.0)/avgdpscore between 99.99 and 101.01) and ((devintscore*100.0)/devdpscore between 99.99 and 101.01) , 'unexpected'; t := rpad('count(*)', 30)|| tochar(countstar, '999999999'); return next; t := ''; return next; t := rpad('avg(%score)', 30)|| tochar(avgdp_score, '9999999.9'); return next; t := rpad('stddev(%score)', 30)|| tochar(devdp_score, '9999999.9'); return next; end; $body$; ```
Project: Apache Storm (App Definition and Development / Streaming & Messaging)
File: Installing-native-dependencies.md

layout: documentation The native dependencies are only needed on actual Storm clusters. When running Storm in local mode, Storm uses a pure Java messaging system so that you don't need to install native dependencies on your development machine. Installing ZeroMQ and JZMQ is usually straightforward. Sometimes, however, people run into issues with autoconf and get strange errors. If you run into any issues, please email the or come get help in the #storm-user room on freenode. Storm has been tested with ZeroMQ 2.1.7, and this is the recommended ZeroMQ release that you install. You can download a ZeroMQ release . Installing ZeroMQ should look something like this: ``` wget http://download.zeromq.org/zeromq-2.1.7.tar.gz tar -xzf zeromq-2.1.7.tar.gz cd zeromq-2.1.7 ./configure make sudo make install ``` JZMQ is the Java bindings for ZeroMQ. JZMQ doesn't have any releases (we're working with them on that), so there is risk of a regression if you always install from the master branch. To prevent a regression from happening, you should instead install from which is tested to work with Storm. Installing JZMQ should look something like this: ``` git clone https://github.com/nathanmarz/jzmq.git cd jzmq ./autogen.sh ./configure make sudo make install ``` To get the JZMQ build to work, you may need to do one or all of the following: Set JAVA_HOME environment variable appropriately Install Java dev package (more info for Mac OSX users) Upgrade autoconf on your machine Follow the instructions in If you run into any errors when running `./configure`, may provide a solution.
Project: YugabyteDB (App Definition and Development / Database)
File: txn_abort.md

title: ABORT statement [YSQL] headerTitle: ABORT linkTitle: ABORT description: Use the ABORT statement to roll back the current transaction and discards all updates by the transaction. menu: v2.18: identifier: txn_abort parent: statements type: docs Use the `ABORT` statement to roll back the current transaction and discards all updates by the transaction. {{%ebnf%}} abort {{%/ebnf%}} Add optional keyword has no effect. Add optional keyword has no effect. Create a sample table. ```plpgsql yugabyte=# CREATE TABLE sample(k1 int, k2 int, v1 int, v2 text, PRIMARY KEY (k1, k2)); ``` Begin a transaction and insert some rows. ```plpgsql yugabyte=# BEGIN TRANSACTION; SET TRANSACTION ISOLATION LEVEL REPEATABLE READ; ``` ```plpgsql yugabyte=# INSERT INTO sample(k1, k2, v1, v2) VALUES (1, 2.0, 3, 'a'), (1, 3.0, 4, 'b'); ``` Open the YSQL shell (`ysqlsh`) and begin another transaction to insert some more rows. ```plpgsql yugabyte=# BEGIN TRANSACTION; SET TRANSACTION ISOLATION LEVEL REPEATABLE READ; ``` ```plpgsql yugabyte=# INSERT INTO sample(k1, k2, v1, v2) VALUES (2, 2.0, 3, 'a'), (2, 3.0, 4, 'b'); ``` In each shell, check the only the rows from the current transaction are visible. First shell. ```plpgsql yugabyte=# SELECT * FROM sample; -- run in first shell ``` ``` k1 | k2 | v1 | v2 -+-+-+- 1 | 2 | 3 | a 1 | 3 | 4 | b (2 rows) ``` Second shell. ```plpgsql yugabyte=# SELECT * FROM sample; -- run in second shell ``` ``` k1 | k2 | v1 | v2 -+-+-+- 2 | 2 | 3 | a 2 | 3 | 4 | b (2 rows) ``` Commit the first transaction and abort the second one. ```plpgsql yugabyte=# COMMIT TRANSACTION; -- run in first shell. ``` Abort the current transaction (from the first shell). ```plpgsql yugabyte=# ABORT TRANSACTION; -- run second shell. ``` In each shell, check that only the rows from the committed transaction are visible. ```plpgsql yugabyte=# SELECT * FROM sample; -- run in first shell. ``` ``` k1 | k2 | v1 | v2 -+-+-+- 1 | 2 | 3 | a 1 | 3 | 4 | b (2 rows) ``` ```plpgsql yugabyte=# SELECT * FROM sample; -- run in second shell. ``` ``` k1 | k2 | v1 | v2 -+-+-+- 1 | 2 | 3 | a 1 | 3 | 4 | b (2 rows) ```
Project: SPIRE (Provisioning / Key Management)
File: plugin_server_upstreamauthority_aws_pca.md

The `aws_pca` plugin uses a certificate authority from AWS Certificate Manager (ACM) Private Certificate Authority (PCA) to sign intermediate signing certificates for SPIRE Server. The plugin accepts the following configuration options: | Configuration | Description | ||-| | region | AWS Region to use | | certificateauthorityarn | ARN of the "upstream" CA certificate | | casigningtemplate_arn | (Optional) ARN of the signing template to use for the server's CA. Defaults to a signing template for end-entity certificates only. See for possible values. | | signing_algorithm | (Optional) Signing algorithm to use for the server's CA. Defaults to the CA's default. See for possible values. | | assumerolearn | (Optional) ARN of an IAM role to assume | | endpoint | (Optional) Endpoint as hostname or fully-qualified URI that overrides the default endpoint. See for more information. | | supplementalbundlepath | (Optional) Path to a file containing PEM-encoded CA certificates that should be additionally included in the bundle. | The plugin will attempt to load AWS credentials using the default provider chain. This includes credentials from environment variables, shared credentials files, and EC2 instance roles. See for the full default credentials chain. See for more details on ACM Private Certificate Authority. Note: A Private Certificate Authority from ACM cannot have it's private key rotated and maintain the same ARN. As a result, restarting SPIRE server is currently required to change which CA from ACM is signing the intermediate CA for SPIRE. It's recommended to use a persisting key store for SPIRE so that existing intermediate signing certificates are maintained upon restart. Sample configuration: ```hcl UpstreamAuthority "aws_pca" { plugin_data { region = "us-west-2" certificateauthorityarn = "arn:aws:acm-pca:us-west-2:123456789012:certificate-authority/12ac02bc-d425-49f7-ab78-570a44972772" casigningtemplatearn = "arn:aws:acm-pca:::template/SubordinateCACertificatePathLen0/V1" signing_algorithm = "SHA256WITHECDSA" assumerolearn = "arn:aws:iam::123456789012:role/my-role" } } ``` SPIRE server requires the following policy for the IAM identity used. Note: The example provided allows access to all CAs and certificates. Resources should be specified down to limit authorized scope further. See . ```json { "Version": "2012-10-17", "Statement": [ { "Sid": "ACMPCASigning", "Effect": "Allow", "Action": [ "acm-pca:DescribeCertificateAuthority", "acm-pca:IssueCertificate", "acm-pca:GetCertificate" ], "Resource": "*" } ] } ```
Project: Vald (App Definition and Development / Database)
File: sdks.md

This page shows the introduction of the Vald SDKs. Vald provides the official SDKs as client libraries. You can use Vald SDKs to request something to Vald, e.g., `Insert`, `Update`, `Upsert`, `Search`, `Remove`, and so on. Also, Vald publishes ; you can use any languages you want, even if Vald does not provide an SDK. Here is the list of Official SDKs. If you use the client libraries provided by Vald, you can try it quickly. There are only a few steps to use like the followings: Import package Create the client Set configurations, then send a request Something you'd like to do For more information about the SDKs, please refer to each SDK's page.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_plugin_search.md

title: kbcli plugin search Search kbcli or kubectl plugins Search kbcli or kubectl plugins by keywords ``` kbcli plugin search [flags] ``` ``` kbcli plugin search keyword1 keyword2 ``` ``` -h, --help help for search --limit int Limit the number of plugin descriptions to output (default 50) ``` ``` --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 ``` - Provides utilities for interacting with plugins.
Project: KICS (Provisioning / Security & Compliance)
File: integrations_aws_codebuild.md

You can integrate KICS into your AWS CodeBuild workflows. This provides you the ability to run KICS scans to find vulnerabilities and misconfiguration checks to your infrastructure as code (IaC). Enable AWS CodeBuild to access your personal profile or GitHub organization. Create a `buildspec.yml` file on the root of your repository, for example: ```yaml version: 0.2 phases: build: commands: echo Starting Kics scan docker run -v $PWD:/path checkmarx/kics scan --no-progress --ignore-on-exit all -p /path -o /path --report-formats junit --output-name kics-report reports: kics-report: files: junit-kics-report.xml ``` After running the pipeline, you can see the logs and the reports section: <img src="https://raw.githubusercontent.com/Checkmarx/kics/master/docs/img/codebuild-report.png" width="850"> Go to report section to see reports: <img src="https://raw.githubusercontent.com/Checkmarx/kics/master/docs/img/codebuild-report-section.png" width="850"> Select the desired report to see the test cases: <img src="https://raw.githubusercontent.com/Checkmarx/kics/master/docs/img/codebuild-test-cases.png" width="850">
Project: ThreatMapper (Provisioning / Security & Compliance)
File: threatgraph.md

title: The Threat Graph The Threat Graph visualization provides an interactive view of your entire threat landscape. It presents the threats exposed on each node - vulnerabilities, secrets and compliance issues - and displays the connections between each based on live and recent network flows. | | |::| | Threat Graph | Nodes depict critical workloads and services that either have exploitable vulnerabilities or misconfigurations. Edges denote potential paths that attackers could take to access and exploit those issues, informed by real network data. The complete threat landscape is rendered as an interactive and actionable graph. The graph correlates the scan results (vulnerabilities, cloud misconfigurations, secrets) with runtime context (live network flows, security groups, live status) to contextualize and prioritize the alerts for each asset. View the Cloud or Platform nodes to gain a summary of the number of significant vulnerabilities, secret and compliance issues within each cloud or platform. Select a asset to view the instances of that asset. | | |:--:| | Threat Graph - View Assets | Select an instance of that asset type to list the issues detected against instance: | | |:--:| | Threat Graph - Investigate Compliance Issues | Select an issue to understand the full nature of the compliance deviation: | | |::| | Threat Graph - View Compliance Issue | You can quickly narrow down from potentially thousands of alerts to a refined and accurate set of issues and attack paths that you can fix. Select a runtime workload, such as a host, to list the issues detected against that asset: | | |::| | Threat Graph - Investigate Workload Issues | You can then review the issues detected against that workload. | | |::| | Threat Graph - View Vulnerabilities | If needed, you can drill down to the vulnerability specifics: | | |:-:| | Threat Graph - View Vulnerability Specifics | Once again, the Threat Graph enables you to quickly narrow down from potentially thousands of alerts to a refined and accurate set of issues and attack paths that you can fix.
Project: KubeArmor (Provisioning / Security & Compliance)
File: tmp-noexec.md

```sh root@wordpress-fb448db97-wj7n7:/var/tmp# ls /var/tmp xvzf root@wordpress-fb448db97-wj7n7:/var/tmp# /var/tmp/xvzf bash: /var/tmp/xvzf: Permission denied root@wordpress-fb448db97-wj7n7:/var/tmp# ``` ``` { "Action": "Block", "ClusterName": "d3mo", "ContainerID": "548176888fca6bb6d66633794f3d5f9d54930a9d9f43d4f05c11de821c758c0f", "ContainerImage": "docker.io/library/wordpress:4.8-apache@sha256:6216f64ab88fc51d311e38c7f69ca3f9aaba621492b4f1fa93ddf63093768845", "ContainerName": "wordpress", "Data": "syscall=SYSOPEN flags=OWRONLY|OCREAT|OEXCL|O_TRUNC", "Enforcer": "AppArmor", "HostName": "master-node", "HostPID": 30490, "HostPPID": 6119, "Labels": "app=wordpress", "Message": "Alert! Execution attempted inside /tmp", "NamespaceName": "wordpress-mysql", "Operation": "File", "Owner": { "Name": "wordpress", "Namespace": "wordpress-mysql", "Ref": "Deployment" }, "PID": 193, "PPID": 6119, "ParentProcessName": "/var/lib/rancher/k3s/data/24a53467e274f21ca27cec302d5fbd58e7176daf0a47a2c9ce032ee877e0979a/bin/containerd-shim-runc-v2", "PodName": "wordpress-fb448db97-wj7n7", "PolicyName": "ksp-block-exec-inside-tmp", "ProcessName": "/bin/bash", "Resource": "/tmp/sh-thd-2512146865", "Result": "Permission denied", "Severity": "1", "Source": "/bin/bash", "Tags": "CIS,CIS_Linux", "Timestamp": 1696492433, "Type": "MatchedPolicy", "UpdatedTime": "2023-10-05T07:53:53.259403Z", "cluster_id": "2302", "component_name": "kubearmor", "instanceGroup": "0", "instanceID": "0", "tenant_id": "167", "workload": "1" } ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: RUNNING_TESTS.md

```shell gmake tests ``` When running tests via `gmake tests`, there is no need to run the `init-etcd.sh` script as the test suite will do it for you. The test suite of this plugin ships with a that starts an `etcd` node in the background. This script can also be used to start a node for experimenting with this plugin. To run it: ```shell ./test/systemSUITEdata/init-etcd.sh [etcd data dir] [etcd client port] ``` where `[etcd data dir]` is the desired `etcd` node data directory path. The script depends on the [`daemonize` tool](https://software.clapper.org/daemonize/) for running the process in the background and pid file creation. To stop a node started this way use the pid file created by `daemonize`: ```shell pkill -INT $(cat [etcd data dir]/etcd.pid) ```
Project: KICS (Provisioning / Security & Compliance)
File: cbd2db69-0b21-4c14-8a40-7710a50571a9.md

title: Encryption Provider Config Is Not Defined hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: cbd2db69-0b21-4c14-8a40-7710a50571a9 Query name: Encryption Provider Config Is Not Defined Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: When using kube-apiserver commands, the '--encryption-provider-config' flag should be defined and the encryption should be correctly configured in Encryption Configuration 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: [] 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: ["--encryption-provider-config=/path/to/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","--encryption-provider-config=/path/to/config/file.yaml"] args: [] restartPolicy: OnFailure ```
Project: YugabyteDB (App Definition and Development / Database)
File: histogram-report.md

title: Histogram of the values in t4.dp_score linkTitle: Histogram report headerTitle: Output from running histogram() on t4.dp_score description: Output from running histogram() on t4.dp_score. menu: v2.18: identifier: histogram-report parent: normal-distribution-analysis-reports weight: 10 type: docs ``` 1 | 1 | 1 | 1 | 5 | 12 | 25 | 25 | 72 | = 109 | = 162 | == 263 | === 428 | ==== 632 | ====== 920 | ========= 1192 | ============ 1713 | ================= 2235 | ====================== 2793 | ============================ 3592 | ==================================== 4158 | ========================================== 4926 | ================================================= 5588 | ======================================================== 6236 | ============================================================== 6492 | ================================================================= 6800 | ==================================================================== 6901 | ===================================================================== 6916 | ===================================================================== 6288 | =============================================================== 5828 | ========================================================== 5195 | ==================================================== 4529 | ============================================= 3771 | ====================================== 3133 | =============================== 2590 | ========================== 1898 | =================== 1443 | ============== 1075 | =========== 691 | ======= 480 | ===== 354 | ==== 209 | == 125 | = 82 | = 65 | = 25 | 9 | 8 | 2 | 1 | ```
Project: ClickHouse (App Definition and Development / Database)
File: v20.11.4.13-stable.md

Backported in : Make it possible to connect to `clickhouse-server` secure endpoint which requires SNI. This is possible when `clickhouse-server` is hosted behind TLS proxy. (). Backported in : fixes fixes fix remote query failure when using 'if' suffix aggregate function. (). Backported in : Fix crash when using `any` without any arguments. This is for . cc @azat. (). Backported in : Abort multipart upload if no data was written to WriteBufferFromS3. (). Backported in : Prevent clickhouse server crashes when using TimeSeriesGroupSum. (). Backported in : Fix possible error `Illegal type of argument` for queries with `ORDER BY`. Fixes . (). Backported in : Install script should always create subdirs in config folders. This is only relevant for Docker build with custom config. (). Backported in : Blame info was not calculated correctly in `clickhouse-git-import`. (). Backported in : Fix possible server crash after `ALTER TABLE ... MODIFY COLUMN ... NewType` when `SELECT` have `WHERE` expression on altering column and alter doesn't finished yet. (). Backported in : Reresolve the IP of the `formatavroschemaregistryurl` in case of errors. (). Backported in : Fixed wrong result in big integers (128, 256 bit) when casting from double. (). Backported in : Avoid unnecessary network errors for remote queries which may be cancelled while execution, like queries with `LIMIT`. (). Backported in : Fixed crash on `CREATE TABLE ... AS sometable` query when `sometable` was created `AS table_function()` Fixes . (). Backported in : Fix bug when `ON CLUSTER` queries may hang forever for non-leader ReplicatedMergeTreeTables. ().
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_create_space.md

title: "Command - devspace create space" sidebar_label: devspace create space Create a new cloud space ``` devspace create space [flags] ``` ``` Creates a new space Example: devspace create space myspace ``` ``` --active Use the new Space as active Space for the current project (default true) --cluster string The cluster to create a space in -h, --help help for space --provider string The cloud provider to use ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile string The devspace profile to use (if there is any) --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```