cwielenb/CNCF-Dataset huggingface dataset:
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: userns-uid-map-user.md

Specifies that a UID mapping to be used to set ownership, at the filesystem level, on the working container's contents, can be found in entries in the `/etc/subuid` file which correspond to the specified user. Commands run when handling `RUN` instructions defaults to being run in their own user namespaces, configured using the UID and GID maps. If --userns-gid-map-group is specified, but --userns-uid-map-user is not specified, `podman` assumes that the specified group name is also a suitable user name to use as the default setting for this option. NOTE: When this option is specified by a rootless user, the specified mappings are relative to the rootless user namespace in the container, rather than being relative to the host as it is when run rootful.
Project: StarRocks (App Definition and Development / Database)
File: timestampadd.md

displayed_sidebar: "English" Adds an integer expression interval to the date or datetime expression `datetime_expr`. The unit for the interval as mentioned must be one of the following: MILLISECOND (since 3.2), SECOND, MINUTE, HOUR, DAY, WEEK, MONTH, or YEAR. ```Haskell DATETIME TIMESTAMPADD(unit, interval, DATETIME datetime_expr) ``` `datetime_expr`: the DATE or DATETIME value to which you want to add a time interval. `interval`: an integer expression that specifies the number of intervals to add. `unit`: the unit of the time interval to add. Supported units include MILLISECOND (since 3.2), SECOND, MINUTE, HOUR, DAY, WEEK, MONTH, and YEAR. Returns a value of the same data type as `datetime_expr`. ```plain text MySQL > SELECT TIMESTAMPADD(MINUTE,1,'2019-01-02'); ++ | timestampadd(MINUTE, 1, '2019-01-02 00:00:00') | ++ | 2019-01-02 00:01:00 | ++ MySQL > SELECT TIMESTAMPADD(WEEK,1,'2019-01-02'); +-+ | timestampadd(WEEK, 1, '2019-01-02 00:00:00') | +-+ | 2019-01-09 00:00:00 | +-+ MySQL > SELECT TIMESTAMPADD(MILLISECOND,1,'2019-01-02'); +--+ | timestampadd(MILLISECOND, 1, '2019-01-02') | +--+ | 2019-01-02 00:00:00.001000 | +--+ ``` TIMESTAMPADD
Project: Harbor (Provisioning / Container Registry)
File: 4-02-LDAP-user-view-logs.md

Test 4-02 - User Views Logs (LDAP Mode) ======= To verify that a non-admin user can views logs when users are managed externally by LDAP or AD (LDAP mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against an LDAP or AD server. ( auth_mode is set to ldap_auth* .) The user data is stored in an LDAP or AD server. A linux host with Docker CLI installed (Docker client). On a Docker client host, use `docker login <harbor_host>` command to log in as a non-admin user. Run some `docker push` and `docker pull` commands to push images to the registry and pull from the registry. Log in to the UI as the non-admin user. Delete a few images from the project. View the logs of the project. Try below search criteria to see if the search result is correct: push only pull only pull and push delete only all push and delete different date ranges date range and push All operations in Step 2 & 4 should be logged. Logs can be viewed in Step 5, check if the time and operations are correct. Logs can be filtered in Step 6. None
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.1.6.en.md

Added option to configure detection of legacy protocol in MondoDB connectors and bridges. Added a new API endpoint `DELETE /banned` to clear all `banned` data. Changed the type of the `mqtt.maxpacketsize` from string to byteSize to better represent the valid numeric range. Strings will still be accepted for backwards compatibility. Refactored datetime-related modules and functions to simplify the code. Introduced topic index for the rule engine runtime that significantly improves the performance of EMQX with a non-trivial number of rules consuming messages matching different topic filters. Added a check for the maximum value of the timestamp in the API to ensure it is a valid Unix timestamp. Removed os_mon application monitor support on Windows platforms to prevent VM crashes. Functionality remains on non-Windows platforms. Fixed crashing when debugging/tracing with large payloads(introduce when ) Removed validation that enforced non-empty PEM for CA cert file. CA certificate file PEM can now be empty. Upgraded Erlang/OTP to 25.3.2-2. Erlang/OTP 25.3.2-2 excludes sensitive data from mnesia_hook log message.
Project: ShardingSphere (App Definition and Development / Database)
File: show-shadow-algorithm-plugins.en.md

+++ title = "SHOW SHADOW ALGORITHM PLUGINS" weight = 6 +++ The `SHOW SHADOW ALGORITHM PLUGINS` syntax is used to query all the implementations of the interface `org.apache.shardingsphere.shadow.spi.ShadowAlgorithm`. {{< tabs >}} {{% tab name="Grammar" %}} ```sql showShadowAlgorithmPlugins ::= 'SHOW' 'SHADOW' 'ALGORITHM' 'PLUGINS' ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} | Columns | Description | |--|--| | type | type | | type_aliases | type aliases | | description | description | Query all the implementations for `org.apache.shardingsphere.shadow.spi.ShadowAlgorithm` interface ```sql SHOW SHADOW ALGORITHM PLUGINS ``` ```sql SHOW SHADOW ALGORITHM PLUGINS; +-+--+-+ | type | type_aliases | description | +-+--+-+ | SQL_HINT | | | | REGEX_MATCH | | | | VALUE_MATCH | | | +-+--+-+ 3 rows in set (0.37 sec) ``` `SHOW`, `SHADOW`, `ALGORITHM`, `PLUGINS`
Project: CockroachDB (App Definition and Development / Database)
File: nodes-response.md

<a name="cockroach.server.serverpb.NodesResponse"></a> NodesResponse describe the nodes in the cluster. Support status: | Field | Type | Label | Description | Support status | | -- | - | -- | -- | -- | | nodes | | repeated | nodes carries the status payloads for all nodes in the cluster. | | | livenessbynodeid | | repeated | livenessbynodeid maps each node ID to a liveness status. | |
Project: YugabyteDB (App Definition and Development / Database)
File: dbschema.md

title: Use DbSchema with YugabyteDB YSQL headerTitle: DbSchema linkTitle: DbSchema description: Use DbSchema to work with distributed SQL databases in YugabyteDB. menu: v2.18: identifier: dbschema parent: tools weight: 60 type: docs is a visual database tool that supports over 40 databases from a single interface, and can be used to reverse-engineer schemas, edit entity-relationship (ER) diagrams, browse data, visually build queries, and synchronize schemas. This document describes how to connect DbSchema to YugabyteDB databases. Your YugabyteDB cluster should be up and running. Refer to . Download the distribution package for the operating system on your client computer from the . Install DbSchema using the install wizard. The following steps show how to configure YugabyteDB running on your local host. Launch the DbSchema application. The Welcome to DbSchema page appears. On the Start New Project panel, click Start to connect to a database. The Database Connection Dialog opens. In the Alias field, enter `YugabyteDB` to name the database connection. From the DBMS dropdown list, select `PostgreSQL`. The Method & Driver field shows the available PostgreSQL JDBC drivers. For the Method & Driver option, select Standard (1 of 2). There is no need to add a driver because DbSchema includes the PostgreSQL JDBC driver. In the Compose URL tab, click Remote computer or custom port. The default PostgreSQL values for server host and port appear. In the port field, enter `5433` (the default port for YSQL) and then click Check (Ping). A message appears saying that the YugabyteDB server is reachable. Under Authentication, change the Database User to `yugabyte` (the default YugabyteDB user). If you have enabled authentication, enter the password. Otherwise, leave the field blank. Under Database, enter `yugabyte` (the default YugabyteDB database) or the name of the database you want to connect to. Click Connect. The Select Schemas / Catalogs dialog appears. Click OK to accept the default options. Otherwise, you can customize the schema information that you want for this connection. You have successfully created a database connection to the default database (`yugabyte`) using the default user (`yugabyte`). For help using DbSchema, see the . YugabyteDB includes sample databases for you to explore using DbSchema. Refer to .
Project: Chef InSpec (Provisioning / Security & Compliance)
File: azurerm_network_interfaces.md

+++ title = "azurermnetworkinterfaces resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurermnetworkinterfaces" identifier = "inspec/resources/azure/azurermnetworkinterfaces.md azurermnetworkinterfaces resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azurenetwork_interfaces" >}} Use the `azurermnetworkinterfaces` InSpec audit resource to test properties and configuration of Azure Network interfaces. This resource interacts with version `2018-11-01` of the Azure Management API. For more information see the . At the moment, there doesn't appear to be a way to select the version of the Azure API docs. If you notice a newer version being referenced in the official documentation please open an issue or submit a pull request using the updated version. This resource is available in the `inspec-azure` [resource pack](/inspec/glossary/#resource-pack). To use it, add the following to your `inspec.yml` in your top-level profile: depends: inspec-azure: git: https://github.com/inspec/inspec-azure.git You'll also need to setup your Azure credentials; see the resource pack . This resource first became available in 1.7.2 of the inspec-azure resource pack. An `azurermnetworkinterfaces` resource block returns all Azure Network Interfaces, either within a Resource Group (if provided), or within an entire Subscription. describe azurermnetworkinterfaces do ... end or describe azurermnetworkinterfaces(resource_group: 'my-rg') do ... end The following examples show how to use this InSpec audit resource. describe azurermnetworkinterfaces do it { should exist } its('names') { should include 'my-network-interface-name' } end Filters the results to include only those network interfaces which match the given name. This is a string value. describe azurermnetworkinterfaces.where{ name.eql?('network-interface-5') } do it { should exist } end Filters the results to include only those servers which reside in a given location. This is a string value. describe azurermnetworkinterfaces.where{ location.eql?('eastus') } do it { should exist } end `id` `name` `location` `properties` `tags` `type` Azure resource ID. Network interface name, e.g. `nic-name`. its('names') { should include 'nic-name' } Resource location, e.g. `eastus`. its('locations') { should_not include 'eastus' } A collection of additional configuration properties related to the Network interface, e.g. `ipConfigurations`. Resource tags applied to the Network interface. The type of Resource, typically `Microsoft.Network/networkInterfaces`. {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The control will pass if the filter returns at least one result. Use `should_not` if you expect zero matches. describe azurermnetworkinterfaces do it { should exist } end Your [Service Principal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal) must be setup with a `contributor` role on the subscription you wish to test.
Project: ScalarDB (App Definition and Development / Database)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Prepare the following config file: ```properties scalar.db.storage=... scalar.db.contact_points=... scalar.db.username=... scalar.db.password=... ``` Prepare the following schema file: ```json { "sampledb.sampletable": { "partition-key": [ "c1" ], "clustering-key": [ "c2 ASC" ], "columns": { "c1": "INT", "c2": "TEXT", "c3": "INT", "c4": "INT" }, "secondary-index": [ "c4" ], } } ``` Load the schema with Schema Loader Execute the following code snippet: ```java // the code snippet to reproduce the behavior ``` See error ```java // the error ``` Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Environment (please complete the following information): OS: [e.g. masOS Monterey 12.5] Java Version: [e.g. 1.8.0_202] ScalarDB Version: [e.g. 3.7.0] Additional context Add any other context about the problem here.
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: postgres.md

The . Based on . 11 (Security Support until November 2023) - `uselagoon/postgres-11` 12 (Security Support until November 2024) - `uselagoon/postgres-12` 13 (Security Support until November 2025) - `uselagoon/postgres-13` 14 (Security Support until November 2026) - `uselagoon/postgres-14` 15 (Security Support until November 2027) - `uselagoon/postgres-15` 16 (Security Support until November 2028) - `uselagoon/postgres-16` !!! Tip We stop updating EOL PostgreSQL images usually with the Lagoon release that comes after the officially communicated EOL date: The default exposed port of Postgres containers is port `5432`. To allow Lagoon to select the best way to run the Postgres container, use `lagoon.type: postgres` - this allows DBaaS operator to provision a cloud database if available in the cluster. Use `lagoon.type: postgres-single` to specifically request Postgres in a container. Persistent storage is always provisioned for postgres containers at /var/lib/postgresql/data. ```yaml title="docker-compose.yml" postgres: image: uselagoon/postgres-14-drupal:latest labels: lagoon.type: postgres ports: "5432" volumes: db:/var/lib/postgresql/data ``` If you have SQL statements that need to be run immediately after container startup to initialize the database, you can place those `.sql` files in the container's `docker-entrypoint-initdb.d` directory. Any `.sql` files contained in that directory are run automatically at startup, as part of bringing the PostgreSQL container up. !!! Warning These scripts are only run if the container is started with an empty database.
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: pre-commit-hooks.md

title: Pre-commit hooks labels: category: tooling layer: cicd software: git pre-commit code: https://github.com/anderseknert/pre-commit-opa blogs: https://www.eknert.com/tech/2020/08/31/pre-commit-hooks-for-opa inventors: independent Pre-commit git hooks for OPA and Rego development
Project: Druid (App Definition and Development / Database)
File: druid-pac4j.md

id: druid-pac4j title: "Druid pac4j based Security extension" <!-- ~ 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. --> Apache Druid Extension to enable based Authentication for Druid Processes using as the underlying client library. This can be used with any authentication server that supports same e.g. . The pac4j authenticator should only be used at the router node to enable a group of users in existing authentication server to interact with Druid cluster, using the . This extension also provides a JWT authenticator that validates associated with a request. ID Tokens are attached to the request under the `Authorization` header with the bearer token prefix - `Bearer `. This authenticator is intended for services to talk to Druid by initially authenticating with an OIDC server to retrieve the ID Token which is then attached to every Druid request. This extension does not support JDBC client authentication. ``` druid.auth.authenticatorChain=["pac4j"] druid.auth.authenticator.pac4j.type=pac4j druid.auth.authenticatorChain=["jwt"] druid.auth.authenticator.jwt.type=jwt ``` |Property|Description|Default|required| |--||--|-| |`druid.auth.pac4j.cookiePassphrase`|passphrase for encrypting the cookies used to manage authentication session with browser. It can be provided as plaintext string or The .|none|Yes| |`druid.auth.pac4j.readTimeout`|Socket connect and read timeout duration used when communicating with authentication server|PT5S|No| |`druid.auth.pac4j.enableCustomSslContext`|Whether to use custom SSLContext setup via extension which must be added to extensions list when this property is set to true.|false|No| |`druid.auth.pac4j.oidc.clientID`|OAuth Client Application id.|none|Yes| |`druid.auth.pac4j.oidc.clientSecret`|OAuth Client Application secret. It can be provided as plaintext string or The .|none|Yes| |`druid.auth.pac4j.oidc.discoveryURI`|discovery URI for fetching OP metadata .|none|Yes| |`druid.auth.pac4j.oidc.oidcClaim`| that will be extracted from the ID Token after validation.|name|No| |`druid.auth.pac4j.oidc.scope`| scope is used by an application during authentication to authorize access to a user's details |`openid profile email`|No
Project: StarRocks (App Definition and Development / Database)
File: st_contains.md

displayed_sidebar: "English" Checks whether the geometric figure shape1 can fully contain shape2. ```Haskell BOOL ST_Contains(GEOMETRY shape1, GEOMETRY shape2) ``` ```Plain Text MySQL > SELECT STContains(STPolygon("POLYGON ((0 0, 10 0, 10 10, 0 10, 0 0))"), ST_Point(5, 5)); +-+ | stcontains(stpolygon('POLYGON ((0 0, 10 0, 10 10, 0 10, 0 0))'), st_point(5.0, 5.0)) | +-+ | 1 | +-+ MySQL > SELECT STContains(STPolygon("POLYGON ((0 0, 10 0, 10 10, 0 10, 0 0))"), ST_Point(50, 50)); ++ | stcontains(stpolygon('POLYGON ((0 0, 10 0, 10 10, 0 10, 0 0))'), st_point(50.0, 50.0)) | ++ | 0 | ++ ``` ST_CONTAINS,ST,CONTAINS
Project: KICS (Provisioning / Security & Compliance)
File: e76fd7ab-7333-40c6-a2d8-ea28af4a319e.md

title: Ram Account Password Policy Max Login Attempts Unrecommended hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e76fd7ab-7333-40c6-a2d8-ea28af4a319e Query name: Ram Account Password Policy Max Login Attempts Unrecommended Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Secret Management URL: Ram Account Password Policy should have 'maxloginattempts' to a maximum of 5 incorrect login attempts<br> ```tf title="Positive test num. 1 - tf file" hl_lines="10" resource "alicloudramaccountpasswordpolicy" "corporate" { minimumpasswordlength = 9 requirelowercasecharacters = false requireuppercasecharacters = false require_numbers = false require_symbols = false hard_expiry = true maxpasswordage = 12 passwordreuseprevention = 5 maxloginattempts = 6 } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudramaccountpasswordpolicy" "corporate" { minimumpasswordlength = 9 requirelowercasecharacters = false requireuppercasecharacters = false require_numbers = false require_symbols = false hard_expiry = true maxpasswordage = 12 passwordreuseprevention = 5 maxloginattempts = 3 } ``` ```tf title="Negative test num. 2 - tf file" resource "alicloudramaccountpasswordpolicy" "corporate" { minimumpasswordlength = 9 requirelowercasecharacters = false requireuppercasecharacters = false require_numbers = false require_symbols = false hard_expiry = true maxpasswordage = 12 passwordreuseprevention = 5 } ```
Project: KICS (Provisioning / Security & Compliance)
File: abcefee4-a0c1-4245-9f82-a473f79a9e2f.md

title: ECS Cluster with Container Insights Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: abcefee4-a0c1-4245-9f82-a473f79a9e2f Query name: ECS Cluster with Container Insights Disabled Platform: Pulumi Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: ECS Cluster should enable container insights<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8" name: aws-eks runtime: yaml description: An EKS cluster resources: foo: type: aws:ecs:Cluster properties: settings: name: containerInsights value: disabled ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="8" name: aws-eks runtime: yaml description: An EKS cluster resources: foo: type: aws:ecs:Cluster properties: settings: [] ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="7" name: aws-eks runtime: yaml description: An EKS cluster resources: foo: type: aws:ecs:Cluster properties: description: example ``` ```yaml title="Negative test num. 1 - yaml file" name: aws-eks runtime: yaml description: An EKS cluster resources: foo: type: aws:ecs:Cluster properties: settings: name: containerInsights value: enabled ```
Project: YugabyteDB (App Definition and Development / Database)
File: cr-pr-cd-equality-report.md

title: crprcdequalityreport.sql linkTitle: crprcdequalityreport.sql headerTitle: crprcdequalityreport.sql description: crprcdequalityreport.sql - Part of the code kit for the "Analyzing a normal distribution" section within the YSQL window functions documentation. menu: v2.18: identifier: cr-pr-cd-equality-report parent: analyzing-a-normal-distribution weight: 60 type: docs Save this script as `crprcdequalityreport.sql`. ```plpgsql set clientminmessages = warning; drop type if exists prcdequalityreportt cascade; create type prcdequalityreportt as("count(*)" int, maxscore text, maxratio text); create or replace function prcdequality_report( delta_threshold in double precision) returns SETOF prcdequalityreportt language sql as $body$ with measures as ( select score, (percent_rank() over w) as pr, (cume_dist() over w) as cd from t4_view window w as (order by score)) , ratios as ( select score, (pr*100::double precision)/cd as ratio from measures) , deltas as ( select score, ratio, abs(ratio - 100) as delta from ratios) , bad_deltas as ( select score, ratio, delta from deltas where delta > delta_threshold) , result as ( select count(*) as n, tochar(max(score), '999.99') as maxscore, tochar(max(ratio), '999.99') as maxratio from bad_deltas) select (n, maxscore, maxratio)::prcdequalityreportt from result; $body$; ```