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

title: UUID and TIMEUUID data types [YCQL] headerTitle: UUID and TIMEUUID linkTitle: UUID and TIMEUUID summary: UUID types description: Use the UUID data type to specify columns for data of universally unique ids. TIMEUUID is a universal unique identifier variant that includes time information. menu: preview: parent: api-cassandra weight: 1460 aliases: /preview/api/cassandra/type_uuid /preview/api/ycql/type_uuid type: docs Use the `UUID` data type to specify columns for data of universally unique IDs. `TIMEUUID` is a universal unique identifier variant that includes time information. Data type | Description | -|--| `UUID` | | `TIMEUUID` | | ``` type_specification ::= { UUID | TIMEUUID } uuidliteral ::= 4hexblock 4hexblock '-' 4hexblock '-' 4hexblock '-' 4hexblock '-' 4hexblock 4hexblock 4hex_block 4hexblock ::= hexdigit hexdigit hexdigit hex_digit ``` Where `hex_digit` is a hexadecimal digit (`[0-9a-fA-F]`). Columns of type `UUID` or `TIMEUUID` can be part of the `PRIMARY KEY`. Implicitly, values of type `UUID` and `TIMEUUID` data types are neither convertible nor comparable to other data types. `TIMEUUID`s are version 1 UUIDs: they include the date and time of their generation and a spatially unique node identifier. Comparison of `TIMEUUID` values first compares the time component and then (if time is equal) the node identifier. ```sql ycqlsh:example> CREATE TABLE devices(id UUID PRIMARY KEY, ordered_id TIMEUUID); ``` ```sql ycqlsh:example> INSERT INTO devices (id, ordered_id) VALUES (123e4567-e89b-12d3-a456-426655440000, 123e4567-e89b-12d3-a456-426655440000); ``` ```sql ycqlsh:example> INSERT INTO devices (id, ordered_id) VALUES (123e4567-e89b-42d3-a456-426655440000, 123e4567-e89b-12d3-a456-426655440000); ``` ```sql ycqlsh:example> UPDATE devices SET ordered_id = 00000000-0000-1000-0000-000000000000 WHERE id = 123e4567-e89b-42d3-a456-426655440000; ``` ```sql ycqlsh:example> SELECT * FROM devices; ``` ``` id | ordered_id --+-- 123e4567-e89b-12d3-a456-426655440000 | 123e4567-e89b-12d3-a456-426655440000 123e4567-e89b-42d3-a456-426655440000 | 00000000-0000-1000-0000-000000000000 ```
Project: YugabyteDB (App Definition and Development / Database)
File: 09-like.md

title: "LIKE" In this exercise we will query the products table and find all the products whose names have the letter C in them. ``` SELECT product_id, product_name, quantityperunit FROM products WHERE product_name LIKE '%C%' ``` This query should return 17 rows In this exercise we will query the products table and find all the products whose names have a single character before the letter E appears in them. ``` SELECT product_id, product_name, quantityperunit FROM products WHERE productname LIKE 'e%' ``` This query should return 5 rows In this exercise we will query the products table and find all the products whose names do not start with the letter C. ``` SELECT product_id, product_name, quantityperunit FROM products WHERE product_name NOT LIKE 'C%' ``` This query should return 68 rows In this exercise we will query the products table using the ILIKE operator (which acts like the LIKE operator) to find the products that have the letter C in them. In addition, the ILIKE operator matches value case-insensitively. ``` SELECT product_id, product_name, quantityperunit FROM products WHERE product_name ILIKE '%C%' ``` This query should return 37 rows
Project: YDB (App Definition and Development / Database)
File: assume_order_by.md

Checking that the `SELECT` result is sorted by the value in the specified column or multiple columns. The result of such a `SELECT` statement is treated as sorted, but without actually running a sort. Sort check is performed at the query execution stage. As in case of `ORDER BY`, it supports setting the sort order using the keywords `ASC` (ascending order) and `DESC` (descending order). Expressions are not supported in `ASSUME ORDER BY`. Examples: ```yql SELECT key || "suffix" as key, -CAST(subkey as Int32) as subkey FROM my_table ASSUME ORDER BY key, subkey DESC; ```
Project: Harbor (Provisioning / Container Registry)
File: 2-22-admin-search-projects.md

Test 2-22 - Admin User Search Projects (DB Mode) ======= To verify that a non-admin user can search projects when users are managed locally by Harbor (DB mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database. ( auth_mode is set to db_auth* .) The user data is stored in a local database. A linux host with Docker CLI installed (Docker client). At least a non-admin user. NOTE: In below test, user A is non-admin user. User A should be replaced by a longer and meaningful name. Log in to UI as user A (non-admin). Create at least 5 projects with different names. Log out and log in again as admin user. Search projects with keywords to see if projects of user A can be matched by criteria. Click on a few projects to toggle publicity on and off. Check in "Public Projects" to verify the projects with publicity on can be listed. As described in step 4,6. None
Project: KICS (Provisioning / Security & Compliance)
File: 50cb6c3b-c878-4b88-b50e-d1421bada9e8.md

title: RDP Access Is Not Restricted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 50cb6c3b-c878-4b88-b50e-d1421bada9e8 Query name: RDP Access Is Not Restricted Platform: GoogleDeploymentManager Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: Check if the Google compute firewall allows unrestricted RDP access. Allowed ports should not contain RDP port 3389<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="14" resources: name: firewall type: compute.v1.firewall properties: name: my-firewall sourceRanges: "0.0.0.0/0" allowed: IPProtocol: icmp ports: "80" "8080" "1000-2000" IPProtocol: tcp ports: "80" "8080" "1000-2000" "3389" ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="14" resources: name: firewall type: compute.v1.firewall properties: name: my-firewall sourceRanges: "::/0" allowed: IPProtocol: icmp ports: "80" "8080" "1000-2000" IPProtocol: udp ports: "80" "8080" "1000-2000" "21-3389" ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="9" resources: name: firewall type: compute.v1.firewall properties: name: my-firewall sourceRanges: "::/0" allowed: IPProtocol: all ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: firewall type: compute.v1.firewall properties: name: my-firewall allowed: IPProtocol: icmp ports: "80" "8080" "1000-2000" ```
Project: ClickHouse (App Definition and Development / Database)
File: v21.8.4.51-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix crash during projection materialization when some parts contain missing columns. This fixes . (). Backported in : Fixed underflow of the time value when constructing it from components. Closes . (). Backported in : - Fix bug with aliased column in `Distributed` table. (). Backported in : Fixed another case of `Unexpected merged part ... intersecting drop range ...` error. (). Backported in : Fix postgresql table function resulting in non-closing connections. Closes . (). Backported in : Fix bad type cast when functions like `arrayHas` are applied to arrays of LowCardinality of Nullable of different non-numeric types like `DateTime` and `DateTime64`. In previous versions bad cast occurs. In new version it will lead to exception. This closes . (). Backported in : Remove duplicated source files in CMakeLists.txt in arrow-cmake. ().
Project: YDB (App Definition and Development / Database)
File: concatenation.md

Executed using the binary operator `||`. As with other binary operators, if the data on either side is `NULL`, the result is also `NULL`. Don't confuse this operator with a logical "or": in SQL, it's denoted by the `OR` keyword. It's also not worth doing concatenation using `+`. Examples ```sql SELECT "fo" || "o"; ```
Project: Open Application Model (App Definition and Development / Application Definition & Image Build)
File: 2.overview_and_terminology.md

This section provides an overview of the Open Application Model (OAM) and its terminology. It begins by identifying the organization roles that are involved in the process of running cloud native applications. From there, it lays out the specific terminology that is used throughout this document. This documentation proposes a model that defines cloud native applications as follows: A cloud native application is a collection of interrelated, but discrete components (services, tasks, workers) that, when coupled with configuration and instantiated in a suitable runtime infrastructure, together accomplish a unified functional purpose. In current release, this application model defines the following: Components represents a runnable unit, together with a description (schematic). Workload types identify the different workloads that a component can execute. Traits are overlays that augment a component with additional operations-specific features. Traits represent operator concerns, not developer/software owner concerns. Application scopes represent application boundaries by grouping components with common properties or dependencies. An application configuration assembles a set of component instances, their traits, and the application scopes in which they are placed, combined with configuration parameters and metadata. Thus, an application is a collection of components with a set of operational traits and scoped together into one or more application boundaries. | Previous Part | Next Part | | - |-| || |
Project: ko (App Definition and Development / Application Definition & Image Build)
File: sboms.md

A is a list of software components that a software artifact depends on. Having a list of dependencies can be helpful in determining whether any vulnerable components were used to build the software artifact. From v0.9+, `ko` generates and uploads an SBOM for every image it produces by default. ko will generate an SBOM in the format by default, but you can select the format instead with the `--sbom=cyclonedx` flag. To disable SBOM generation, pass `--sbom=none`. These SBOMs can be downloaded using the command.
Project: YugabyteDB (App Definition and Development / Database)
File: oidc-authentication.md

title: Enable YugabyteDB Anywhere SSO authentication via OIDC headerTitle: Enable YugabyteDB Anywhere SSO authentication via OIDC description: Use OIDC to enable SSO login to YugabyteDB Anywhere. linkTitle: Configure authentication menu: v2.18_yugabyte-platform: identifier: oidc-authentication parent: administer-yugabyte-platform weight: 10 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="../oidc-authentication/" class="nav-link active"> <i class="fa-solid fa-cubes"></i> OIDC </a> </li> <li> <a href="../ldap-authentication/" class="nav-link"> <i class="fa-solid fa-cubes" aria-hidden="true"></i> LDAP </a> </li> </ul> OpenID Connect (OIDC) is an authentication protocol that allows client applications to confirm the user's identity via authentication by an authorization server. YugabyteDB Anywhere uses OIDC to enable single sign-on (SSO) authentication. You can create an OIDC configuration as follows: Navigate to Admin > User Management > User Authentication. Select OIDC Configuration and complete the fields shown in the following illustration: In the Client ID field, enter the unique identifier that you provided when you manually created the client application in the identity provider. In the Client Secret field, enter the password or secret for authenticating your Yugabyte client application with your identity provider. Use the Discovery URL field to provide a URL for a discovery document that contains OIDC configuration for the identity provider. The discovery document is a JSON file stored in a well-known location. This file contains key-value pairs with details about the OIDC provider's configuration, including uniform resource identifiers of the authorization, token, revocation, user information, and public-keys endpoints. is an example of such file. For most identity providers, `/.well-known/openid-configuration` is appended to the issuer to generate the metadata URL for OIDC specifications. In the Scope field, enter your identity provider OIDC scope that is allowed to be requested. This field accepts a space-separated list of values. If left blank, all scopes will be considered. In the Email Attribute field, enter the OIDC scope containing the user email identifier. This field accepts a case-sensitive custom configuration. Typically, this field is left blank. Click Save. For information on how to add users, see . The email ID that you enter in the Add User dialog must be registered with the identity provider, and the role must reflect the user's role on YugabyteDB Anywhere. Once OIDC is enabled, the user is presented with the following login options: Login with SSO redirects the user to the appropriate identity provider's login mechanism. Super Admin Login allows the user to log in to YugabyteDB Anywhere as a local super admin.
Project: KICS (Provisioning / Security & Compliance)
File: 66505003-7aba-45a1-8d83-5162d5706ef5.md

title: Ram Policy Attached to User hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 66505003-7aba-45a1-8d83-5162d5706ef5 Query name: Ram Policy Attached to User Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Ram policies should not be attached to users<br> ```tf title="Positive test num. 1 - tf file" hl_lines="35" resource "alicloudramuser" "user1" { name = "userName" displayname = "userdisplay_name" mobile = "86-18688888888" email = "hello.uuu@aaa.com" comments = "yoyoyo" force = true } resource "alicloudrampolicy" "policy1" { name = "policyName" document = <<EOF { "Statement": [ { "Action": [ "oss:ListObjects", "oss:GetObject" ], "Effect": "Allow", "Resource": [ "acs:oss:::mybucket", "acs:oss:::mybucket/*" ] } ], "Version": "1" } EOF description = "this is a policy test" force = true } resource "alicloudramuserpolicyattachment" "attach" { policyname = alicloudram_policy.policy1.name policytype = alicloudram_policy.policy1.type username = alicloudram_user.user1.name } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudramgroup" "group2" { name = "groupName" comments = "this is a group comments." force = true } resource "alicloudrampolicy" "policy2" { name = "policyName" document = <<EOF { "Statement": [ { "Action": [ "oss:ListObjects", "oss:GetObject" ], "Effect": "Allow", "Resource": [ "acs:oss:::mybucket", "acs:oss:::mybucket/*" ] } ], "Version": "1" } EOF description = "this is a policy test" force = true } resource "alicloudramgrouppolicyattachment" "attach" { policyname = alicloudram_policy.policy2.name policytype = alicloudram_policy.policy2.type groupname = alicloudram_group.group2.name } ``` ```tf title="Negative test num. 2 - tf file" resource "alicloudramrole" "role3" { name = "roleName" document = <<EOF { "Statement": [ { "Action": "sts:AssumeRole", "Effect": "Allow", "Principal": { "Service": [ "apigateway.aliyuncs.com", "ecs.aliyuncs.com" ] } } ], "Version": "1" } EOF description = "this is a role test." force = true } resource "alicloudrampolicy" "policy3" { name = "policyName" document = <<EOF { "Statement": [ { "Action": [ "oss:ListObjects", "oss:GetObject" ], "Effect": "Allow", "Resource": [ "acs:oss:::mybucket", "acs:oss:::mybucket/*" ] } ], "Version": "1" } EOF description = "this is a policy test" force = true } resource "alicloudramrolepolicyattachment" "attach" { policyname = alicloudram_policy.policy3.name policytype = alicloudram_policy.policy3.type rolename = alicloudram_role.role3.name } ```
Project: KICS (Provisioning / Security & Compliance)
File: 967eb3e6-26fc-497d-8895-6428beb6e8e2.md

title: Elasticsearch Domain Not Encrypted Node To Node hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 967eb3e6-26fc-497d-8895-6428beb6e8e2 Query name: Elasticsearch Domain Not Encrypted Node To Node Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: Elasticsearch Domain encryption should be enabled node to node<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awselasticsearchdomain" "positive1" { domain_name = "example" elasticsearch_version = "1.5" cluster_config { instance_type = "r4.large.elasticsearch" } snapshot_options { automatedsnapshotstart_hour = 23 } tags = { Domain = "TestDomain" } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="14" resource "awselasticsearchdomain" "positive1" { domain_name = "example" elasticsearch_version = "1.5" cluster_config { instance_type = "r4.large.elasticsearch" } snapshot_options { automatedsnapshotstart_hour = 23 } nodetonode_encryption { enabled = false } tags = { Domain = "TestDomain" } } ``` ```tf title="Negative test num. 1 - tf file" resource "awselasticsearchdomain" "negative1" { domain_name = "example" elasticsearch_version = "1.5" cluster_config { instance_type = "r4.large.elasticsearch" } snapshot_options { automatedsnapshotstart_hour = 23 } nodetonode_encryption { enabled = true } tags = { Domain = "TestDomain" } } ```
Project: KICS (Provisioning / Security & Compliance)
File: c9d81239-c818-4869-9917-1570c62b81fd.md

title: BOM - GCP FI hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c9d81239-c818-4869-9917-1570c62b81fd Query name: BOM - GCP FI Platform: Terraform Severity: <span style="color:#CCCCCC">Trace</span> Category: Bill Of Materials URL: A list of Filestore Instance resources found. Filestore instances are fully managed file servers on Google Cloud that can be connected to Compute Engine VMs, GKE clusters, and your on-premises machines. Once provisioned, you can scale the capacity of your instances according to need without any downtime.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="32 1 59" resource "googlefilestoreinstance" "instance" { name = "test-instance" location = "us-central1-b" tier = "BASIC_SSD" file_shares { capacity_gb = 2660 name = "share1" nfsexportoptions { ip_ranges = ["10.0.0.0/24"] accessmode = "READWRITE" squashmode = "NOROOT_SQUASH" } nfsexportoptions { ip_ranges = ["10.10.0.0/24"] accessmode = "READONLY" squashmode = "ROOTSQUASH" anon_uid = 123 anon_gid = 456 } } networks { network = "default" modes = ["MODE_IPV4"] connectmode = "DIRECTPEERING" } } resource "googlefilestoreinstance" "instance2" { name = "test-instance" location = "us-central1" tier = "ENTERPRISE" file_shares { capacity_gb = 2560 name = "share1" } networks { network = "default" modes = ["MODE_IPV4"] } kmskeyname = googlekmscryptokey.filestorekey.id } resource "googlekmskeyring" "filestorekeyring" { name = "filestore-keyring" location = "us-central1" } resource "googlekmscryptokey" "filestorekey" { name = "filestore-key" keyring = googlekmskeyring.filestore_keyring.id } resource "googlefilestoreinstance" "instance3" { name = "test-instance" location = "us-central1-b" tier = "BASIC_SSD" file_shares { capacity_gb = 2660 name = "share1" nfsexportoptions { ip_ranges = ["0.0.0.0/0"] accessmode = "READWRITE" squashmode = "NOROOT_SQUASH" } } networks { network = "default" modes = ["MODE_IPV4"] connectmode = "DIRECTPEERING" } } ``` ```tf title="Negative test num. 1 - tf file" resource "googlebigquerydataset" "negative1" { datasetid = "exampledataset" friendly_name = "test" description = "This is a test description" location = "EU" defaulttableexpiration_ms = 3600000 labels = { env = "default" } access { role = "OWNER" userbyemail = googleserviceaccount.bqowner.email } access { role = "READER" domain = "hashicorp.com" } } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: 10-13-2022-17-10-10_50caf82f.md

timestamp: "2022-10-13 17:10:00 UTC Thu" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "v0.6.15" k8s-distro: minikube k8s-version: "v1.20.11" service-mesh: Consul service-mesh-version: "v0.49.0" tests: consul-client: null consul-server: null overall-status: "failing"
Project: Teleport (Provisioning / Security & Compliance)
File: DEBUG.md

Running locally let you attach a debugger while still working against a real cluster. This can be used to reproduce most complex issues and troubleshoot specific cases. Validate your current context works ```shell kubectl cluster-info ``` Open a proxy to the api-server, then let the shell open and running ```shell kubectl proxy ``` open a new terminal, create a new temporary directory and create your new kubeconfig ```shell export KUBECONFIG="$(mktemp)" kubectl config set-credentials myself --username=foo kubectl config set-cluster local-server --server=http://localhost:8001 kubectl config set-context default-context --cluster=local-server --user=myself kubectl config use-context default-context echo "$KUBECONFIG" ``` run the controller with the `KUBECONFIG` environment variable set yzlg092_dgktzq3nzp5s040000gn/T/tmp.WQWM1TXWku ``` Configure your IDE to set the tag `debug` on build, or manually build the plugin `go build -o protoc-gen-crd-debug -tags debug`. This debug build won't load requests from stdin, but from a dump file. You must instruct the debug build to load instructions from a dump file by setting the `TELEPORTPROTOCREAD_FILE` environment variable. ```shell export TELEPORTPROTOCREADFILE="/var/folders/vz/qfyzlg092dgktzq3nzp5s040000gn/T/tmp.WQWM1TXWku" ./protoc-gen-crd-debug ``` From there you can invoke the plugin from `delve`, or configure your favorite IDE to set the environment variable when debugging the binary.