cwielenb/CNCF-Dataset huggingface dataset:
Project: ThreatMapper (Provisioning / Security & Compliance)
File: README.md

This tool populates neo4j with sensible data that mimicks production environment. Ingesting huge amount of data to neo4j may result into JavaHeap issue. To solve that, the script limits insertion up to 100k. If you need to ingest 500k, set a NUM to 5 and 5 ingestion at 100k will be performed. ``` DFCONSOLE=ip DFNEO4JPASS=pass go run ./main.go -imagenum=1000 -hostnum=1000 -containernum=1000 -vulnnum=1000 -awslambda_num=1000 ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_alert_config-smtpserver.md

title: kbcli alert config-smtpserver Set smtp server config ``` kbcli alert config-smtpserver [flags] ``` ``` kbcli alert config-smtpserver --smtp-from alert-test@apecloud.com --smtp-smarthost smtp.feishu.cn:587 --smtp-auth-username alert-test@apecloud.com --smtp-auth-password 123456abc --smtp-auth-identity alert-test@apecloud.com ``` ``` -h, --help help for config-smtpserver --smtp-auth-identity string The identity to authenticate to the smarthost. --smtp-auth-password string The password to authenticate to the smarthost. --smtp-auth-username string The username to authenticate to the smarthost. --smtp-from string The email address to send alert. --smtp-smarthost string The smtp host to send alert. ``` ``` --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 ``` - Manage alert receiver, include add, list and delete receiver.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: ppa.md

+++ title = "ppa resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "ppa" identifier = "inspec/resources/os/ppa.md ppa resource" parent = "inspec/resources/os" +++ Use the `ppa` Chef InSpec audit resource to verify the PPA repositories on Debian-based Linux distributions. The Personal Package Archives (PPAs) are software repositories designed for Ubuntu users and are easier to install than other third-party repositories. The following ppa formats are supported: `ubuntu-wine/ppa` `ppa:ubuntu-wine/ppa` `http://ppa.launchpad.net/juju/stable/ubuntu` This resource is distributed with Chef InSpec. describe ppa('PATH') do it { should exist } it { should be_enabled } end where `ppa('PATH')` represents PPA repository `exist` and `be_enabled` are a valid matchers for this resource. For a full list of available matchers, please visit our . The `exist` matcher tests if a repository exists on the system: it { should exist } The `be_enabled` matcher tests if a repository is enabled on the system: it { should be_enabled } The following example shows how to use this Chef InSpec audit resource. describe ppa('ppa:nginx/stable') do it { should exist } it { should be_enabled } end
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: regal.md

title: Regal subtitle: The Linter of Rego Language labels: category: tooling layer: shell inventors: styra blogs: https://www.styra.com/blog/guarding-the-guardrails-introducing-regal-the-rego-linter/ https://thenewstack.io/scaling-open-source-community-by-getting-closer-to-users/ code: https://github.com/StyraInc/regal videos: https://www.youtube.com/live/Xx8npd2TQJ0?feature=share&t=2567 tutorials: https://docs.styra.com/regal#try-it-out docs_features: learning-rego: note: | Regal can automatically check for common Rego mistakes as you code. Each violation is accompanied by a detailed explanation which can be a great learning tool for new Rego users. See the . go-integration: note: | Regal is built using the Go Rego API. Regal evaluates linting rules defined in Rego against the Rego AST of policy files. The is a good place to see how OPA is used in the project. policy-testing: note: | Regal is a useful step to use when testing Rego policies to ensure code is correct and free of common errors. See to get started. debugging-rego: note: | Regal can be used to debug Rego policies by identifying common mistakes. See for some example issues it can identify automatically. Regal is a linter for Rego, with the goal of making your Rego magnificent! Regal can: Identify common mistakes, bugs and inefficiencies in Rego policies, and suggest better approaches Provide advice on best practices, coding style, and tooling Allow users, teams and organizations to enforce custom rules on their policy code
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_bench_pgbench_run.md

title: kbcli bench pgbench run Run pgbench against a PostgreSQL cluster ``` kbcli bench pgbench run [flags] ``` ``` kbcli bench pgbench run pgcluster --database postgres --user xxx --password xxx kbcli bench sysbench run pgcluster --user xxx --password xxx --database xxx --clients 5 --threads 5 kbcli bench pgbench run pgcluster --database postgres --user xxx --password xxx --transactions 1000 kbcli bench pgbench run pgcluster --database postgres --user xxx --password xxx --times 1000 kbcli bench pgbench run pgcluster --database postgres --user xxx --password xxx --select ``` ``` --clients int The number of clients to use for pgbench (default 1) -h, --help help for run --select Run pgbench with select only --threads int The number of threads to use for pgbench (default 1) --time int The duration to run pgbench for --transactions int The number of transactions to run for pgbench ``` ``` --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 --database string database name --disable-compression If true, opt-out of response compression for all requests to the server --host string the host of database --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 --password string the password of database --port int the port of database --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 user of database ``` - Run pgbench against a PostgreSQL cluster
Project: Beam (App Definition and Development / Streaming & Messaging)
File: python-sdk.md

title: "Python SDK Roadmap" <!-- 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. --> The Apache Beam community voted to join to sunset Python 2 support in 2020. The Beam community will discontinue Python 2 support in 2020 and cannot guarantee long-term functional support or maintenance of Beam on Python 2. To ensure minimal disruption to your service, we strongly recommend that you upgrade to Python 3 as soon as possible. Apache Beam 2.14.0 and higher support Python 3.5, 3.6, and 3.7. We're continuing to the experience for Python 3 users and add support for Python 3.x minor versions (): - - Contributions and feedback are welcome! If you are interested in helping, you can select an unassigned issue on the Kanban board and assign it to yourself. If you cannot assign the issue to yourself, comment on the issue. When submitting a new PR, please tag , and . To report a Python 3 related issue, create a subtask in and cc: [~altay] and [~tvalentyn] in a JIRA comment. The best way to help us identify and investigate the issue is with a minimal pipeline that reproduces the issue. You can also discuss encountered issues on user@ or dev@ mailing lists as appropriate.
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_use.md

title: "Command - devspace use" sidebar_label: devspace use Use specific config ``` ``` ``` -h, --help help for use ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --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 strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: 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) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ```
Project: CDK for Kubernetes (CDK8s) (Provisioning / Automation & Configuration)
File: feature-request.md

name: "\U0001F680 Feature Request" about: Request a new feature title: '' labels: feature-request, needs-triage assignees: '' <!--Please make sure to read the "Reporting Issues" section of the contribution guide before submitting an issue https://github.com/cdk8s-team/cdk8s/blob/master/CONTRIBUTING.md#reporting-issues --> <!-- short description of the feature you are proposing: --> <!-- why do you need this feature? --> <!-- Please include prototype/workaround/sketch/reference implementation: --> <!-- e.g. detailed explanation, stacktraces, related issues, suggestions on how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc --> [ ] :wave: I may be able to implement this feature request [ ] :warning: This feature might incur a breaking change This is a :rocket: Feature Request
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: FAQ.md

id: faqs title: TechDocs FAQ sidebar_label: FAQ description: This page answers frequently asked questions about TechDocs This page answers frequently asked questions about . TechDocs is using to build project documentation under the hood. Documentation built with the is using the MkDocs . The package is a MkDocs Plugin that works like a wrapper around multiple MkDocs plugins (e.g. ) as well as a selection of Python Markdown extensions that TechDocs supports. Not right now. We are currently using MkDocs to generate the documentation from source, so the files have to be in Markdown format. However, in the future we want to support other static site generators which will make it possible to use other file formats. The value of metadata annotation is used in the build process of TechDocs. But when is set to `'external'` in `app-config.yaml`, the value of the annotation remains unused. However the annotation should still be present in entity descriptor file (e.g. `catalog-info.yaml`) for Backstage to know that TechDocs is enabled for the entity. This is supported for TechDocs sites whose source code is hosted in either GitHub or GitLab. In order to add "edit this page" and "leave feedback" buttons on a TechDocs page, be sure that you have `repourl` and `edituri` values in your `mkdocs.yml` files per . If the host name of your source code hosting URL does not include `github` or `gitlab`, an `integrations` entry in your `app-config.yaml` pointed at your source code provider is also needed (only the `host` key is necessary).
Project: StarRocks (App Definition and Development / Database)
File: percentile_approx.md

displayed_sidebar: "English" Returns the approximation of the pth percentile, where the value of p is between 0 and 1. Compression parameter is optional and has a setting range of [2048, 10000]. The larger the value, the higher the accuracy, the larger the memory consumption, and the longer the calculation time. If it is not specified or not beyond the range of [2048, 10000], the function runs with a default compression parameter of 10000. This function uses fixed size memory, so less memory can be used for columns with high cardinality, and can be used to calculate statistics such as tp99. ```Haskell PERCENTILE_APPROX(expr, DOUBLE p[, DOUBLE compression]) ``` ```plain text MySQL > select `table`, percentileapprox(costtime,0.99) from log_statis group by `table`; +-+--+ | table | percentileapprox(`costtime`, 0.99) | +-+--+ | test | 54.22 | +-+--+ MySQL > select `table`, percentileapprox(costtime,0.99, 4096) from log_statis group by `table`; +-+-+ | table | percentileapprox(`costtime`, 0.99, 4096.0) | +-+-+ | test | 54.21 | +-+-+ ``` PERCENTILE_APPROX,PERCENTILE,APPROX
Project: Checkov (Provisioning / Security & Compliance)
File: graph_issue.md

name: Graph Issue about: Create an issue regarding the graph creation and querying title: '' labels: 'graph' assignees: '' Describe the issue Please explain what is missing or malfunctioning in the graph (creation or querying). Also detail what is the expected behavior for this use case. Examples Please share an example code sample (in the IaC of your choice) + the expected outcomes. Desktop (please complete the following information): OS: [e.g. iOS] Checkov Version [e.g. 22] Additional context Add any other context about the problem here (e.g. code snippets).
Project: SuperEdge (Provisioning / Automation & Configuration)
File: CHANGELOG-0.7.md

* * * Support NodeUnit and Nodegroup CRD to manage edge site resources. ( ) Nodeunit add setnode attribute and nodeunit label to node. ( ) Add default apply NodeUnit and NodeGroup crd and default nodeunit. ( ) support nodegroup autofindnodekeys to automatically create nodeunits in batches ( ) Support an edge applications can be updated when the cloud edge network is disconnected. ( ) Tunnel supports apiserver EgressSelector feature. ( ) Edge-health supports user-defined edge node health check plugins. ( ) Add Superedge support k8s v1.20.6 ( ) Support containerd runtime install in edgeadm. ( ) Support adding edge nodes and native K8s nodes to SuperEdge edge clusters. ( ) Lite-apiserver supports specifying multiple network interfaces to establish connections with the cloud. ( ) Lite-apiserver support use pebble as storage. ( ) Lite-apiserver support pprof debugging. ( ) Add SuperEdge unit test e2e test.( ) FIX wrapper for different k8s version about EndpointSlice ( ) FIX: keep annotations when application-grid-controller create service from servicegrid. ( ) FIx: edgeadm init and join with --enable-edge, and node label mistaken. ( ) FIX redefined log_dir panic. ( ) FIX: Setfilecontent func in init-node.sh. ( ) Support nodeunit and Nodegroup CRD to manage edge site resources. ( ) Tunnel supports apiserver EgressSelector feature using docs. ( ) Superedge and fabedge jointly support native service mutual access and podip pass through in edge k8s clusters( ) Add Use GPU in SuperEdge ( ) Add the WasmEdge runtime to SuperEdge to run WebAssembly applications ) New outstanding contributors members of the SuperEdge community
Project: KICS (Provisioning / Security & Compliance)
File: 37304d3f-f852-40b8-ae3f-725e87a7cedf.md

title: EKS cluster logging is not enabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 37304d3f-f852-40b8-ae3f-725e87a7cedf Query name: EKS cluster logging is not enabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Amazon EKS control plane logging is not enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="6" variable "cluster_name" { default = "example" type = string } resource "awsekscluster" "positive1" { dependson = [awscloudwatchloggroup.example] name = var.cluster_name } ``` ```tf title="Negative test num. 1 - tf file" variable "cluster_name" { default = "example" type = string } resource "awsekscluster" "negative1" { dependson = [awscloudwatchloggroup.example] enabledclusterlog_types = ["api", "audit", "authenticator", "controllerManager", "scheduler"] name = var.cluster_name } ```
Project: ClickHouse (App Definition and Development / Database)
File: v20.8.7.15-lts.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 : Query is finished faster in case of exception. Cancel execution on remote replicas if exception happens. (). Backported in : fixes fixes fix remote query failure when using 'if' suffix aggregate function. (). Backported in : This will fix optimizereadinorder/optimizeaggregationinorder with max_threads>0 and expression in ORDER BY. (). Backported in : Fix `IN` operator over several columns and tuples with enabled `transformnullin` setting. Fixes . (). 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 : 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 : Fix bug when `ON CLUSTER` queries may hang forever for non-leader ReplicatedMergeTreeTables. ().
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: README.md

This document describes how to fetch OpenAPI data from a live kubernetes API server. The scripts used will create a clean [kind] instance for this purpose. This will remove both the Kustomization and Kubernetes schemas: ``` make nuke ``` The compiled-in schema version should maximize API availability with respect to all actively supported Kubernetes versions. For example, while 1.20, 1.21 and 1.22 are the actively supported versions, 1.21 is the best choice. This is because 1.21 introduces at least one new API and does not remove any, while 1.22 removes a large set of long-deprecated APIs that are still supported in 1.20/1.21. In the Makefile in this directory, update the `API_VERSION` to your desired version. You may need to update the version of Kind these scripts use by changing `KIND_VERSION` in the Makefile in this directory. You can find compatibility information in the . In this directory, fetch the openapi schema and generate the corresponding swagger.go for the kubernetes api: ``` make all ``` The above command will update the [OpenAPI schema] and the [Kustomization schema]. It will create a directory kubernetesapi/v1212 and store the resulting swagger.json and swagger.go files there. To avoid expensive schema lookups, some functions have precomputed results based on the schema. Unit tests ensure these are kept in sync with the schema; if these tests fail you will need to follow the suggested diff to update the precomputed results. At the top of the repository, run the tests. ``` make prow-presubmit-check >& /tmp/k.txt; echo $? ``` The exit code should be zero; if not, examine `/tmp/k.txt`. Instead of replacing the default version, you can specify a desired version as part of the make invocation: ``` rm kubernetesapi/swagger.go make kubernetesapi/swagger.go API_VERSION=v1.21.2 ``` While the above commands generate the swagger.go files, they do not make them available for use nor do they update the info field reported by `kustomize openapi info`. To make the newly fetched schema and swagger.go available: ``` rm kubernetesapi/openapiinfo.go make kubernetesapi/openapiinfo.go ``` You can also regenerate the kubernetes api schemas specifically with: ``` rm kubernetesapi/swagger.go make kubernetesapi/swagger.go ``` To fetch the schema without generating the swagger.go, you can run: ``` rm kubernetesapi/swagger.json make kubernetesapi/swagger.json ``` Note that generating the swagger.go will re-fetch the schema.