cwielenb/CNCF-Dataset huggingface dataset:
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: form-editor.md

Monokle Desktop shows form editors for diverse Kubernetes resources which allows you to interactively change the specification of your resources using visual controls/inputs. For example in the case of a ConfigMap Kubernetes resource, clicking on the Form tab at the top of the Editor, opens the form fields editor for key ConfigMap properties, allowing you to edit/discover all available properties without having to learn or lookup the corresponding YAML/resource documentation. Any changes made and saved (with the Save button on the top right) are written back to the underlying YAML. To have insight into the changes made to your configuration, the exact properties edited with Monokles Form Editor are highlighted when you make the transition from the Form Editor tab to the Source tab. This highlighting feature identifies all changes providing full visibility of edited resources as you work toward attaining your desired state. The configuration file you are editing can be visible even when you are using templates. Click on the side-by-side icon at the top right of the editor to open a side-by-side view showing the source code on the left and the form editor on the right, providing instant visibility of the changed files while updating the state. To launch the Metadata Editor, click on the Metadata tab. For editing object metadata, you need to provide a specific name, namespace, annotations, labels, cluster name, generate name, and finalizers to uniquely identify the object. Check out for more details on how to use the Form Editor and Metadata.
Project: Flink (App Definition and Development / Streaming & Messaging)
File: select.md

title: "SELECT & WHERE" weight: 4 type: docs <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you 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. --> {{< label Batch >}} {{< label Streaming >}} The general syntax of the `SELECT` statement is: ```sql SELECT selectlist FROM tableexpression [ WHERE boolean_expression ] ``` The `table_expression` refers to any source of data. It could be an existing table, view, or `VALUES` clause, the joined results of multiple existing tables, or a subquery. Assuming that the table is available in the catalog, the following would read all rows from `Orders`. ```sql SELECT * FROM Orders ``` The `selectlist` specification `*` means the query will resolve all columns. However, usage of `*` is discouraged in production because it makes queries less robust to catalog changes. Instead, a `selectlist` can specify a subset of available columns or make calculations using said columns. For example, if `Orders` has columns named `order_id`, `price`, and `tax` you could write the following query: ```sql SELECT order_id, price + tax FROM Orders ``` Queries can also consume from inline data using the `VALUES` clause. Each tuple corresponds to one row and an alias may be provided to assign names to each column. ```sql SELECT orderid, price FROM (VALUES (1, 2.0), (2, 3.1)) AS t (orderid, price) ``` Rows can be filtered based on a `WHERE` clause. ```sql SELECT price + tax FROM Orders WHERE id = 10 ``` Additionally, built-in and can be invoked on the columns of a single row. User-defined functions must be registered in a catalog before use. ```sql SELECT PRETTYPRINT(orderid) FROM Orders ``` {{< top >}}
Project: kpt (Provisioning / Automation & Configuration)
File: 06-creating-a-package.md

Creating a new package is simple: create a new directory and [author resources]: ```shell $ mkdir awesomeapp ``` For convenience, you can use `pkg init` command to create a minimal `Kptfile` and `README` files: ```shell $ kpt pkg init awesomeapp writing Kptfile writing README.md ``` ?> Refer to the for usage. The `info` section of the `Kptfile` contains some optional package metadata you may want to set. These fields are not consumed by any functionality in kpt: ```yaml apiVersion: kpt.dev/v1 kind: Kptfile metadata: name: awesomeapp info: description: Awesomeapp solves all the world's problems in half the time. site: awesomeapp.example.com emails: jack@example.com jill@example.com license: Apache-2.0 keywords: awesome-tech world-saver ```
Project: KICS (Provisioning / Security & Compliance)
File: 41c127a9-3a85-4bc3-a333-ed374eb9c3e4.md

title: Nifcloud Computing Undefined Description To Security Group hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 41c127a9-3a85-4bc3-a333-ed374eb9c3e4 Query name: Nifcloud Computing Undefined Description To Security Group Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: Missing description for security group<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "nifcloudsecuritygroup" "positive" { group_name = "http" } ``` ```tf title="Negative test num. 1 - tf file" resource "nifcloudsecuritygroup" "negative" { group_name = "http" description = "Allow inbound HTTP traffic" } ```
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: index.md

This section covers some of the basic features and functionality in Lagoon. If you're familiar with these, move on to . If you need help, contact your Lagoon administrator or reach out to the community and maintainers in our . To run a Lagoon Project, your system must meet the requirements to run Docker. We suggest installing the latest version of Docker for your workstation. You can download Docker . We also suggest allowing Docker at least 4 CPUs and 4 GB RAM. You can choose from pygmy, Lando, or DDEV - it's up to you! Learn more about Lagoon and General: General: Drupal: Drupal: All: This is the main file that will be used by Lagoon to understand what should be deployed, as well as many other things. See . This file is used by `Docker Compose` to start your local development environment. Lagoon also uses it to understand which of the services should be deployed, which type, and how to build them. This happens via `labels`. See . Some Docker images and containers need additional customizations from the provided images. This usually has two reasons: Application code: Containers like NGINX, PHP, Node.js, etc, need the actual programming code within their images. This is done during a Docker build step, which is configured in a Dockerfile. Lagoon has full support for Docker, and therefore also allows you full control over the resulting images via Dockerfile customizations. Customization of images: Lagoon also allows you to customize the base images according to your needs. This can be to inject an additional environment variable, change a service configuration, or even install additional tools. We advise caution with installing additional tools to the Docker images, as you will need to maintain any adaptions in the future! | Type | Versions | Dockerfile | | : | : | : | | | 10.4, 10.5, 10.6, 10.11 | | | | 11, 12, 13, 14, 15 | | | | 4 | | | | openresty/1.21 | | | | 16, 18, 20 | | | | 8.0, 8.1, 8.2 | | | | 8.0, 8.1, 8.2 | | | | 3.7, 3.8, 3.9, 3.10, 3.11 | | | | 5, 6, 7 | | | | 7, 8 | | | | 5, 6, 7 | | | | 2 | | | | 3.10 | | | | 3.0, 3.1, 3.2 | | All images are pushed to . We suggest always using the latest tag \(like `uselagoon/nginx:latest`\) as they are kept up to date in terms of features and security. If you choose to use a specific Lagoon version of an image like `uselagoon/nginx:20.10.0` or `uselagoon/node-10:20.10.0` it is your own responsibility to upgrade the version of the images as soon as a new Lagoon version is released!
Project: StarRocks (App Definition and Development / Database)
File: weeks_add.md

displayed_sidebar: "English" Returns the value with the number of weeks added to date. ```Haskell DATETIME weeks_add(DATETIME expr1, INT expr2); ``` `expr1`: the original date. It must be of the `DATETIME` type. `expr2`: the number of weeks. It must be of the `INT` type. returns `DATETIME`. `NULL` is returned if the date does not exist. ```Plain select weeks_add('2022-12-20',2); +-+ | weeks_add('2022-12-20', 2) | +-+ | 2023-01-03 00:00:00 | +-+ ```
Project: KICS (Provisioning / Security & Compliance)
File: b161c11b-a59b-4431-9a29-4e19f63e6b27.md

title: REST API With Vulnerable Policy hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b161c11b-a59b-4431-9a29-4e19f63e6b27 Query name: REST API With Vulnerable Policy Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: REST API policy should avoid wildcard in 'Action' and 'Principal'<br> ```tf title="Positive test num. 1 - tf file" hl_lines="15" provider "aws" { region = "us-east-1" } resource "awsapigatewayrestapi" "api_gw" { name = "api-gw-cache-encrypted" description = "API GW test" } resource "awsapigatewayrestapi_policy" "test" { restapiid = awsapigatewayrestapi.api_gw.id policy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "AWS": "*" }, "Action": "execute-api:*", "Resource": "${awsapigatewayrestapi.api_gw.arn}" } ] } EOF } resource "awsapigatewaydeployment" "apigw_deploy" { dependson = [awsapigatewayintegration.apigwint] restapiid = awsapigatewayrestapi.api_gw.id stage_name = "dev" } resource "awsapigatewayresource" "apigw_resource" { restapiid = awsapigatewayrestapi.api_gw.id parentid = awsapigatewayrestapi.apigw.rootresourceid path_part = "mytestresource" } resource "awsapigatewaymethod" "apigw_method" { restapiid = awsapigatewayrestapi.api_gw.id resourceid = awsapigatewayresource.apigwresource.id http_method = "GET" authorization = "NONE" } resource "awsapigatewayintegration" "apigw_int" { restapiid = awsapigatewayrestapi.api_gw.id resourceid = awsapigatewayresource.apigwresource.id httpmethod = awsapigatewaymethod.apigwmethod.http_method type = "MOCK" request_templates = { "application/xml" = <<EOF { "body" : $input.json('$') } EOF } } resource "awsapigatewaystage" "apigw_stage" { stage_name = "prod" restapiid = awsapigatewayrestapi.api_gw.id deploymentid = awsapigatewaydeployment.apigwdeploy.id } resource "awsapigatewaymethodsettings" "apigwmethod_sett" { restapiid = awsapigatewayrestapi.api_gw.id stagename = awsapigatewaystage.apigwstage.stage_name methodpath = "${awsapigatewayresource.apigwresource.pathpart}/${awsapigatewaymethod.apigwmethod.http_method}" settings { logging_level = "OFF" caching_enabled = true # This is required for cache encryption cachedataencrypted = true # This is required for cache encryption } } ``` ```tf title="Negative test num. 1 - tf file" resource "awsapigatewayrestapi" "test" { name = "example-rest-api" } resource "awsapigatewayrestapi_policy" "test" { restapiid = awsapigatewayrestapi.test.id policy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "AWS": [ "arn:aws:iam::123456789012:user/test-user" ] }, "Action": "execute-api:Invoke", "Resource": "awsapigatewayrestapi.test.execution_arn", "Condition": { "IpAddress": { "aws:SourceIp": "123.123.123.123/32" } } } ] } EOF } ```
Project: OAuth2 Proxy (Provisioning / Key Management)
File: keycloak.md

id: keycloak title: Keycloak :::note This is the legacy provider for Keycloak, use if possible. ::: Create new client in your Keycloak realm with Access Type 'confidential' and Valid Redirect URIs 'https://internal.yourcompany.com/oauth2/callback' Take note of the Secret in the credential tab of the client Create a mapper with Mapper Type 'Group Membership' and Token Claim Name 'groups'. Make sure you set the following to the appropriate url: ``` --provider=keycloak --client-id=<client you have created> --client-secret=<your client's secret> --login-url="http(s)://<keycloak host>/auth/realms/<your realm>/protocol/openid-connect/auth" --redeem-url="http(s)://<keycloak host>/auth/realms/<your realm>/protocol/openid-connect/token" --profile-url="http(s)://<keycloak host>/auth/realms/<your realm>/protocol/openid-connect/userinfo" --validate-url="http(s)://<keycloak host>/auth/realms/<your realm>/protocol/openid-connect/userinfo" --keycloak-group=<firstalloweduser_group> --keycloak-group=<secondalloweduser_group> ``` For group based authorization, the optional `--keycloak-group` (legacy) or `--allowed-group` (global standard) flags can be used to specify which groups to limit access to. If these are unset but a `groups` mapper is set up above in step (3), the provider will still populate the `X-Forwarded-Groups` header to your upstream server with the `groups` data in the Keycloak userinfo endpoint response. The group management in keycloak is using a tree. If you create a group named admin in keycloak you should define the 'keycloak-group' value to /admin.
Project: Meshery (Provisioning / Automation & Configuration)
File: hexa.md

layout: integration title: Hexa subtitle: Collaborative and visual infrastructure as code for Hexa image: /assets/img/integrations/hexa/icons/color/hexa-color.svg permalink: extensibility/integrations/hexa docURL: https://docs.meshery.io/extensibility/integrations/hexa description: integrations-category: Provisioning integrations-subcategory: Security & Compliance registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] 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: Meshery (Provisioning / Automation & Configuration)
File: v0.7.3-patch.1.md

layout: release date: 2023-12-20 tag: v0.7.3-patch.1 [Relationships] Add Environment Hierarchical Parent Relationship @theBeginner86 (#9677) Add Routing To Dashboard tabs @aabidsofi19 (#9687) [UI] fix kubernetes icon @aabidsofi19 (#9690) Add Routing To Dashboard tabs @aabidsofi19 (#9687) chore(deps): Bump github.com/containerd/containerd from 1.7.6 to 1.7.11 @dependabot (#9683) [Docs] Update for each page's abstract @leecalcote (#9685) Thank you to our contributors for making this release possible: @aabidsofi19, @dependabot, @leecalcote and @theBeginner86
Project: YDB (App Definition and Development / Database)
File: scrubbing.md

Scrubbing is a process that reads data, checks its integrity, and restores it if needed. The process is run by default. The interval between completing a scrub and starting the next one is 1 month. You can change the interval using . The process checks data that was accessed before the previous scrub. Scrubbing is started and stopped for the entire {{ ydb-short-name }} cluster. Scrubbing is performed in the background without overloading the system. To set a 48-hour interval, run the command: ```bash ydb-dstool -e <bs_endpoint> cluster set --scrub-periodicity 48h ``` You can also set the maximum number of cluster disks to be scrubbed at a time. For example, to only scrub one disk at a time, run the command: ```bash ydb-dstool -e <bs_endpoint> cluster set --max-scrubbed-disks-at-once ``` To stop cluster scrubbing, run the command: ```bash ydb-dstool -e <bs_endpoint> cluster set --scrub-periodicity disable ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: name.container.md

Assign a name to the container. The operator can identify a container in three ways: UUID long identifier (f78375b1c487e03c9438c729345e54db9d20cfa2ac1fc3494b6eb60872e74778); UUID short identifier (f78375b1c487); Name (jonah). Podman generates a UUID for each container, and if a name is not assigned to the container with --name then it generates a random string name. The name can be useful as a more human-friendly way to identify containers. This works for both background and foreground containers.
Project: ArangoDB (App Definition and Development / Database)
File: on_result_in_place_construction.md

+++ title = "`static void onresultinplaceconstruction(T *, inplacetype_t<U>, Args &&...) noexcept`" description = "(>= Outcome v2.2.0) Hook invoked by the in-place constructors of `basic_result`." categories = ["observer-policies"] weight = 450 +++ One of the constructor hooks for {{% api "basicresult<T, E, NoValuePolicy>" %}}, generally invoked by the in-place constructors of `basicresult`. See each constructor's documentation to see which specific hook it invokes. Requires: Always available. Guarantees: Never throws an exception.
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_create_table_as.md

title: CREATE TABLE AS statement [YSQL] headerTitle: CREATE TABLE AS linkTitle: CREATE TABLE AS description: Use the CREATE TABLE AS statement to create a table using the output of a subquery. menu: v2.18: identifier: ddlcreatetable_as parent: statements type: docs Use the `CREATE TABLE AS` statement to create a table using the output of a subquery. {{%ebnf%}} createtableas {{%/ebnf%}} YugabyteDB may extend the syntax to allow specifying PRIMARY KEY for `CREATE TABLE AS` command. Specify the name of the table. Specify the name of a column in the new table. When not specified, column names are taken from the output column names of the query. Using this qualifier will create a temporary table. Temporary tables are visible only in the current client session or transaction in which they are created and are automatically dropped at the end of the session or transaction. Any indexes created on temporary tables are temporary as well. See the section . ```plpgsql CREATE TABLE sample(k1 int, k2 int, v1 int, v2 text, PRIMARY KEY (k1, k2)); ``` ```plpgsql INSERT INTO sample VALUES (1, 2.0, 3, 'a'), (2, 3.0, 4, 'b'), (3, 4.0, 5, 'c'); ``` ```plpgsql CREATE TABLE selective_sample AS SELECT * FROM sample WHERE k1 > 1; ``` ```plpgsql yugabyte=# SELECT * FROM selective_sample ORDER BY k1; ``` ``` k1 | k2 | v1 | v2 -+-+-+- 2 | 3 | 4 | b 3 | 4 | 5 | c (2 rows) ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_kms_key_ring_iam_policy.md

+++ title = "googlekmskeyringiam_policy resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlekmskeyringiam_policy" identifier = "inspec/resources/gcp/googlekmskeyringiampolicy.md googlekmskeyringiampolicy resource" parent = "inspec/resources/gcp" +++ A `googlekmskeyringiam_policy` is used to test a Google KeyRing Iam Policy resource ```ruby describe googlekmskeyringiampolicy(project: "project", location: "location", keyringname: "keyring_name") do it { should exist } end googlekmskeyringiampolicy(project: "project", location: "location", keyringname: "keyring_name").bindings.each do |binding| describe binding do its('role') { should eq 'roles/editor'} its('members') { should include 'user:testuser@example.com'} end end ``` Properties that can be accessed from the `googlekmskeyringiam_policy` resource: `iambindingroles` : The list of roles that exist on the policy. `bindings` : Associates a list of members to a role. `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. `audit_configs` : Specifies cloud audit logging configuration for this policy. `service` : Specifies a service that will be enabled for audit logging. For example, `storage.googleapis.com`, `cloudsql.googleapis.com`. `allServices` is a special value that covers all services. `auditlogconfigs` : The configuration for logging of each type of permission. `log_type` : The log type that this config enables. For example, ADMINREAD, DATAWRITE or DATA_READ `exempted_members` : Specifies the identities that do not cause logging for this type of permission. Ensure the is enabled for the current project.
Project: YugabyteDB (App Definition and Development / Database)
File: end-migration.md

title: End migration headcontent: yb-voyager end migration linkTitle: End migration description: YugabyteDB Voyager end migration reference menu: preview_yugabyte-voyager: identifier: end-migration-voyager parent: yb-voyager-cli weight: 100 type: docs Cleans up all the migration-related information and metadata stored in the export directory (export-dir) and databases (source, target, and source-replica). The command also provides an option to back up the schema, data, migration reports, and log files. ```text Usage: yb-voyager end migration [ <arguments> ... ] ``` The valid arguments for end migration are described in the following table: | Argument | Description/valid options | | :- | : | | --backup&#8209;data&#8209;files | Back up snapshot data files. <br>Accepted parameters: true, false, yes, no, 0, 1 | | --backup&#8209;log&#8209;files | Back up yb-voyager log files for the current migration. <br>Accepted parameters: true, false, yes, no, 0, 1 | | &#8209;&#8209;backup&#8209;schema&#8209;files | Back up migration schema files. <br>Accepted parameters: true, false, yes, no, 0, 1 | | &#8209;&#8209;save&#8209;migration&#8209;reports | Saves all the reports generated in the migration workflow (`analyze-schema` report, `export data status` output, `import data status` output, or `get data-migration-report`). <br>Accepted parameters: true, false, yes, no, 0, 1 | | -e, --export-dir | Path to the export directory. This directory is a workspace used to store exported schema DDL files, export data files, migration state, and a log file.| | --backup-dir | Directory where the schema, data, logs, and reports are backed up.<br> Note: Mandatory if any of the following flags are set to true or yes or 1: `--backup-data-files`, `--backup-log-files`, `--backup-schema-files`, `--save-migration-reports`. | | -h, --help | Command line help for end migration. | | -y, --yes | Answer yes to all prompts during the export schema operation. <br>Default: false | ```sh yb-voyager end migration --export-dir /dir/export-dir \ --backup-log-files true \ --backup-data-files true \ --backup-schema-files true \ --save-migration-reports true \ --backup-dir /dir/backup-dir ```
Project: sigstore (Provisioning / Security & Compliance)
File: oid-info.md

Sigstore maintains its own Private Enterprise Number (57264) with the Internet Assigned Numbers Authority to help identify and organize additional metadata in code signing certificates issued by Fulcio instances. This document aims to provide a simple directory of values in use with an explanation of their meaning. Note that all values begin from the root OID 1.3.6.1.4.1.57264 (registered by Sigstore)[http://oid-info.com/get/1.3.6.1.4.1.57264]. When adding additional OIDs under the root, please update the above link with the child OID. | OID | Name | Details | | - | - | - | | 1.3.6.1.4.1.57264.1 | Fulcio | https://github.com/sigstore/fulcio/blob/main/docs/oid-info.md | | 1.3.6.1.4.1.57264.2 | Timestamp Authority | https://github.com/sigstore/timestamp-authority/blob/main/docs/tsa-policy.md#52-identification | | 1.3.6.1.4.1.57264.3 | Rekor | https://github.com/sigstore/rekor |
Project: CloudNativePG (App Definition and Development / Database)
File: backup_recovery.md

Until CloudNativePG 1.20, this page used to contain both the backup and recovery phases of a PostgreSQL cluster. The reason was that CloudNativePG supported only backup and recovery object stores. Version 1.21 introduces support for the Kubernetes `VolumeSnapshot` API, providing more possibilities for the end user. As a result, and are now in two separate sections.