cwielenb/CNCF-Dataset huggingface dataset:
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-kube.1.md

% podman-kube 1 podman\-kube - Play containers, pods or volumes based on a structured input file podman kube subcommand The kube command recreates containers, pods or volumes based on the input from a structured (like YAML) file input. Containers are automatically started. Note: The kube commands in podman focus on simplifying the process of moving containers from podman to a Kubernetes environment and from a Kubernetes environment back to podman. Podman is not replicating the kubectl CLI. Once containers are deployed to a Kubernetes cluster from podman, please use `kubectl` to manage the workloads in the cluster. | Command | Man Page | Description | | - | - | -- | | apply | | Apply Kubernetes YAML based on containers, pods, or volumes to a Kubernetes cluster | | down | | Remove containers and pods based on Kubernetes YAML. | | generate | | Generate Kubernetes YAML based on containers, pods or volumes. | | play | | Create containers, pods and volumes based on Kubernetes YAML. | , , , , , , December 2018, Originally compiled by Brent Baude (bbaude at redhat dot com)
Project: Terrascan (Provisioning / Security & Compliance)
File: about.md

Terrascan is a security analyzer for infrastructure as code. Originally developed in 2017, Terrascan has evolved from a Python application specifically focused on scanning of security issues for Terraform into a Golang application with pluggable support for multiple IaC tools and technologies. The project is maintained by enables organizations to protect their cloud native infrastructure in hybrid and multi-cloud environments. It seamlessly scans infrastructure as code for misconfigurations, monitors provisioned cloud infrastructure for configuration changes that introduce posture drift, and enables reverting to a secure posture.
Project: NATS (App Definition and Development / Streaming & Messaging)
File: PULL_REQUEST_TEMPLATE.md

<!-- Please make sure to read CONTRIBUTING.md, then delete this notice and replace it with your PR description. The below sign-off certifies that the contribution is your original work and that you license the work to the project under the Apache-2.0 license. We cannot accept contributions without it. --> Signed-off-by: Your Name <your.email@example.com>
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: API-009-bidirectional-bindings.md

Accepted As we want to provide bi-directional capabilities for bindings to allow for cases such as getting a blob from a storage account, An API change is needed to account for the requested type of operation. It was decided to keep the bindings name as is. Alternative proposals were included changing bindings to connectors, but a strong case couldn't be made in favor of connectors to justify the breaking change it would cause. It was decided to keep the same YAML format for both input bindings and bi-directional bindings as it is today. After careful inspection, splitting to two types (for example, trigger bindings and bindings) would incur significant maintanace overhead for the app operator and Did not provide meaningful value. In addition, there was no feedback from community or prospecive users that input bindings and output bindings were confusing in any way. It was decided that the API url will be kept as: `http://localhost:<port>/v1.0/bindings/<name>`. The verb for the HTTP API will remain POST/PUT, and the type of operation will be part of a versioned, structured schema for bindings. This is not a breaking change. In accordance with our decision to work towards enterprise versioning, it was accepted that schemas will include a `version` field in The payload to specify which version of given component needs to be used that corresponds to the given payload. In addition, an extra field will be added to denote the type of operation that binding supports, for example: `get`, `list`, `create` etc. Bindings components will provide the means for the Dapr runtime to query for their supported capabilities and return a validaton error if the operation type is not supported.
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: PULL_REQUEST_TEMPLATE.md

<!-- IMPORTANT: Please provide enough information and context so that others can review your pull request: --> <!-- You can skip this if you're fixing a typo. --> [ ] Affected Issues have been mentioned in the Closing issues section [ ] Documentation has been written/updated [ ] PR title is ready for inclusion in changelog [ ] If your PR contains a database migation, it MUST be the latest in date order alphabetically Explain the details for making this change. What existing problem does the pull request solve? <!-- Lagoon is using GitHub's in-built automated release notes feature to create changelogs using PR titles Please ensure that this PR has a concise and descriptive title - they can be edited after merging, but not after release. --> Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such).
Project: KICS (Provisioning / Security & Compliance)
File: 7ebd323c-31b7-4e5b-b26f-de5e9e477af8.md

title: Missing Flag From Dnf Install hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7ebd323c-31b7-4e5b-b26f-de5e9e477af8 Query name: Missing Flag From Dnf Install Platform: Dockerfile Severity: <span style="color:#edd57e">Low</span> Category: Supply-Chain URL: The '-y' or '--assumeyes' flag should be added when invoking dnf install. If omitted, it can cause the command to fail during the build process, because dnf would expect manual input.<br> ```dockerfile title="Positive test num. 1 - dockerfile file" hl_lines="2 10" FROM fedora:27 RUN set -uex && \ dnf config-manager --set-enabled docker-ce-test && \ dnf install docker-ce && \ dnf clean all FROM fedora:28 RUN set -uex RUN dnf config-manager --set-enabled docker-ce-test RUN dnf in docker-ce RUN dnf clean all ``` ```dockerfile title="Positive test num. 2 - dockerfile file" hl_lines="2 10" FROM fedora:27 RUN set -uex; \ dnf config-manager --set-enabled docker-ce-test; \ dnf install docker-ce; \ dnf clean all FROM fedora:28 RUN set -uex RUN dnf config-manager --set-enabled docker-ce-test RUN dnf in docker-ce RUN dnf clean all ``` ```dockerfile title="Negative test num. 1 - dockerfile file" FROM fedora:27 RUN set -uex && \ dnf config-manager --set-enabled docker-ce-test && \ dnf install -y docker-ce && \ dnf clean all ``` ```dockerfile title="Negative test num. 2 - dockerfile file" FROM fedora:27 RUN set -uex; \ dnf config-manager --set-enabled docker-ce-test; \ dnf install -y docker-ce; \ dnf clean all ``` ```dockerfile title="Negative test num. 3 - dockerfile file" FROM fedora:27 RUN microdnf install -y \ openssl-libs-1:1.1.1k-6.el85.x8664 \ zlib-1.2.11-18.el85.x8664 \ && microdnf clean all ```
Project: KICS (Provisioning / Security & Compliance)
File: general_template.md

This page contains all queries. | Query |Platform|Severity|Category|More info| |--||||| {%- for platform in data %} {%- for sub_platform in data[platform] -%} {%- for severity in data -%} {%- for id in data[severity] %} |{{data['queryName']}}<br/><sup><sub>{{id}}</sub></sup>|{{platform -}} |<span style="color:{{colors['category'] -}} |{{data['descriptionUrl']}}">Documentation</a><br/>| {%- endfor -%} {%- endfor -%} {%- endfor -%} {%- endfor -%}
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.4.19.md

layout: release date: 2020-11-10 tag: v0.4.19 General Add meshery-kuma @Aisuko (#1854) Add the meshery-osm chart @Aisuko (#1802) Add support for linkerd in the dashboard service mesh view @utkarsh-pro (#1881) Add permission to watch the nodes @Aisuko (#1893) add shell completion command @WLun001 (#1877) Bug Fixes fix: bash script to utilise dynamic input @kushthedude (#1875) Maintenance [UI] Add e2e test for /userpreference @ramrodo (#1862) Documentation Docs: add AKS installation instructions for Meshery @kushthedude (#1871)
Project: YugabyteDB (App Definition and Development / Database)
File: extension-pgstatstatements.md

title: pgstatstatements extension headerTitle: pgstatstatements extension linkTitle: pgstatstatements description: Using the pgstatstatements extension in YugabyteDB menu: v2.18: identifier: extension-pgstatstatements parent: pg-extensions weight: 20 type: docs The module provides a means for tracking execution statistics of all SQL statements executed by a server. ```sql CREATE EXTENSION pgstatstatements; SELECT query, calls, totaltime, mintime, maxtime, meantime, stddevtime, rows FROM pgstat_statements; ``` To get the output of `pgstatstatements` in JSON format, visit `https://<yb-tserver-ip>:13000/statements` in your web browser, where `<yb-tserver-ip>` is the IP address of any YB-TServer node in your cluster. For more information on using pgstatstatements in YugabyteDB, refer to .
Project: Clair (Provisioning / Security & Compliance)
File: CHANGELOG.tpl.md

{{ if .Versions -}} <a name="unreleased"></a> {{ if .Unreleased.CommitGroups -}} {{ range .Unreleased.CommitGroups -}} {{ range .Commits -}} : {{ .Subject }} {{ if .Refs -}}{{ range .Refs }} -{{if .Action}}{{ .Action }} {{ end }} {{ end -}} {{ end -}} {{ end -}} {{ end -}} {{ end -}} {{ range .Versions }} <a name="{{ .Tag.Name }}"></a> {{ range .CommitGroups -}} {{ range .Commits -}} : {{ .Subject }} {{ if .Refs -}}{{ range .Refs }} - {{if .Action}}{{ .Action }}{{ end }} {{ end -}} {{ end -}} {{ end -}} {{ end -}} {{- if .RevertCommits -}} {{ range .RevertCommits -}} {{ .Revert.Header }} {{ end }} {{ end -}} {{- if .MergeCommits -}} {{ range .MergeCommits -}} {{ .Header }} {{ end }} {{ end -}} {{- if .NoteGroups -}} {{ range .NoteGroups -}} {{ range .Notes }} {{ .Body }} {{ end }} {{ end -}} {{ end -}} {{ end -}} {{- if .Versions }} {{ range .Versions -}} {{ if .Tag.Previous -}} {{ end -}} {{ end -}} {{ end -}} {{ end -}}
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_subnetwork_iam_binding.md

+++ title = "googlecomputesubnetworkiambinding resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputesubnetworkiambinding" identifier = "inspec/resources/gcp/googlecomputesubnetworkiambinding.md googlecomputesubnetworkiambinding resource" parent = "inspec/resources/gcp" +++ A `googlecomputesubnetworkiambinding` is used to test a Google Subnetwork Iam Bindings ```ruby describe googlecomputesubnetworkiambinding(project: "project", region: "region", name: "name", role: "roles/editor") do it { should exist } its('members') { should include 'user:testuser@example.com' } end ``` Properties that can be accessed from the `googlecomputesubnetworkiambinding` resource: `role` : Role that is assigned to members. For example, roles/viewer, roles/editor, or roles/owner. `members` : Specifies the identities requesting access for a Cloud Platform resource. Ensure the is enabled for the current project.
Project: YDB (App Definition and Development / Database)
File: rank_dense.md

Number the groups of neighboring rows in the that have the same expression value in the argument. `DENSE_RANK` numbers the groups one-by-one, and `RANK` skips `(N - 1)` values, with `N` being the number of rows in the previous group. If there is no argument, it uses the order specified in the `ORDER BY` section in the window definition. If the argument is omitted and `ORDER BY` is not specified, then all rows are considered equal to each other. {% note info %} Passing an argument to `RANK`/`DENSE_RANK` is a non-standard extension in YQL. {% endnote %} Signature ``` RANK([T])->Uint64 DENSE_RANK([T])->Uint64 ``` Examples ```yql SELECT RANK(my_column) OVER w FROM my_table WINDOW w AS (ORDER BY key); ``` ```yql SELECT RANK() OVER w FROM my_table WINDOW w AS (ORDER BY my_column);
Project: YDB (App Definition and Development / Database)
File: file_structure.md

The file structure outlined below is used to export data both to the file system and an S3-compatible object storage. When working with S3, the file path is added to the object key, and the key's prefix specifies the export directory. Each database directory has a counterpart directory in the file structure. The directory hierarchy in the file structure matches the directory hierarchy in the database. If a certain database directory includes no items (neither tables nor subdirectories), the first structure of such a directory includes one file of zero size named `empty_dir`. For each table in the database, there's a same-name directory in the file structure's directory hierarchy that includes: The `scheme.pb` file describing the table structure and parameters in the format One or more `dataXX.csv` files with the table data in `csv` format, where `XX` is the file's sequence number. The export starts with the `data00.csv` file, with a next file created whenever the current file exceeds 100MB. The format of data files is `.csv`, where each row corresponds to a record in the table (except the row with column headings). The urlencoded format is used for rows. For example, the file row for the table with the uint64 and utf8 columns that includes the number 1 and the Russian string "" (translates to English as "Hi"), would look like this: ``` 1,"%D0%9F%D1%80%D0%B8%D0%B2%D0%B5%D1%82" ``` When you export the tables created under in Getting started, the system will create the following file structure: ``` episodes data_00.csv scheme.pb seasons data_00.csv scheme.pb series data_00.csv scheme.pb ``` Contents of the `series/scheme.pb` file: ``` columns { name: "series_id" type { optional_type { item { type_id: UINT64 } } } } columns { name: "title" type { optional_type { item { type_id: UTF8 } } } } columns { name: "series_info" type { optional_type { item { type_id: UTF8 } } } } columns { name: "release_date" type { optional_type { item { type_id: UINT64 } } } } primarykey: "seriesid" storage_settings { storeexternalblobs: DISABLED } column_families { name: "default" compression: COMPRESSION_NONE } ```
Project: KICS (Provisioning / Security & Compliance)
File: d7dc9350-74bc-485b-8c85-fed22d276c43.md

title: Communication over HTTP hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d7dc9350-74bc-485b-8c85-fed22d276c43 Query name: Communication over HTTP Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Using HTTP URLs (without encryption) could lead to security vulnerabilities and risks<br> ```cfg title="Positive test num. 1 - cfg file" hl_lines="5" [galaxy] cachedir=~/.ansible/galaxycache ignore_certs=False roleskeletonignore=^.git$, ^.*/.git_keep$ server=http://galaxy.ansible.com ``` ```cfg title="Negative test num. 1 - cfg file" [galaxy] cachedir=~/.ansible/galaxycache ignore_certs=False roleskeletonignore=^.git$, ^.*/.git_keep$ server=https://galaxy.ansible.com ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: key_rsa.md

+++ title = "key_rsa resource" draft = false gh_repo = "inspec" platform = "os" [menu] [menu.inspec] title = "key_rsa" identifier = "inspec/resources/os/keyrsa.md keyrsa resource" parent = "inspec/resources/os" +++ Use the `key_rsa` Chef InSpec audit resource to test RSA public/private keypairs. This resource is mainly useful when used in conjunction with the x509_certificate resource, but it can also be used for checking RSA-based SSH keys. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.18.0 of InSpec. An `key_rsa` resource block declares a `key file` to be tested. describe key_rsa('certificate.key') do it { should be_private } it { should be_public } its('publickey') { should match "PUBLICKEY" } its('key_length') { should eq 2048 } end You can use an optional passphrase with `key_rsa` describe key_rsa('certificate.key', 'passphrase') do it { should be_private } end The `public_key` property returns the public part of the RSA key pair describe key_rsa('/etc/pki/www.example.com.key') do its('publickey') { should match "RSAPUBLIC_KEY" } end The `private_key` property returns the private key or the RSA key pair. describe key_rsa('/etc/pki/www.example.com.key') do its('privatekey') { should match "RSAPRIVATE_KEY" } end The `key_length` property allows testing the number of bits in the key pair. describe key_rsa('/etc/pki/www.example.com.key') do its('key_length') { should eq 2048 } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. To verify if a key is public use the following: describe key_rsa('/etc/pki/www.example.com.key') do it { should be_public } end This property verifies that the key includes a private key: describe key_rsa('/etc/pki/www.example.com.key') do it { should be_private } end
Project: Meshery (Provisioning / Automation & Configuration)
File: jira-service-desk-operator.md

layout: integration title: Jira Service Desk Operator subtitle: Collaborative and visual infrastructure as code for Jira Service Desk Operator image: /assets/img/integrations/jira-service-desk-operator/icons/color/jira-service-desk-operator-color.svg permalink: extensibility/integrations/jira-service-desk-operator docURL: https://docs.meshery.io/extensibility/integrations/jira-service-desk-operator description: integrations-category: Tools integrations-subcategory: Tools registrant: Artifact Hub components: name: customer colorIcon: assets/img/integrations/jira-service-desk-operator/components/customer/icons/color/customer-color.svg whiteIcon: assets/img/integrations/jira-service-desk-operator/components/customer/icons/white/customer-white.svg description: name: project colorIcon: assets/img/integrations/jira-service-desk-operator/components/project/icons/color/project-color.svg whiteIcon: assets/img/integrations/jira-service-desk-operator/components/project/icons/white/project-white.svg description: featureList: [ "Teams can track issues, manage projects, and automate workflows.", "Configure Issues - abstract away use a Jira's REST API in it's underlying layer and extend to perform other tasks that are supported via the REST API.", "Manage Projects - Manage customer and organization for projects." ] howItWorks: "Configure and customize Jira Projects and Issues" howItWorksDetails: "Automate the process of setting up the Jira Service Desk (JSD) operator configuration of alertmanager in a Kubernetes native way. " language: en list: include type: extensibility category: integrations
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.0.18.3.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Blocker | Include librecordio as part of the release* Included librecordio in release for use by xerces-c (ant -Dlibrecordio=true -Dxercescroot=\<path to the xerces-c root\>) | Major | Large number of decommission freezes the Namenode* Added a new conf property dfs.namenode.decommission.nodes.per.interval so that NameNode checks decommission status of x nodes for every y seconds, where x is the value of dfs.namenode.decommission.nodes.per.interval and y is the value of dfs.namenode.decommission.interval. | Blocker | Root cause of connection failure is being lost to code that uses it for delaying startup* WARNING: No release note provided for this change. | Minor | Fault in TestDistributedUpgrade* TestDistributedUpgrade used succeed for wrong reasons. | Blocker | Memory leak ?* fix memory leak of user/group information in fuse-dfs | Major | Datanode prints tons of log messages: Waiting for threadgroup to exit, active theads is XX* Only datanode's offerService thread shutdown the datanode to avoid deadlock; Datanode checks disk in case of failure on creating a block file. | Major | Streaming mapper never completes if the mapper does not write to stdout* This patch HADOOP-4620.patch (1) solves the hanging problem on map side with empty input and nonempty output this map task generates output properly to intermediate files similar to other map tasks. (2) solves the problem of hanging reducer with empty input to reduce task and nonempty output this reduce task doesn't generate output if input to reduce task is empty. | Blocker | RPC Server can leave a lot of direct buffers* Improve how RPC server reads and writes large buffers. Avoids soft-leak of direct buffers and excess copies in NIO layer. | Blocker | Block report times from datanodes could converge to same time.* A long (unexpected) delay at datanodes could make subsequent block reports from many datanode at the same time. | Blocker | workaround for tmp file handling on DataNodes in 0.18 (HADOOP-4663)* Revert tmp files handling on DataNodes back to 0.17. sync() introduced in 0.18 has less gaurantees. | Blocker | JavaDoc errors in 0.18.3* Fix couple of JavaDoc warnings.
Project: KICS (Provisioning / Security & Compliance)
File: 2b1836f1-dcce-416e-8e16-da8c71920633.md

title: Workload Host Port Not Specified hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2b1836f1-dcce-416e-8e16-da8c71920633 Query name: Workload Host Port Not Specified Platform: Kubernetes Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: Verifies if Kubernetes workload's host port is specified<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="24 9" apiVersion: v1 kind: Pod metadata: name: firstpod spec: containers: name: container image: nginx ports: containerPort: 80 hostIP: 10.0.0.1 hostPort: 8080 apiVersion: apps/v1 kind: Deployment metadata: name: secondpod spec: template: spec: containers: name: container2 image: nginx ports: containerPort: 81 hostIP: 10.0.0.2 hostPort: 8081 metadata: labels: app: nginx selector: matchLabels: app: nginx ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: firstpod spec: containers: name: container image: nginx ports: containerPort: 80 hostIP: 10.0.0.1 ```
Project: KOTS (App Definition and Development / Application Definition & Image Build)
File: _template.md

One to two sentences that describes the goal of this proposal. The reader should be able to tell by the title, and the opening paragraph, if this document is relevant to them. Note: The preferred style for design documents is one sentence per line. Do not wrap lines. This aids in review of the document as changes to a line are not obscured by the reflowing those changes caused. A short list of things which will be accomplished by implementing this proposal. Two things is ok. Three is pushing it. More than three goals suggests that the proposal's scope is too large. A short list of items which are: a. out of scope b. follow on items which are deliberately excluded from this proposal. One to two paragraphs of exposition to set the context for this proposal. One to two paragraphs that describe the high level changes that will be made to implement this proposal. A detailed design describing how the changes to the product should be made. The names of types, fields, interfaces, and methods should be agreed on here, not debated in code review. The same applies to changes in CRDs, YAML examples, and so on. Ideally the changes should be made in sequence so that the work required to implement this design can be done incrementally, possibly in parallel. Write a summary of how this enhancement will be tested to ensure there are no regressions in the future. If there are alternative high level or detailed designs that were not pursued they should be called out here with a brief explanation of why they were not pursued. If this proposal has an impact to the security of the product, its users, or data stored or transmitted via the product, they must be addressed here. (Thanks to vmware-tanzu/velero for this design template)