cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 16e0879a-c4ae-4ff8-a67d-a2eed5d67b8f.md

title: PostgreSQL Log Duration Not Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 16e0879a-c4ae-4ff8-a67d-a2eed5d67b8f Query name: PostgreSQL Log Duration Not Set Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Make sure that for PostgreSQL Database, server parameter 'log_duration' is set to 'ON'<br> ```tf title="Positive test num. 1 - tf file" hl_lines="20 13 6" resource "azurermpostgresqlconfiguration" "positive1" { name = "log_duration" resourcegroupname = "example1resourcegroup_name" servername = "example1server_name" value = "off" } resource "azurermpostgresqlconfiguration" "positive2" { name = "log_duration" resourcegroupname = "example2resourcegroup_name" servername = "example2server_name" value = "Off" } resource "azurermpostgresqlconfiguration" "positive3" { name = "log_duration" resourcegroupname = "example3resourcegroup_name" servername = "example3server_name" value = "OFF" } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermpostgresqlconfiguration" "negative1" { name = "log_duration" resourcegroupname = "example1resourcegroup_name" servername = "example1server_name" value = "on" } resource "azurermpostgresqlconfiguration" "negative2" { name = "log_duration" resourcegroupname = "example2resourcegroup_name" servername = "example2server_name" value = "On" } resource "azurermpostgresqlconfiguration" "negative3" { name = "log_duration" resourcegroupname = "example3resourcegroup_name" servername = "example3server_name" value = "ON" } ```
Project: ClickHouse (App Definition and Development / Database)
File: ssl-x509.md

slug: /en/operations/external-authenticators/ssl-x509 title: "SSL X.509 certificate authentication" import SelfManaged from '@site/docs/en/snippets/selfmanagedonlynoroadmap.md'; <SelfManaged /> enables mandatory certificate validation for the incoming connections. In this case, only connections with trusted certificates can be established. Connections with untrusted certificates will be rejected. Thus, certificate validation allows to uniquely authenticate an incoming connection. `Common Name` field of the certificate is used to identify connected user. This allows to associate multiple certificates with the same user. Additionally, reissuing and revoking of the certificates does not affect the ClickHouse configuration. To enable SSL certificate authentication, a list of `Common Name`'s for each ClickHouse user must be specified in the settings file `users.xml `: Example ```xml <clickhouse> <!- ... --> <users> <user_name> <ssl_certificates> <commonname>host.domain.com:exampleuser</common_name> <commonname>host.domain.com:exampleuserdev</commonname> <!-- More names --> </ssl_certificates> <!-- Other settings --> </user_name> </users> </clickhouse> ``` For the SSL to work correctly, it is also important to make sure that the parameter is configured properly.
Project: Eclipse Che (App Definition and Development / Application Definition & Image Build)
File: PULL_REQUEST_TEMPLATE.md

<!-- Please review the following before submitting a PR: Che's Contributing Guide: https://github.com/eclipse/che/blob/master/CONTRIBUTING.md Pull Request Policy: https://github.com/eclipse/che/wiki/Development-Workflow#pull-requests --> <!-- Please include a screenshot or a screencast explaining what is doing this PR --> <!-- Please include any related issue from eclipse che repository (or from another issue tracker). Include link to other pull requests like documentation PR from --> <!-- Please explain for example : The test platform (openshift, kubernetes, minikube, CodeReady Container, docker-desktop, etc) Installation method: chectl / che-operator steps to reproduce --> Reviewers, please comment how you tested the PR when approving it.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_resourcemanager_folder_iam_policy.md

+++ title = "googleresourcemanagerfolderiampolicy resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleresourcemanagerfolderiampolicy" identifier = "inspec/resources/gcp/googleresourcemanagerfolderiampolicy.md googleresourcemanagerfolderiampolicy resource" parent = "inspec/resources/gcp" +++ A `googleresourcemanagerfolderiampolicy` is used to test a Google Folder Iam Policy resource ```ruby describe googleresourcemanagerfolderiampolicy(name: "name") do it { should exist } end googleresourcemanagerfolderiampolicy(name: "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 `googleresourcemanagerfolderiampolicy` 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: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.0.6.md

fix instructions under example by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/199 fix #202: camera stops streaming without timeout by @Yang-Xijie in https://github.com/Edgenesis/shifu/pull/204 fix variable name by @Yang-Xijie in https://github.com/Edgenesis/shifu/pull/203 fix readme by @Yang-Xijie in https://github.com/Edgenesis/shifu/pull/211 Update auto_assign.yml by @tomqin93 in https://github.com/Edgenesis/shifu/pull/201 Bump k8s.io/client-go from 0.24.3 to 0.24.4 by @dependabot in https://github.com/Edgenesis/shifu/pull/206 Bump k8s.io/apimachinery from 0.24.3 to 0.24.4 in /deviceshifu/pkg/mockdevice/mockdevice by @dependabot in https://github.com/Edgenesis/shifu/pull/207 Add logo in README by @Yang-Xijie in https://github.com/Edgenesis/shifu/pull/208 Better README by @Yang-Xijie in https://github.com/Edgenesis/shifu/pull/209 add markdown contribution standard by @Yang-Xijie in https://github.com/Edgenesis/shifu/pull/210 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.0.5...v0.0.6
Project: ShardingSphere (App Definition and Development / Database)
File: show-unused-sharding-key-generators.en.md

+++ title = "SHOW UNUSED SHARDING KEY GENERATORS" weight = 6 +++ `SHOW SHARDING KEY GENERATORS` syntax is used to query sharding key generators that are not used in specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowShardingKeyGenerators::= 'SHOW' 'SHARDING' 'KEY' 'GENERATOR' ('FROM' databaseName)? databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When databaseName is not specified, the default is the currently used DATABASE. If DATABASE is not used, No database selected will be prompted. | column | Description | |--|--| | name | Sharding key generator name | | type | Sharding key generator type | | props | Sharding key generator properties | Query sharding key generators that are not used in the specified logical database ```sql SHOW UNUSED SHARDING KEY GENERATORS FROM sharding_db; ``` ```sql mysql> SHOW UNUSED SHARDING KEY GENERATORS FROM sharding_db; +-+--+-+ | name | type | props | +-+--+-+ | snowflakekeygenerator | snowflake | | +-+--+-+ 1 row in set (0.00 sec) ``` Query sharding key generators that are not used in the current logical database ```sql SHOW UNUSED SHARDING KEY GENERATORS; ``` ```sql mysql> SHOW UNUSED SHARDING KEY GENERATORS; +-+--+-+ | name | type | props | +-+--+-+ | snowflakekeygenerator | snowflake | | +-+--+-+ 1 row in set (0.00 sec) ``` `SHOW`, `UNUSED`, `SHARDING`, `KEY`, `GENERATORS`, `FROM`
Project: YDB (App Definition and Development / Database)
File: version.md

Use the `version` subcommand to find out the version of the {{ ydb-short-name }} CLI installed and manage new version availability auto checks. New version availability auto checks are made when you run any {{ ydb-short-name }} CLI command, except `ydb version --enable-checks` and `ydb version --disable-checks`, but only once in 24 hours. The result and time of the last check are saved to the {{ ydb-short-name }} CLI configuration file. General format of the command: ```bash {{ ydb-cli }} [global options...] version [options...] ``` `global options`: . `options`: . View a description of the command: ```bash {{ ydb-cli }} version --help ``` | Parameter | Description | | | `--semantic` | Get only the version number. | | `--check` | Check if a new version is available. | | `--disable-checks` | Disable new version availability checks. | | `--enable-checks` | Enable new version availability checks. | When running {{ ydb-short-name }} CLI commands, the system automatically checks if a new version is available. If the host where the command is run doesn't have internet access, this causes a delay and the corresponding warning appears during command execution. To disable auto checks for updates, run: ```bash {{ ydb-cli }} version --disable-checks ``` Result: ```text Latest version checks disabled ``` To facilitate data handling in scripts, you can limit result to the {{ ydb-short-name }} CLI version number: ```bash {{ ydb-cli }} version --semantic ``` Result: ```text 1.9.1 ```
Project: YugabyteDB (App Definition and Development / Database)
File: role.md

title: ROLE linkTitle: ROLE description: ROLE menu: preview: parent: api-yedis weight: 2240 aliases: /preview/api/redis/role /preview/api/yedis/role type: docs YEDIS only has `master` role as far as Redis compatibility is concerned. `ROLE` This command provides information of a Redis instance, such as its role, its state of replication, its followers, or its master. Roles are either "master", "follower", or "sentinel". Information of a master instance may include the following. "master" An integer that represents state of replication An array of connected followers { IP address, IP port, State of replication } Information of a follower instance may include the following. "follower" Master IP address Master IP port Connection state that is either "disconnected", "connecting", "sync", or "connected" An integer that represents state of replication Information of a sentinel instance may include the following. "sentinel" An array of master names. Returns an array of values. ```sh $ ROLE ``` ``` 1) "master" 2) 0 3) 1) 1) "127.0.0.1" 2) "9200" 3) "0" 2) 1) "127.0.0.1" 2) "9201" 3) "0" ``` ,
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk_create.md

title: "operator-sdk create" Scaffold a Kubernetes API or webhook Scaffold a Kubernetes API or webhook. ``` -h, --help help for create ``` ``` --plugins strings plugin keys to be used for this subcommand execution --verbose Enable verbose logging ``` - - Scaffold a Kubernetes API - Scaffold a webhook for an API resource
Project: KICS (Provisioning / Security & Compliance)
File: 4b6012e7-7176-46e4-8108-e441785eae57.md

title: EBS Volume Encryption Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 4b6012e7-7176-46e4-8108-e441785eae57 Query name: EBS Volume Encryption Disabled Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: EBS volumes should be encrypted<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="24 19 12 5" name: Creating EBS volume01 amazon.aws.ec2_vol: instance: XXXXXX encrypted: no volume_size: 50 volume_type: gp2 device_name: /dev/xvdf name: Creating EBS volume02 amazon.aws.ec2_vol: instance: XXXXXX encrypted: false volume_size: 50 volume_type: gp2 device_name: /dev/xvdf name: Creating EBS volume03 amazon.aws.ec2_vol: instance: XXXXXX encrypted: "false" volume_size: 50 volume_type: gp2 device_name: /dev/xvdf name: Creating EBS volume04 amazon.aws.ec2_vol: instance: XXXXXX volume_size: 50 volume_type: gp2 device_name: /dev/xvdf ``` ```yaml title="Negative test num. 1 - yaml file" name: Creating EBS volume05 amazon.aws.ec2_vol: instance: XXXXXX encrypted: yes volume_size: 50 volume_type: gp2 device_name: /dev/xvdf name: Creating EBS volume06 amazon.aws.ec2_vol: instance: XXXXXX encrypted: 'True' volume_size: 50 volume_type: gp2 device_name: /dev/xvdf ```
Project: ArangoDB (App Definition and Development / Database)
File: static-constructor.md

+++ title = "Phase 2 construction" description = "" weight = 30 +++ Its phase 2 constructor: {{% snippet "constructors.cpp" "file" %}} The static member function implementing phase 2 firstly calls phase 1 which puts the object into a legally destructible state. We then proceed to implement phase 2 of construction, filling in the various parts as we go, reporting via `result` any failures. {{% notice note %}} Remember that `operator new` has a non-throwing form, `new(std::nothrow)`. {{% /notice %}} For the final return, in theory we could just `return ret` and depending on the C++ version currently in force, it might work via move, or via copy, or it might refuse to compile. You can of course type lots of boilerplate to be explicit, but this use via initialiser list is a reasonable balance of explicitness versus brevity, and it should generate minimum overhead code irrespective of compiler, C++ version, or any other factor.
Project: Apache Storm (App Definition and Development / Streaming & Messaging)
File: Project-ideas.md

layout: documentation DSLs for non-JVM languages:* These DSL's should be all-inclusive and not require any Java for the creation of topologies, spouts, or bolts. Since topologies are structs, Nimbus is a Thrift service, and bolts can be written in any language, this is possible. Online machine learning algorithms:* Something like but for online algorithms Suite of performance benchmarks:* These benchmarks should test Storm's performance on CPU and IO intensive workloads. There should be benchmarks for different classes of applications, such as stream processing (where throughput is the priority) and distributed RPC (where latency is the priority).
Project: ClickHouse (App Definition and Development / Database)
File: v21.3.17.2-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix a rare bug in `DROP PART` which can lead to the error `Unexpected merged part intersects drop range`. (). Backported in : Fix bug which can lead to error `Existing table metadata in ZooKeeper differs in sorting key expression.` after alter of `ReplicatedVersionedCollapsingMergeTree`. Fixes . (). Backported in : Fix benign race condition in ReplicatedMergeTreeQueue. Shouldn't be visible for user, but can lead to subtle bugs. (). Backported in : Fix reading of subcolumns from compact parts. (). Backported in : Fix higher-order array functions (`SIGSEGV` for `arrayCompact`/`ILLEGAL_COLUMN` for `arrayDifference`/`arrayCumSumNonNegative`) with consts. ().
Project: YDB (App Definition and Development / Database)
File: is-distinct-from.md

Comparing of two values. Unlike the regular , NULLs are treated as equal to each other. More precisely, the comparison is carried out according to the following rules: 1) The operators `IS DISTINCT FROM`/`IS NOT DISTINCT FROM` are defined for those and only for those arguments for which the operators `!=` and `=` are defined. 2) The result of `IS NOT DISTINCT FROM` is equal to the logical negation of the `IS DISTINCT FROM` result for these arguments. 3) If the result of the `==` operator is not equal to zero for some arguments, then it is equal to the result of the `IS NOT DISTINCT FROM` operator for the same arguments. 4) If both arguments are empty `Optional` or `NULL`s, then the value of `IS NOT DISTINCT FROM` is `True`. 5) The result of `IS NOT DISTINCT FROM` for an empty `Optional` or `NULL` and filled-in `Optional` or non-`Optional` value is `False`. For values of composite types, these rules are used recursively.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: README.md

<!-- 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. --> This directory provisions a redis cluster in Kubernetes. Follow terraform workflow convention to apply this module. It assumes the working directory is at . Initialize the terraform workspace. ``` DIR=02.redis terraform -chdir=$DIR init ``` Apply the terraform module. ``` DIR=02.redis terraform -chdir=$DIR apply -var-file=common.tfvars ```
Project: Pinniped (Provisioning / Key Management)
File: 2021-07-30-supporting-remote-oidc-workflows.md

title: "Pinniped v0.10.0: Managing OIDC Login Flows in Browserless Environments" slug: supporting-remote-oidc-workflows date: 2021-07-30 author: Anjali Telang image: https://images.unsplash.com/photo-1539830801588-496be8036aca?ixid=MnwxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8&ixlib=rb-1.2.1&auto=format&fit=crop&w=2250&q=80 excerpt: "With the release of v0.10.0, Pinniped now supports Kubernetes clusters behind firewalls or in restricted environments" tags: ['Matt Moyer', 'Anjali Telang', 'release'] Photo by on Enterprise workloads on Kubernetes clusters often run in a restricted environment behind a firewall. In such a setup, the clusters can be accessed via servers sometimes called SSH jump hosts. These servers pose restrictions on what the users can execute and typically allow only command line access. Users can use command line utilities such as kubectl, `pinniped` CLI, etc. on these servers to access the Kubernetes clusters. However, this poses a problem for the OIDC login workflows since they require a browser to complete the authentication workflow. In the , we introduce the ability to use a manual workaround to complete the OIDC workflow in such restricted browserless environments by supporting `responsemode=formpost` in the Pinniped Supervisor. As described in the , the response parameters are encoded as HTML form values that are auto-submitted in the User Agent, and thus are transmitted via the HTTP POST method to the Client. To complete the authentication process, The Pinniped users can copy and paste the response from the HTML page hosted by the Pinniped Supervisor into the waiting CLI process on the Jump Host. You can find more details in our . {{< youtube id="RZ7hdwRXx4E" title="New SSH jump host support in Pinniped v0.10.0" >}} Pinniped Concierge is installed with JWTAuthenticator on the Kubernetes cluster. Pinniped Supervisor is configured with OIDC Identity Provider on the Kubernetes cluster. Jump Host server/machine with Kubectl and Pinniped CLI is installed but has no web-browser. Desktop environment with a web browser for the User is available. Kubeconfig pointing to the Kubernetes cluster is available. User accesses the Jump Host via SSH. User initiates a kubectl command with kubeconfig pointing to the cluster. User is prompted to complete the login process using the Desktop web-browser. User competes the web-browser OIDC workflow and gets an authorization response code. User will copy-paste the authorization code into the Jump Host environment to complete the login. Additionally, the includes support for non-interactive password based LDAP logins. This feature provides the ability for Jenkins as well as other CI/CD tools that use LDAP Identity Platforms to access the cluster with centralized service account identities from the LDAP directory We invite your suggestions and contributions to make Pinniped work across all flavors of Kubernetes. {{< community >}}
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: Socket.md

Socket source connector Spark<br/> Flink<br/> SeaTunnel Zeta<br/> Used to read data from Socket. The File does not have a specific type list, and we can indicate which SeaTunnel data type the corresponding data needs to be converted to by specifying the Schema in the config. | SeaTunnel Data type | || | STRING | | SHORT | | INT | | BIGINT | | BOOLEAN | | DOUBLE | | DECIMAL | | FLOAT | | DATE | | TIME | | TIMESTAMP | | BYTES | | ARRAY | | MAP | | Name | Type | Required | Default | Description | |-||-||-| | host | String | Yes | _ | socket server host | | port | Integer | Yes | _ | socket server port | | common-options | | no | - | Source plugin common parameters, please refer to for details. | Configuring the SeaTunnel config file The following example demonstrates how to create a data synchronization job that reads data from Socket and prints it on the local client: ```bash env { parallelism = 1 job.mode = "BATCH" } source { Socket { host = "localhost" port = 9999 } } sink { Console { parallelism = 1 } } ``` Start a port listening ```shell nc -l 9999 ``` Start a SeaTunnel task Socket Source send test data ```text ~ nc -l 9999 test hello flink spark ``` Console Sink print data ```text [test] [hello] [flink] [spark] ```
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.1.2.2.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Unnecessary Configuration instantiation in IFileInputStream slows down merge - Port to branch-1 | Blocker | mrv1 | Stanislav Barton | Stanislav Barton | | | Map-only job with new-api runs wrong OutputCommitter when cleanup scheduled in a reduce slot | Blocker | client, job submission | Gera Shegalov | Gera Shegalov |