cwielenb/CNCF-Dataset huggingface dataset:
Project: Druid (App Definition and Development / Database)
File: delta-lake.md

id: delta-lake title: "Delta Lake 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. --> Delta Lake is an open source storage framework that enables building a Lakehouse architecture with various compute engines. lets you ingest data stored in a Delta Lake table into Apache Druid. To use the Delta Lake extension, add the `druid-deltalake-extensions` to the list of loaded extensions. See for more information. The Delta input source reads the configured Delta Lake table and extracts the underlying Delta files in the table's latest snapshot based on an optional Delta filter. These Delta Lake files are versioned Parquet files. The Delta Lake extension uses the Delta Kernel introduced in Delta Lake 3.0.0, which is compatible with Apache Spark 3.5.x. Older versions are unsupported, so consider upgrading to Delta Lake 3.0.x or higher to use this extension. To download `druid-deltalake-extensions`, run the following command after replacing `<VERSION>` with the desired Druid version: ```shell java \ -cp "lib/*" \ -Ddruid.extensions.directory="extensions" \ -Ddruid.extensions.hadoopDependenciesDir="hadoop-dependencies" \ org.apache.druid.cli.Main tools pull-deps \ --no-default-hadoop \ -c "org.apache.druid.extensions.contrib:druid-deltalake-extensions:<VERSION>" ``` See for more information. This extension relies on the Delta Kernel API and can only read from the latest Delta table snapshot. Ability to read from arbitrary snapshots is tracked .
Project: TDengine (App Definition and Development / Database)
File: 25-grant.md

title: User and Access Control sidebar_label: Access Control description: This document describes how to manage users and permissions in TDengine. User and Access control is a distingguished feature of TDengine enterprise edition. In this section, only the most fundamental functionalities of user and access control are demonstrated. To get the full knowledge of user and access control, please contact the TDengine team. ```sql CREATE USER user_name PASS 'password' [SYSINFO {1|0}]; ``` This statement creates a user account. The maximum length of user_name is 23 bytes. The maximum length of password is 31 bytes. The password can include leters, digits, and special characters excluding single quotation marks, double quotation marks, backticks, backslashes, and spaces. The password cannot be empty. `SYSINFO` indicates whether the user is allowed to view system information. `1` means allowed, `0` means not allowed. System information includes server configuration, dnode, vnode, storage. The default value is `1`. For example, we can create a user whose password is `123456` and is able to view system information. ```sql taos> create user test pass '123456' sysinfo 1; Query OK, 0 of 0 rows affected (0.001254s) ``` To show the users in the system, please use ```sql SHOW USERS; ``` This is an example: ```sql taos> show users; name | super | enable | sysinfo | create_time | ================================================================================ test | 0 | 1 | 1 | 2022-08-29 15:10:27.315 | root | 1 | 1 | 1 | 2022-08-29 15:03:34.710 | Query OK, 2 rows in database (0.001657s) ``` Alternatively, you can get the user information by querying a built-in table, INFORMATIONSCHEMA.INSUSERS. For example: ```sql taos> select * from informationschema.insusers; name | super | enable | sysinfo | create_time | ================================================================================ test | 0 | 1 | 1 | 2022-08-29 15:10:27.315 | root | 1 | 1 | 1 | 2022-08-29 15:03:34.710 | Query OK, 2 rows in database (0.001953s) ``` ```sql DROP USER user_name; ``` ```sql ALTER USER username alteruser_clause alteruserclause: { PASS 'literal' | ENABLE value | SYSINFO value } ``` PASS: Modify the user password. ENABLE: Specify whether the user is enabled or disabled. 1 indicates enabled and 0 indicates disabled. SYSINFO: Specify whether the user can query system information. 1 indicates that the user can query system information and 0 indicates that the user cannot query system information. For example, you can use below command to disable user `test`: ```sql taos> alter user test enable 0; Query OK, 0 of 0 rows affected (0.001160s) ``` Permission control is only available in TDengine Enterprise, please contact TDengine sales team.
Project: CDK for Kubernetes (CDK8s) (Provisioning / Automation & Configuration)
File: app.md

The `App` is the entry-point of your `cdk8s` application, and is the root of the constructs tree. Every application first starts by creating an instance of an `App`. ```ts import { App } from 'cdk8s'; const app = new App(); ``` Then, are registered into the app: ```ts new MyChart(app, 'Chart'); ``` And finally, the `app` is synthesized in order to produce the YAML manifests. Overall, your `cdk8s` application will have the following high level structure to it: ```ts import { App } from 'cdk8s'; // create the app entry-point const app = new App(); // register charts to the app new MyChart(app, 'Chart'); // synthesize the app app.synth(); ``` Resolvers are a mechanism to inject custom logic into the cdk8s value resolution process. It allows to transform any value just before being written to the Kubernetes manifest. For example, lets create a resolver that adds a prefix to every resource in our application. To define a custom resolver, create a class that implements the `IResolver` interface: ```ts import { IResolver, ResolutionContext } from 'cdk8s'; export class AddNamePrefixResolver implements IResolver { constructor(private readonly prefix: string) {} public resolve(context: ResolutionContext): void { // check if we are resolving the name property const isNameProperty = context.key.includes('metadata') && context.key.includes('name') && context.key.length === 2; // check we haven't already added a prefix. this is important because // resolution is recursive, so we need to avoid infinite recursion. const isPrefixed = typeof(context.value) === 'string' && context.value.startsWith(this.prefix); if (isNameProperty && !isPrefixed) { // replace the value with a new one context.replaceValue(`${this.prefix}${context.value}`); } } } ``` The `context` argument contains information about the value that is currently being resolved: obj: `ApiObject` currently being resolved. key: Array containing the JSON path elements of the keys leading up to the value. value: The original value. It also contains the `replaceValue` method you should use to set a replacement value instead of the original. When you create a cdk8s `App`, pass the resolver instance to it via the `resolvers` property: ```ts import { App, Chart } from 'cdk8s' const app = new App({ resolvers: [new AddNamePrefixResolver('custom-prefix')] }); new Chart(app, 'Chart'); ``` When you run `cdk8s synth`, your custom logic will be invoked, allowing you to replace the original value. When passing multiple resolvers, the first one (by natural order of the array) that invokes `replaceValue` is considered, and others are ignored. One common use-case for resolvers is to fetch values from deployed infrastructure. This allows authoring cdk8s applications that natively leverage managed cloud resources. To that end, two specific resolvers are available that allow you to integrate cdk8s with other CDK frameworks:
Project: KICS (Provisioning / Security & Compliance)
File: 5f670f9d-b1b4-4c90-8618-2288f1ab9676.md

title: NAS File System Without KMS hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 5f670f9d-b1b4-4c90-8618-2288f1ab9676 Query name: NAS File System Without KMS Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: NAS File System should have encryption provided by user KMS <br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "alicloudnasfile_system" "foo" { protocol_type = "NFS" storage_type = "Performance" description = "tf-testAccNasConfig" } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="5" resource "alicloudnasfile_system" "fooabr" { protocol_type = "NFS" storage_type = "Performance" description = "tf-testAccNasConfig" encrypt_type = "0" } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudnasfile_system" "foo" { protocol_type = "NFS" storage_type = "Performance" description = "tf-testAccNasConfig" encrypt_type = "2" kmskeyid = "1234abcd-12ab-34cd-56ef-1234567890ab" } ```
Project: Hazelcast Jet (App Definition and Development / Streaming & Messaging)
File: CONTRIBUTING.md

Thanks for your contribution to Hazelcast Jet. For issue reports, please share with us the following information to help us resolve your issue quickly and efficiently: Hazelcast Jet version that you use (e.g. 3.2 or 4.0-SNAPSHOT) Logs and stack traces where available. Description of the steps to reproduce your issue or a minimum reproducer for the issue, if possible If it's related to integration with an external system (i.e. Kafka) details about the external system and configuration parameters for connecting to it. Additional things that may be relevant: Java version. It is also helpful to mention the JVM parameters. Cluster size and configuration Operating system. If it is Linux, kernel version is helpful. PRs are the main way we accept contributions to Hazelcast Jet. If you're introducing a new source/sink connector, consider sending the PR to repository instead as it acts as an incubator for new Jet features. We have a PR review process where each PR is reviewed by the Jet development team. While your PR is being reviewed, you should sign the [Contributor Agreement Form] if this is your first contribution to Hazelcast or Hazelcast Jet. This is required to be completed before the PR is merged. The current development version is in the `master` branch. Patch versions are in the `n.n-maintenance` branches. Before you create the PR, run the command `mvn clean package -DskipTests` in your terminal and fix the CheckStyle and SpotBugs errors (if any). Tests will be run on our PR builder and can take very long time to run locally, so this is up to you if you want to do this on your own environment. Please keep your PRs as small as possible, i.e. if you plan to perform a huge change, do not submit a single and large PR for it. For an enhancement or larger feature, you can create a GitHub issue first to discuss. If you submit a PR as the solution to a specific issue, please mention the issue number either in the PR description or commit message. [Contributor Agreement Form]:https://hazelcast.atlassian.net/wiki/display/COM/Hazelcast+Contributor+Agreement
Project: Apache Heron (App Definition and Development / Streaming & Messaging)
File: LICENSE-normalize.css.md

Copyright Nicolas Gallagher and Jonathan Neal Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Project: Stolon (App Definition and Development / Database)
File: service_discovery.md

Service discovery helps in discovering stolon standby keepers for performing readonly queries `register` watches the keeper and registers them in `consul` for service discovery. `clients` which want to do readonly query can find the standby keepers by querying `consul` use `--register-master` flag to register master for performing readonly queries, don't use it for write queries, always use `proxy` to connect to master, refer for more info
Project: Chef Infra (Provisioning / Automation & Configuration)
File: resource_file_content_verification.md

File-based resources should be able to verify a file's content via user-supplied instructions before deploying the new content. The `verify` attribute of the `file`, `template`, `cookbook_file`, and `remote_file` resources will take a user-provided block or string. At converge time, a block will be passed the path to a temporary file holding the proposed content for the file. If the block returns `true`, the provider will continue to update the file on disk as appropriate. If the block returns `false`, the provider will raise an error. If a string argument to verify is passed, it will then be executed as a system command. If the command's return code indicates success -- 0 on unix-like system -- the provider will continue to update the file on disk as appropriate. If the command's return code indicates failure, the provider will raise an error. The path to the temporary file with the proposed content will be available by using Ruby's sprintf formatting: "%{path}" Other variables may be made available to commands in the future. If no verification block or string is supplied by the user, the provider assumes the content is valid. Multiple verify blocks may be provided by the user. All given verify block must pass before the content is deployed. As an example: ```ruby template "/tmp/foo" do verify do |path| true end end template "/tmp/wombat" do verify "/usr/bin/true" end template "/tmp/bar" do verify do |path| false end end template "/tmp/turtle" do verify "/usr/bin/false" end template "/tmp/baz" do verify { true } verify { 1 == 1 } end template "/tmp/bat" do verify { true } verify { 1 == 0 } end ``` Users could use this feature to shell out to tools, which check the configuration: ```ruby template "/etc/nginx.conf" do verify "nginx -t -c %{path}" end ``` Chef ships built-in verifiers for common content-types such as `:systemd_unit`, `:yaml` and `:json`. Built-in verifiers can be used by passing well-known symbols to the verify attribute: ```ruby template "/etc/config.json" do verify :json end ``` ```ruby template "/etc/config.yaml" do verify :yaml end ``` Typos and bugs in a template can lead Chef to render invalid configuration files on a node. In some cases, this will cause the related service to fail a notified restart and bring down the user's application. One hopes to catch such errors in testing, but that is not always possible. Many applications provide a means to verify a configuration file, but it is currently difficult to use these tools to verify a template without an elaborate series of resources chained together with notifications. https://tickets.opscode.com/browse/CHEF-4416 https://tickets.opscode.com/browse/CHEF-3634
Project: StarRocks (App Definition and Development / Database)
File: ngram_search.md

displayed_sidebar: "English" Calculate the ngram similarity of the two strings. :::info Currently, the character encoding only supports ASCII encoding and does not support UTF-8 encoding. The function `ngramsearch` is case-sensitive. Another function `ngramsearchcaseinsensitive` is case-insensitive. Other than that, these two functions are the same. ::: ```sql DOUBLE ngramsearch(VARCHAR haystack, VARCHAR needle, INT gramnum) ``` `haystack`: required, the first string to compare. It must be a VARCHAR value. It can be a column name or a const value. If `haystack` is a column name, and an N-Gram bloom filter index is created for that column in the table, the index can accelerate the computation speed of the `ngram_search` function. `needle`: required, the second string to compare. It must be a VARCHAR value. It can only be a const value. :::tip The length of the `needle` value can not be larger than 2^15. Otherwise an error will be thrown. If the length of the `haystack` value is larger than 2^15, this function will return 0. If the length of the `haystack` or `needle` value is smaller than `gram_num`, this function will return 0. ::: `gram_num`: required, used for specifying the number of grams. The recommended value is `4`. Returns a value describing how similar these two strings are. The range of returned value is between 0 and 1. The larger this value, the more similar the two strings are. ```SQL -- The values of haystack and needle are const values. mysql> select ngram_search('English', 'England',4); ++ | ngram_search('English', 'England', 4) | ++ | 0.25 | ++ -- The value of haystack is a column name and the value of needle is a const value. mysql> select rowkey,ngramsearch(rowkey,"31dc496b-760d-6f1a-4521-050073a70000",4) as stringsimilarity from stringtable order by stringsimilarity desc limit 5; +--+-+ | rowkey | string_similarity | +--+-+ | 31dc496b-760d-6f1a-4521-050073a70000 | 1 | | 31dc496b-760d-6f1a-4521-050073a40000 | 0.8787879 | | 31dc496b-760d-6f1a-4521-05007fa70000 | 0.8787879 | | 31dc496b-760d-6f1a-4521-050073a30000 | 0.8787879 | | 31dc496b-760d-6f1a-4521-0500c3a70000 | 0.8787879 | +--+-+ ```
Project: YugabyteDB (App Definition and Development / Database)
File: listdb.md

title: LISTDB linkTitle: LISTDB description: LISTDB menu: preview: parent: api-yedis weight: 2036 aliases: /preview/api/yedis/listdb type: docs `LISTDB` is used to list all the yedis database(s) available for use. All databases other than the default database ("0") need to be created using the `CREATEDB` command before use. A client can issue the `LISTDB` command through the redis-cli. Returns an array of string values, with the yedis database names. ```sh $ LISTDB ``` ``` 1) "0" ``` ```sh $ CREATEDB "second" ``` ``` "OK" ``` ```sh $ LISTDB ``` ``` 1) "0" 2) "second" ``` ```sh $ CREATEDB "3.0" ``` ``` "OK" ``` ```sh $ LISTDB ``` ``` 1) "0" 2) "3.0" 3) "second" ``` ```sh $ DELETEDB "3.0" ``` ``` "OK" ``` ```sh $ LISTDB ``` ``` 1) "0" 2) "second" ```
Project: StarRocks (App Definition and Development / Database)
File: bit_shift_right_logical.md

displayed_sidebar: "English" Shifts the binary representation of a numeric expression to the right by a specified number of bits. This function performs an arithmetic right shift, during which the bit length does not change, the low bit is dropped, and the sign bit is used as the high bit. For example, shifting `10101` to the right by one bit results in `11010`. ```Haskell bitshiftright(value, shift) ``` `value`: the value or numeric expression to shift. Supported data types are TINYINT, SMALLINT, INT, BIGINT, and LARGEINT. `shift`: the number of bits to shift. The supported data type is BIGINT. The supported data type is BIGINT. Returns a value of the same type as `value`. If any input parameter is NULL, NULL is returned. If `shift` is less than 0, 0 is returned. Shifting a `value` by `0` always results in the original `value`. Shifting `0` by a `shift` always results in `0`. If the data type of `value` is numeric but not an integer, that value will be cast to an integer. See . If the data type of `value` is a string, the value will be cast to an integer if possible. For example, the string "2.3" will be cast to 2. If the value cannot be cast to an integer, the value will be treated as NULL. See . Use this function to shift numeric values. ```Plain SELECT bitshiftright(2, 1); +--+ | bitshiftright(2, 1) | +--+ | 1 | +--+ SELECT bitshiftright(2.2, 1); +-+ | bitshiftright(2.2, 1) | +-+ | 1 | +-+ SELECT bitshiftright("2", 1); +-+ | bitshiftright('2', 1) | +-+ | 1 | +-+ SELECT bitshiftright(-2, 1); ++ | bitshiftright(-2, 1) | ++ | -1 | ++ ```
Project: Pomerium (Provisioning / Key Management)
File: README.md

A tiny go http server that enforces client certificates and can be used to test mutual TLS with Pomerium. ```yaml authenticateserviceurl: https://authenticate.corp.domain.example authorizeserviceurl: https://authorize.corp.domain.example idp_provider: google idpclientid: REPLACE_ME idpclientsecret: REPLACE_ME routes: from: https://mtls.corp.domain.example to: https://localhost:8443 policy: allow: or: domain: is: domain.example tlscustomca_file: "/Users/bdd/examples/mutual-tls/out/good-ca.crt" tlsclientcert_file: "/Users/bdd/examples/mutual-tls/out/pomerium.crt" tlsclientkey_file: "/Users/bdd/examples/mutual-tls/out/pomerium.key" from: https://verify.corp.domain.example to: https://verify.pomerium.com allowpublicunauthenticated_access: true ``` ```yaml version: "3" services: pomerium: image: pomerium/pomerium:latest environment: CERTIFICATE CERTIFICATE_KEY COOKIE_SECRET volumes: ./example.config.yaml:/pomerium/config.yaml:ro ports: 443:443 mtls: image: pomerium/examples:mtls environment: TLS_CERT TLS_KEY CLIENT_CA ports: 8443:8443 ``` This can be done a myriad of ways. The easiest for testing is probably using . See Certificates can be set using the following base 64 encoded . For example, ```bash source ./env && go run main.go ``` See Pull `pomerium/examples:mtls` or see See