cwielenb/CNCF-Dataset huggingface dataset:
Project: Checkov (Provisioning / Security & Compliance)
File: GitLab SAST.md

layout: default published: true title: GitLab SAST nav_order: 20 GitLab SAST output adds the possibility to directly integrate with the Security tab and Merge Requests in GitLab. A typical output looks like this ```json { "schema": "https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/raw/v15.0.4/dist/sast-report-format.json", "version": "15.0.4", "scan": { "start_time": "2023-01-23T22:45:33", "end_time": "2023-01-23T22:45:33", "analyzer": { "id": "checkov", "name": "Checkov", "url": "https://www.checkov.io/", "vendor": { "name": "Prisma Cloud" }, "version": "2.2.281" }, "scanner": { "id": "checkov", "name": "Checkov", "url": "https://www.checkov.io/", "vendor": { "name": "Prisma Cloud" }, "version": "2.2.281" }, "status": "success", "type": "sast" }, "vulnerabilities": [ { "id": "605d1ad8-da1e-4784-859a-199708846fee", "identifiers": [ { "name": "CKVAWS18", "type": "checkov", "url": "https://docs.prismacloud.io/en/enterprise-edition/policy-reference/aws-policies/s3-policies/s3_13-enable-logging", "value": "CKVAWS18" } ], "links": [ { "url": "https://docs.prismacloud.io/en/enterprise-edition/policy-reference/aws-policies/s3-policies/s3_13-enable-logging" } ], "location": { "file": "main.tf", "start_line": 1, "end_line": 8 }, "name": "Ensure the S3 bucket has access logging enabled", "description": "Further info can be found None", "severity": "Unknown", "solution": "Further info can be found None" }, { "id": "1fe876c4-db57-4785-867e-ab1415250382", "identifiers": [ { "name": "CKV2AWS6", "type": "checkov", "url": "https://docs.prismacloud.io/en/enterprise-edition/policy-reference/aws-policies/s3-policies/s3-bucket-should-have-public-access-blocks-defaults-to-false-if-the-public-access-block-is-not-attached", "value": "CKV2AWS6" } ], "links": [ { "url": "https://docs.prismacloud.io/en/enterprise-edition/policy-reference/aws-policies/s3-policies/s3-bucket-should-have-public-access-blocks-defaults-to-false-if-the-public-access-block-is-not-attached" } ], "location": { "file": "main.tf", "start_line": 1, "end_line": 8 }, "name": "Ensure that S3 bucket has a Public Access block", "description": "Further info can be found None", "severity": "Unknown", "solution": "Further info can be found None" } ] } ``` The output can be created via the output flag ```shell checkov -d . -o gitlab_sast ``` Further information on the different elements and attributes can be found .
Project: YDB (App Definition and Development / Database)
File: THANKS.md

Many people have contributed to OpenJPEG by reporting problems, suggesting various improvements, or submitting actual code. Here is a list of these people. Help me keep it complete and exempt of errors. Giuseppe Baruffa Ben Boeckel Aaron Boxer David Burken Matthieu Darbois Rex Dieter Herve Drolon Antonin Descampe Francois-Olivier Devaux Parvatha Elangovan Jerme Fimes Bob Friesenhahn Kaori Hagihara Luc Hermitte Luis Ibanez David Janssens Hans Johnson Callum Lerwick Ke Liu (Tencent's Xuanwu LAB) Sebastien Lugan Benoit Macq Mathieu Malaterre Julien Malik Arnaud Maye Vincent Nicolas Aleksander Nikolic (Cisco Talos) Glenn Pearson Even Rouault Dzonatas Sol Winfried Szukalski Vincent Torri Yannick Verschueren Peter Wimmer
Project: Kubescape (Provisioning / Security & Compliance)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: 'feature' assignees: '' <!-- A brief overview of the related current state --> <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] --> <!-- A clear and concise description of what you want to happen. --> <!-- A clear and concise description of any alternative solutions or features you've considered. --> <!-- Add any other context or screenshots about the feature request here. -->
Project: Anchore (Provisioning / Security & Compliance)
File: DEVELOPING.md

There are a couple ways to run functional tests: A docker-compose setup (the same as used in CI) Locally against your own installation Modify the `tests/functional/local.env` file to meet your needs `source tests/functional/local.env` `make setup-and-test-functional-grype` or `make setup-and-test-functional-legacy` to standup engine and run the functional tests. Modify the `tests/functional/local.env` file to meet your needs `source tests/functional/local.env` `tox tests/functional`
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.1.1.1.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Add ability for safemode to wait for a minimum number of live datanodes | Major | scripts | Todd Lipcon | Todd Lipcon | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | prevent data loss when a cluster suffers a power loss | Major | datanode, hdfs-client, namenode | dhruba borthakur | dhruba borthakur | | | ant package target should not depend on cn-docs | Major | build | Tsz Wo Nicholas Sze | Tsz Wo Nicholas Sze | | | Backport HDFS-1031 to branch-1: to list a few of the corrupted files in WebUI | Major | . | Jing Zhao | Jing Zhao | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | TestDFSClientRetries#testNamenodeRestart failed | Major | . | Eli Collins | Tsz Wo Nicholas Sze | | | Namenode deadlock in branch-1 | Major | namenode | Tsz Wo Nicholas Sze | Brandon Li | | | Backport HDFS-173 to Branch-1 : Recursively deleting a directory with millions of files makes NameNode unresponsive for other commands until the deletion completes | Major | namenode | Uma Maheswara Rao G | Uma Maheswara Rao G | | | Namenode is not coming out of safemode when we perform ( NN crash + restart ) . Also FSCK report shows blocks missed. | Critical | namenode | Uma Maheswara Rao G | Uma Maheswara Rao G | | | Incorrect version numbers in hadoop-core POM | Minor | . | Matthias Friedrich | Matthias Friedrich | | | uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on | Major | . | Arpit Gupta | Arpit Gupta | | | uppercase namenode host name causes fsck to fail when useKsslAuth is on | Major | . | Arpit Gupta | Arpit Gupta | | | Remove unnecessary bogus exception log from Configuration | Minor | . | Jing Zhao | Jing Zhao | | | hadoop namenode & datanode entry points should return negative exit code on bad arguments | Minor | namenode | Steve Loughran | | | | NLineInputFormat skips first line of last InputSplit | Blocker | client | Mark Fuhs | Mark Fuhs | | | HDFS keeps a thread open for every file writer | Major | hdfs-client | Suresh Srinivas | Tsz Wo Nicholas Sze | | | Killing multiple attempts of a task taker longer as more attempts are killed | Major | . | Arpit Gupta | Arpit Gupta | | | fix hadoop-client-pom-template.xml and hadoop-client-pom-template.xml for version | Major | build | Giridharan Kesavan | Giridharan Kesavan | | | the SPNEGO user for secondary namenode should use the web keytab | Major | . | Arpit Gupta | Arpit Gupta | | | Unit Test TestJobTrackerRestartWithLostTracker fails with ant-1.8.4 | Major | test | Amir Sanjar | Amir Sanjar | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Log newly allocated blocks | Major | ha, namenode | dhruba borthakur | Todd Lipcon |
Project: KICS (Provisioning / Security & Compliance)
File: 6d2e0790-cc3d-4c74-b973-d4e8b09f4455.md

title: Global Schema Definition Not Being Used hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6d2e0790-cc3d-4c74-b973-d4e8b09f4455 Query name: Global Schema Definition Not Being Used Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Best Practices URL: All global schemas definitions should be in use<br> ```json title="Positive test num. 1 - json file" hl_lines="44" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "parameters": [ { "name": "category", "in": "body", "description": "max records to return", "required": true, "schema": { "$ref": "#/definitions/Category" } } ] } } }, "definitions": { "Category": { "type": "object", "properties": { "id": { "type": "integer", "format": "int64" }, "name": { "type": "string" } } }, "Tag": { "type": "object", "properties": { "id": { "type": "integer", "format": "int64" }, "name": { "type": "string" } } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="29" swagger: "2.0" info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response parameters: name: category in: body description: max records to return required: true schema: $ref: "#/definitions/Category" definitions: Category: type: object properties: id: type: integer format: int64 name: type: string Tag: type: object properties: id: type: integer format: int64 name: type: string ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "parameters": [ { "name": "category", "in": "body", "description": "max records to return", "required": true, "schema": { "$ref": "#/definitions/Category" } } ] } } }, "definitions": { "Category": { "type": "object", "properties": { "id": { "type": "integer", "format": "int64" }, "name": { "type": "string" } } } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: "2.0" info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response parameters: name: category in: body description: max records to return required: true schema: $ref: "#/definitions/Category" definitions: Category: type: object properties: id: type: integer format: int64 name: type: string ```
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: lagoon-backups.md

Lagoon uses the K8up backup operator: . Lagoon isnt tightly integrated with K8up, its more that Lagoon can create its resources in a way that K8up can automatically discover and backup. Lagoon has been extensively tested with K8up 1.x, but is not compatible with 2.x yet. We recommend using the 1.1.0 chart version (App version v1.2.0). Create new AWS User with policies: ```json title="example K8up IAM user" { "Version":"2012-10-17", "Statement":[ { "Sid":"VisualEditor0", "Effect":"Allow", "Action":[ "s3:ListAllMyBuckets", "s3:CreateBucket", "s3:GetBucketLocation" ], "Resource":"*" }, { "Sid":"VisualEditor1", "Effect":"Allow", "Action":"s3:ListBucket", "Resource":"arn:aws:s3:::baas-*" }, { "Sid":"VisualEditor2", "Effect":"Allow", "Action":[ "s3:PutObject", "s3:GetObject", "s3:AbortMultipartUpload", "s3:DeleteObject", "s3:ListMultipartUploadParts" ], "Resource":"arn:aws:s3:::baas-/" } ] } ``` Create `k8up-values.yml` (customize for your provider): ```yaml title="k8up-values.yml" k8up: envVars: name: BACKUP_GLOBALS3ENDPOINT value: 'https://s3.eu-west-1.amazonaws.com' name: BACKUP_GLOBALS3BUCKET value: '' name: BACKUP_GLOBALKEEPJOBS value: '1' name: BACKUP_GLOBALSTATSURL value: 'https://backup.lagoon.example.com' name: BACKUP_GLOBALACCESSKEYID value: '' name: BACKUP_GLOBALSECRETACCESSKEY value: '' name: BACKUP_BACKOFFLIMIT value: '2' name: BACKUP_GLOBALRESTORES3BUCKET value: '' name: BACKUP_GLOBALRESTORES3ENDPOINT value: 'https://s3.eu-west-1.amazonaws.com' name: BACKUP_GLOBALRESTORES3ACCESSKEYID value: '' name: BACKUP_GLOBALRESTORES3SECRETACCESSKEY value: '' timezone: Europe/Zurich ``` Install K8up: ```bash title="Install K8up Step 1" helm repo add appuio https://charts.appuio.ch ``` ```bash title="Install K8up Step 2" kubectl apply -f https://github.com/vshn/k8up/releases/download/v1.2.0/k8up-crd.yaml ``` ```bash title="Install K8up Step 3" helm upgrade --install --create-namespace \ --namespace k8up \ -f k8up-values.yaml \ --version 1.1.0 \ k8up appuio/k8up ``` Update `lagoon-core-values.yml`: ```yaml title="lagoon-core-values.yml" s3BAASAccessKeyID: <<Access Key ID for restore bucket>> s3BAASSecretAccessKey: <<Access Key Secret for restore bucket>> ``` Redeploy `lagoon-core`.
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: container-resources.md

can be customized for all the types of vertices. For configuring container resources on pods not owned by a vertex, see . To specify `resources` for the `numa` container of vertex pods: ```yaml apiVersion: numaflow.numaproj.io/v1alpha1 kind: Pipeline metadata: name: my-pipeline spec: vertices: name: my-vertex containerTemplate: resources: limits: cpu: "3" memory: 6Gi requests: cpu: "1" memory: 4Gi ``` To specify `resources` for `udf` container of vertex pods: ```yaml apiVersion: numaflow.numaproj.io/v1alpha1 kind: Pipeline metadata: name: my-pipeline spec: vertices: name: my-vertex udf: container: resources: limits: cpu: "3" memory: 6Gi requests: cpu: "1" memory: 4Gi ``` To specify `resources` for `udsink` container of vertex pods: ```yaml apiVersion: numaflow.numaproj.io/v1alpha1 kind: Pipeline metadata: name: my-pipeline spec: vertices: name: my-vertex sink: udsink: container: resources: limits: cpu: "3" memory: 6Gi requests: cpu: "1" memory: 4Gi ``` To specify `resources` for the `init` init-container of vertex pods: ```yaml apiVersion: numaflow.numaproj.io/v1alpha1 kind: Pipeline metadata: name: my-pipeline spec: vertices: name: my-vertex initContainerTemplate: resources: limits: cpu: "3" memory: 6Gi requests: cpu: "1" memory: 4Gi ``` Container resources for are instead specified at `.spec.vertices[].initContainers[].resources`.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_clusterversion_set-default.md

title: kbcli clusterversion set-default Set the clusterversion to the default clusterversion for its clusterdefinition. ``` kbcli clusterversion set-default NAME [flags] ``` ``` kbcli clusterversion set-default ac-mysql-8.0.30 ``` ``` -h, --help help for set-default ``` ``` --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 ``` - ClusterVersion command.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-system-connection-list.1.md

% podman-system-connection-list 1 podman\-system\-connection\-list - List the destination for the Podman service(s) podman system connection list [options] podman system connection ls [options] List ssh destination(s) for podman service(s). Change the default output format. This can be of a supported type like 'json' or a Go template. Valid placeholders for the Go template listed below: | Placeholder | Description | | | -- | | .Default | Indicates whether connection is the default | | .Identity | Path to file containing SSH identity | | .Name | Connection Name/Identifier | | .ReadWrite | Indicates if this connection can be modified using the system connection commands | | .URI | URI to podman service. Valid schemes are ssh://[user@]host[:port]Unix domain socket[?secure=True], unix://Unix domain socket, and tcp://localhost[:port] | Only show connection names List system connections: ``` $ podman system connection list Name URI Identity Default ReadWrite deva ssh://root@example.com:/run/podman/podman.sock ~/.ssh/id_rsa true true devb ssh://user@example.com:/run/user/1000/podman/podman.sock ~/.ssh/id_rsa false true ``` , , July 2020, Originally compiled by Jhon Honce (jhonce at redhat dot com)
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_zones.md

+++ title = "googlecomputezones resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputezones" identifier = "inspec/resources/gcp/googlecomputezones.md googlecomputezones resource" parent = "inspec/resources/gcp" +++ A `googlecomputezones` is used to test a Google Zone resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ``` googlecomputezones(project: 'chef-gcp-inspec').zonenames.each do |zonename| describe googlecomputezone(project: 'chef-gcp-inspec', name: zone_name) do it { should exist } it { should be_up } end end ``` describe googlecomputezones(project: 'chef-inspec-gcp') do its('count') { should be <= 100} end describe googlecomputezones(project: 'chef-inspec-gcp') do its('zone_ids.count') { should cmp 9 } end describe googlecomputezones(project: 'chef-inspec-gcp') do its('zone_names') { should include "us-east1-b" } end describe googlecomputezones(project: 'chef-inspec-gcp') do its('zonestatuses') { shouldnot include "DOWN" } end googlecomputezones(project: 'chef-inspec-gcp').where(zonename: /^us/).zonenames.each do |zone_name| describe googlecomputezone(project: 'chef-inspec-gcp', zone: zone_name) do it { should exist } its('status') { should eq 'UP' } end end Properties that can be accessed from the `googlecomputezones` resource: See the resource for more information. `creation_timestamps` : an array of `googlecomputezone` creation_timestamp `deprecateds` : an array of `googlecomputezone` deprecated `descriptions` : an array of `googlecomputezone` description `zone_ids` : an array of `googlecomputezone` id `zone_names` : an array of `googlecomputezone` name `regions` : an array of `googlecomputezone` region `zone_statuses` : an array of `googlecomputezone` status `availablecpuplatforms` : an array of `googlecomputezone` availablecpuplatforms This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: YugabyteDB (App Definition and Development / Database)
File: dml_close.md

title: CLOSE statement [YSQL] headerTitle: CLOSE linkTitle: CLOSE description: Use the CLOSE statement to 'drop' a cursor. menu: v2.18: identifier: dml_close parent: statements type: docs {{< warning title="YSQL currently supports only fetching rows from a cursor consecutively in the forward direction." >}} See the subsection in the generic section . {{< /warning >}} Use the `CLOSE` statement to "drop" a . The `CLOSE` statement is used jointly with the , , and statements. {{%ebnf%}} close {{%/ebnf%}} `CLOSE` drops a cursor. Use this statement so that you can shorten the lifetime a cursortypically in order to save resources. {{< note title="CLOSE is outside the scope of rolling back to a savepoint." >}} If a cursor is closed after a savepoint to which you later roll back, the effect of `CLOSE` is not rolled backin other words the closed cursor continues no longer to exist. {{< /note >}} A cursor is identified only by an unqualified name and is visible only in the session that declares it. This determines the uniqueness scope for its name. (The name of a cursor is like that of a prepared statement in this respect.) Using the keyword `ALL` in place of the name of an extant cursor closes every extant cursor. ```plpgsql close all; start transaction; declare "Cur-One" no scroll cursor without hold for select 17 as v; declare "Cur-Two" no scroll cursor with hold for select 42 as v; select name, isholdable::text, isscrollable::text from pg_cursors order by name; close "Cur-One"; commit; select name, isholdable::text, isscrollable::text from pg_cursors order by name; fetch all from "Cur-Two"; ``` This is the result from the first pgcursors_ query: ```output name | isholdable | isscrollable +-+ Cur-One | false | false Cur-Two | true | false ``` This is the result from the second pgcursors_ query: ```output name | isholdable | isscrollable +-+ Cur-Two | true | false ``` And this is the result from fetch all from "Cur-Two": ```output v 42 ```
Project: KICS (Provisioning / Security & Compliance)
File: 29f35127-98e6-43af-8ec1-201b79f99604.md

title: Admin User Enabled For Container Registry hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 29f35127-98e6-43af-8ec1-201b79f99604 Query name: Admin User Enabled For Container Registry Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Admin user is enabled for Container Registry<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="17 7" name: Create an azure container registry azure.azcollection.azurermcontainerregistry: name: myRegistry location: eastus resource_group: myResourceGroup adminuserenabled: true sku: Premium tags: Release: beta1 Environment: Production name: Create an azure container registry2 azure.azcollection.azurermcontainerregistry: name: myRegistry location: eastus resource_group: myResourceGroup adminuserenabled: "true" sku: Premium tags: Release: beta1 Environment: Production ``` ```yaml title="Negative test num. 1 - yaml file" name: Create an azure container registry azure.azcollection.azurermcontainerregistry: name: myRegistry location: eastus resource_group: myResourceGroup adminuserenabled: false sku: Premium tags: Release: beta1 Environment: Production name: Create an azure container registry2 azure.azcollection.azurermcontainerregistry: name: myRegistry location: eastus resource_group: myResourceGroup adminuserenabled: false sku: Premium tags: Release: beta1 Environment: Production ```