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

title: DROP FUNCTION statement [YSQL] headerTitle: DROP FUNCTION linkTitle: DROP FUNCTION description: Remove a function from a database. menu: v2.18: identifier: ddldropfunction parent: statements type: docs Use the `DROP FUNCTION` statement to remove a function from a database. {{%ebnf%}} drop_function, subprogram_signature, arg_decl {{%/ebnf%}} You must identify the to-be-dropped function by: Its name and the schema where it lives. This can be done by using its fully qualified name or by using just its bare name and letting name resolution find it in the first schema on the searchpath_ where it occurs. Notice that you don't need to (and cannot) mention the name of its owner. Its signature. The is sufficient; and this is typically used. You can use the full subprogramsignature. But you should realize that the argname and argmode for each argdecl carry no identifying information. (This is why it is not typically used when a function or procedure is to be altered or dropped.) This is explained in the section . An error will be thrown if the function does not exist unless `IF EXISTS` is used. Then a notice is issued instead. `RESTRICT` is the default and it will not drop the function if any objects depend on it. `CASCADE` will drop any objects that transitively depend on the function. ```plpgsql DROP FUNCTION IF EXISTS inc(i integer), mul(integer, integer) CASCADE; ```
Project: Meshery (Provisioning / Automation & Configuration)
File: newrelic-operator.md

layout: integration title: New Relic Operator subtitle: Collaborative and visual infrastructure as code for New Relic Operator image: /assets/img/integrations/newrelic-operator/icons/color/newrelic-operator-color.svg permalink: extensibility/integrations/newrelic-operator docURL: https://docs.meshery.io/extensibility/integrations/newrelic-operator description: integrations-category: Observability and Analysis integrations-subcategory: Observability and Analysis registrant: Artifact Hub components: name: alert-channel colorIcon: assets/img/integrations/newrelic-operator/components/alert-channel/icons/color/alert-channel-color.svg whiteIcon: assets/img/integrations/newrelic-operator/components/alert-channel/icons/white/alert-channel-white.svg description: name: alert-policy colorIcon: assets/img/integrations/newrelic-operator/components/alert-policy/icons/color/alert-policy-color.svg whiteIcon: assets/img/integrations/newrelic-operator/components/alert-policy/icons/white/alert-policy-white.svg description: name: dashboard colorIcon: assets/img/integrations/newrelic-operator/components/dashboard/icons/color/dashboard-color.svg whiteIcon: assets/img/integrations/newrelic-operator/components/dashboard/icons/white/dashboard-white.svg description: name: data colorIcon: assets/img/integrations/newrelic-operator/components/data/icons/color/data-color.svg whiteIcon: assets/img/integrations/newrelic-operator/components/data/icons/white/data-white.svg description: name: monitor colorIcon: assets/img/integrations/newrelic-operator/components/monitor/icons/color/monitor-color.svg whiteIcon: assets/img/integrations/newrelic-operator/components/monitor/icons/white/monitor-white.svg description: featureList: [ "Alert Policies and NRQL Alert Conditions", "Alert Conditions for APM, Browser and mobile", "Alert Channels" ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Chef InSpec (Provisioning / Security & Compliance)
File: install.md

+++ title = "Install Chef InSpec" draft = false gh_repo = "inspec" [menu] [menu.inspec] title = "Install" identifier = "inspec/install/install" parent = "inspec/install" weight = 20 +++ Use , an installer, script, or package manager to install Chef InSpec. To see which platforms and platform versions Chef InSpec is supported on, see the . You can install Chef InSpec using a curl script. ```bash curl https://omnitruck.chef.io/install.sh | sudo bash -s -- -P inspec ``` Download a Windows Chef InSpec package from , then double-click on the `.msi` file to launch the installer and follow the prompts. You can install Chef InSpec using the following Powershell script. ```powershell . { iwr -useb https://omnitruck.chef.io/install.ps1 } | iex; install -project inspec ``` Once you have installed Chef InSpec, run `inspec version` to verify that the installation was successful. The following curl script will install Chef InSpec for Ubuntu and Red Hat Enterprise Linux: ```bash curl https://omnitruck.chef.io/install.sh | sudo bash -s -- -P inspec ``` If you prefer, you can use a package manager to install Chef InSpec. Once you downloaded the latest relevant to your Linux-based platform, use the command for the respective package manager listed below. Replace the example file path with the file path leading to your downloaded package. For Ubuntu, use the following command to install Chef InSpec: ```bash sudo dpkg -i /path/to/inspec.deb ``` For Red Hat Enterprise Linux, use the following command to install Chef InSpec: ```bash sudo rpm -U /path-to/inspec.rpm ``` For SUSE Linux Enterprise Server, use the following command to install Chef InSpec: ```bash sudo zypper install /path-to/inspec.rpm ``` After installing Chef InSpec, you must accept the Chef EULA andstarting with Chef InSpec 6add a license key. See the to complete these tasks.
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: OpenMldb.md

OpenMldb source connector Used to read data from OpenMldb. | name | type | required | default value | |--||-|| | cluster_mode | boolean | yes | - | | sql | string | yes | - | | database | string | yes | - | | host | string | no | - | | port | int | no | - | | zk_path | string | no | - | | zk_host | string | no | - | | session_timeout | int | no | 10000 | | request_timeout | int | no | 60000 | | common-options | | no | - | OpenMldb is or not cluster mode Sql statement Database name OpenMldb host, only supported on OpenMldb single mode OpenMldb port, only supported on OpenMldb single mode Zookeeper host, only supported on OpenMldb cluster mode Zookeeper path, only supported on OpenMldb cluster mode OpenMldb session timeout(ms), default 60000 OpenMldb request timeout(ms), default 10000 Source plugin common parameters, please refer to for details ```hocon OpenMldb { host = "172.17.0.2" port = 6527 sql = "select * from demo_table1" database = "demo_db" cluster_mode = false } ```
Project: ClickHouse (App Definition and Development / Database)
File: data_skipping_indices.md

slug: /en/operations/system-tables/dataskippingindices Contains information about existing data skipping indices in all the tables. Columns: `database` () Database name. `table` () Table name. `name` () Index name. `type` () Index type. `type_full` () Index type expression from create statement. `expr` () Expression for the index calculation. `granularity` () The number of granules in the block. `datacompressedbytes` () The size of compressed data, in bytes. `datauncompressedbytes` () The size of decompressed data, in bytes. `marks_bytes` () The size of marks, in bytes. Example ```sql SELECT * FROM system.dataskippingindices LIMIT 2 FORMAT Vertical; ``` ```text Row 1: database: default table: user_actions name: clicks_idx type: minmax type_full: minmax expr: clicks granularity: 1 datacompressedbytes: 58 datauncompressedbytes: 6 marks: 48 Row 2: database: default table: users name: contactsnullidx type: minmax type_full: minmax expr: assumeNotNull(contacts_null) granularity: 1 datacompressedbytes: 58 datauncompressedbytes: 6 marks: 48 ```
Project: StarRocks (App Definition and Development / Database)
File: catalog.md

displayed_sidebar: "English" Returns the name of the current catalog. The catalog can be a StarRocks internal catalog or an external catalog that is mapped to an external data source. For more information about catalogs, see . If no catalog is selected, the StarRocks internal catalog `default_catalog` is returned. ```Haskell catalog() ``` This function does not require parameters. Returns the name of the current catalog as a string. Example 1: The current catalog is StarRocks internal catalog `default_catalog`. ```plaintext select catalog(); +--+ | CATALOG() | +--+ | default_catalog | +--+ 1 row in set (0.01 sec) ``` Example 2: The current catalog is an external catalog `hudi_catalog`. ```sql -- Switch to an external catalog. set catalog hudi_catalog; -- Return the name of the current catalog. select catalog(); +--+ | CATALOG() | +--+ | hudi_catalog | +--+ ``` : Switches to a destination catalog.
Project: KICS (Provisioning / Security & Compliance)
File: eb64f1e9-f67d-4e35-8a3c-3d6a2f9efea7.md

title: Role With Privilege Escalation By Actions 'iam:PutRolePolicy' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: eb64f1e9-f67d-4e35-8a3c-3d6a2f9efea7 Query name: Role With Privilege Escalation By Actions 'iam:PutRolePolicy' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Role with privilege escalation by actions 'iam:PutRolePolicy' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamrole" "cosmic" { name = "cosmic" } resource "awsiamrolepolicy" "testinline_policy" { name = "testinlinepolicy" role = awsiamrole.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:PutRolePolicy", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk_scorecard.md

title: "operator-sdk scorecard" Runs scorecard Has flags to configure dsl, bundle, and selector. This command takes one argument, either a bundle image or directory containing manifests and metadata. If the argument holds an image tag, it must be present remotely. ``` operator-sdk scorecard [flags] ``` ``` -c, --config string path to scorecard config file -h, --help help for scorecard --kubeconfig string kubeconfig path -L, --list Option to enable listing which tests are run -n, --namespace string namespace to run the test images in -o, --output string Output format for results. Valid values: text, json, xunit (default "text") --pod-security string option to run scorecard with legacy pod security context (default "legacy") -l, --selector string label selector to determine which tests are run -s, --service-account string Service account to use for tests (default "default") -x, --skip-cleanup Disable resource cleanup after tests are run -b, --storage-image string Storage image to be used by the Scorecard pod (default "quay.io/operator-framework/scorecard-storage@sha256:a3bfda71281393c7794cabdd39c563fb050d3020fd0b642ea164646bdd39a0e2") -t, --test-output string Test output directory. (default "test-output") -u, --untar-image string Untar image to be used by the Scorecard pod (default "quay.io/operator-framework/scorecard-untar@sha256:2e728c5e67a7f4dec0df157a322dd5671212e8ae60f69137463bd4fdfbff8747") -w, --wait-time duration seconds to wait for tests to complete. Example: 35s (default 30s) ``` ``` --plugins strings plugin keys to be used for this subcommand execution --verbose Enable verbose logging ``` -
Project: YugabyteDB (App Definition and Development / Database)
File: drop_group.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="445" height="80" viewbox="0 0 445 80"><path class="connector" d="M0 52h15m53 0h10m62 0h30m32 0h10m64 0h20m-141 0q5 0 5 5v8q0 5 5 5h116q5 0 5-5v-8q0-5 5-5m5 0h30m-5 0q-5 0-5-5v-20q0-5 5-5h35m24 0h35q5 0 5 5v20q0 5-5 5m-5 0h35"/><polygon points="0,59 5,52 0,45" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="35" width="53" height="25" rx="7"/><text class="text" x="25" y="52">DROP</text><rect class="literal" x="78" y="35" width="62" height="25" rx="7"/><text class="text" x="88" y="52">GROUP</text><rect class="literal" x="170" y="35" width="32" height="25" rx="7"/><text class="text" x="180" y="52">IF</text><rect class="literal" x="212" y="35" width="64" height="25" rx="7"/><text class="text" x="222" y="52">EXISTS</text><rect class="literal" x="356" y="5" width="24" height="25" rx="7"/><text class="text" x="366" y="22">,</text><a xlink:href="../../../syntaxresources/grammardiagrams#role-name"><rect class="rule" x="326" y="35" width="84" height="25"/><text class="text" x="336" y="52">role_name</text></a><polygon points="441,59 445,59 445,45 441,45" style="fill:black;stroke-width:0"/></svg>
Project: KICS (Provisioning / Security & Compliance)
File: 8657197e-3f87-4694-892b-8144701d83c1.md

title: Readiness Probe Is Not Configured hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8657197e-3f87-4694-892b-8144701d83c1 Query name: Readiness Probe Is Not Configured Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Availability URL: Check if Readiness Probe is not configured.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="7" resource "kubernetes_pod" "test" { metadata { name = "terraform-example" } spec { container { image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } ``` ```tf title="Negative test num. 1 - tf file" resource "kubernetes_pod" "test2" { metadata { name = "terraform-example" } spec { container { readiness_probe { initialdelayseconds = 10 } image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: support_commercial_platforms.md

| Platform | Architecture | Version | | | | | | Amazon Linux | `x86_64`, `aarch64` | `2.x` | | Debian | `x86_64`, `aarch64` (10.x only) | `9`, `10`, `11` | | macOS | `x86_64`, `aarch64` (M1 processors) | `11.x`, `12.x` | | Oracle Enterprise Linux | `x86_64`, `aarch64` (7.x / 8.x only) | `6.x`, `7.x`, `8.x` | | Red Hat Enterprise Linux | `x86_64`, `aarch64` (7.x, 8.x and 9.x only) | `7.x`, `8.x`, `9.x` | | SUSE Linux Enterprise Server | `x86_64`, `aarch64` (15.x only) | `12.x`, `15.x` | | Ubuntu | `x86_64` | `16.04`, `18.04`, `20.04` | | Windows | `x86_64` | `8.1`, `2012`, `2012 R2`, `2016`, `10` (all channels except "insider" builds), `2019`, `11`, `2022` |
Project: KICS (Provisioning / Security & Compliance)
File: 4f31dd9f-2cc3-4751-9b53-67e4af83dac0.md

title: Host Namespace is Shared hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 4f31dd9f-2cc3-4751-9b53-67e4af83dac0 Query name: Host Namespace is Shared Platform: DockerCompose Severity: <span style="color:#ff7213">Medium</span> Category: Resource Management URL: The hosts process namespace should not be shared by containers<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10" version: '3' services: servicename1: image: not/a-real-image:latest command: ["launch"] ports: "8080:8080" pid: "host" # Share Process ID Namespace ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="6" version: "2.4" services: servicename2: build: ./ restart: always pid: "host" entrypoint: node /app/directory.js volumes: "./directory:/app" ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="11" version: "3" services: app: build: app ports: "0.0.0.0:80:80" internal: build: internal pid: "host" ``` ```yaml title="Negative test num. 1 - yaml file" version: '2.1' services: servicename4: image: not/a-real-image:latest command: ["launch"] ports: "8080:8080" pid: "container:containername4" ``` ```yaml title="Negative test num. 2 - yaml file" version: '2.1' services: servicename5: image: not/a-real-image:latest command: ["launch"] ports: "8080:8080" pid: "container:servicename4" ``` ```yaml title="Negative test num. 3 - yaml file" version: '3' services: servicename3: image: not/a-real-image:latest command: ["launch"] ports: "8080:8080" ```
Project: KubeCarrier (App Definition and Development / Application Definition & Image Build)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: "[Feature] " labels: kind/feature assignees: '' Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here.
Project: Crunchy Postgres Operator (App Definition and Development / Database)
File: feature_request.md

name: Feature Request about: Help us improve PGO! Have an idea to improve PGO? We'd love to hear it! We're going to need some information from you to learn more about your feature requests. Please be sure you've done the following: [ ] Provide a concise description of your feature request. [ ] Describe your use case. Detail the problem you are trying to solve. [ ] Describe how you envision that the feature would work. [ ] Provide general information about your current PGO environment. Provide a concise description of your feature request. Describe your use case. Why do you want this feature? What problem will it solve? Why will it help you? Why will it make it easier to use PGO? Describe how the feature would work. How do you envision interfacing with it? Tell us about your environment: Please provide the following details: Platform: (`Kubernetes`, `OpenShift`, `Rancher`, `GKE`, `EKS`, `AKS` etc.) Platform Version: (e.g. `1.20.3`, `4.7.0`) PGO Image Tag: (e.g. `ubi8-5.x.y-0`) Postgres Version (e.g. `15`) Storage: (e.g. `hostpath`, `nfs`, or the name of your storage class) Number of Postgres clusters: (`XYZ`) Please provide any additional information that may be helpful.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: RELEASE.md

The `yaml` Project is released on an as-needed basis. The process is as follows: An issue is proposing a new release with a changelog since the last release All must LGTM this release An OWNER runs `git tag -s $VERSION` and inserts the changelog and pushes the tag with `git push $VERSION` The release issue is closed An announcement email is sent to `kubernetes-dev@googlegroups.com` with the subject `[ANNOUNCE] kubernetes-template-project $VERSION is released`
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-machine-info.1.md

% podman-machine-info 1 podman\-machine\-info - Display machine host info podman machine info Display information pertaining to the machine host. Rootless only, as all `podman machine` commands can be only be used with rootless Podman. Change output format to "json" or a Go template. | Placeholder | Description | | - | | | .Host ... | Host information for local machine| | .Version ... | Version of the machine | Print usage statement. Display default Podman machine info. ``` $ podman machine info Host: Arch: amd64 CurrentMachine: "" DefaultMachine: "" EventsDir: /run/user/3267/podman MachineConfigDir: /home/myusername/.config/containers/podman/machine/qemu MachineImageDir: /home/myusername/.local/share/containers/podman/machine/qemu MachineState: "" NumberOfMachines: 0 OS: linux VMType: qemu Version: APIVersion: 4.4.0 Built: 1677097848 BuiltTime: Wed Feb 22 15:30:48 2023 GitCommit: aa196c0d5c9abd5800edf9e27587c60343a26c2b-dirty GoVersion: go1.20 Os: linux OsArch: linux/amd64 Version: 4.4.0 ``` Display default Podman machine info formatted as json. ``` $ podman machine info --format json { "Host": { "Arch": "amd64", "CurrentMachine": "", "DefaultMachine": "", "EventsDir": "/run/user/3267/podman", "MachineConfigDir": "/home/myusername/.config/containers/podman/machine/qemu", "MachineImageDir": "/home/myusername/.local/share/containers/podman/machine/qemu", "MachineState": "", "NumberOfMachines": 0, "OS": "linux", "VMType": "qemu" }, "Version": { "APIVersion": "4.4.0", "Version": "4.4.0", "GoVersion": "go1.20", "GitCommit": "aa196c0d5c9abd5800edf9e27587c60343a26c2b-dirty", "BuiltTime": "Wed Feb 22 15:30:48 2023", "Built": 1677097848, "OsArch": "linux/amd64", "Os": "linux" } } ``` Display default Podman machine Host.Arch field. ``` $ podman machine info --format "{{ .Host.Arch }}" amd64 ``` , June 2022, Originally compiled by Ashley Cui <acui@redhat.com>
Project: YugabyteDB (App Definition and Development / Database)
File: anywhere-terraform.md

title: YugabyteDB Anywhere Terraform Provider headerTitle: Terraform Provider linkTitle: Terraform Provider description: Terraform Provider for YugabyteDB Anywhere. headcontent: Manage YugabyteDB Anywhere accounts and deployments using the Terraform Provider menu: stable_yugabyte-platform: parent: anywhere-automation identifier: anywhere-terraform weight: 10 type: docs Use the YugabyteDB Anywhere Terraform Provider to deploy and manage universes programmatically. Some examples of what you can accomplish using this provider include: Create and manage YBA provider configurations Deploy and manage universes Pause and resume universes Perform software upgrades Run on-demand backups and restores Resize nodes The provider documentation includes guides to help you get started. {{< sections/2-boxes >}} {{< sections/bottom-image-box title="Get Started" description="Manage YugabyteDB Anywhere using the Terraform Provider." buttonText="Provider Documentation" buttonUrl="https://registry.terraform.io/providers/yugabyte/yba/latest/docs/" >}} {{< /sections/2-boxes >}}