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

displayed_sidebar: "English" Obtains an arbitrary row from each aggregated group. You can use this function to optimize a query that has a `GROUP BY` clause. ```Haskell ANY_VALUE(expr) ``` `expr`: the expression that gets aggregated. Since v3.2, `expr` can evaluate to ARRAY, MAP, and STRUCT. Returns an arbitrary row from each aggregated group. The return value is non-deterministic. Create a table `t0` and insert data into this table. ```sql CREATE TABLE t0( a INT, b BIGINT, c SMALLINT, d ARRAY<INT>, e JSON, f MAP<INT, INT>, g STRUCT<a STRING, b INT> ) DUPLICATE KEY(a) DISTRIBUTED BY HASH(a); INSERT INTO t0 VALUES (1, 1, 1, [2,3,4],parse_json('{"a":1, "b":true}'), map{1:1,3:4}, row(1, 2)), (1, 2, 1, [2,3,5],parse_json('{"a":2, "b":true}'), map{1:2,3:3},row(2, 2)), (2, 1, 1, [2,3,6],parse_json('{"a":3, "b":true}'), map{2:1,3:2},row(3, 2)), (2, 2, 2, [2,4,5],parse_json('{"a":4, "b":false}'),map{1:3,3:1},row(4, 2)), (3, 1, 1, [3,3,5],parse_json('{"a":5, "b":false}'),map{2:1,3:3},row(1, 2)); ``` ```plain text mysql> select * from t0 order by a; +++++-+--+--+ | a | b | c | d | e | f | g | +++++-+--+--+ | 1 | 1 | 1 | [2,3,4] | {"a": 1, "b": true} | {1:1,3:4} | {"a":"1","b":2} | | 1 | 2 | 1 | [2,3,5] | {"a": 2, "b": true} | {1:2,3:3} | {"a":"2","b":2} | | 2 | 1 | 1 | [2,3,6] | {"a": 3, "b": true} | {2:1,3:2} | {"a":"3","b":2} | | 2 | 2 | 2 | [2,4,5] | {"a": 4, "b": false} | {1:3,3:1} | {"a":"4","b":2} | | 3 | 1 | 1 | [3,3,5] | {"a": 5, "b": false} | {2:1,3:3} | {"a":"1","b":2} | +++++-+--+--+ 5 rows in set (0.01 sec) ``` Use `any_value` for data query. For `a = 1` and `a = 2`, an arbitrary row is returned for `b`. ```plain text mysql> select a,any_value(b),sum(c) from t0 group by a; ++-+-+ | a | any_value(`b`) | sum(`c`) | ++-+-+ | 1 | 1 | 2 | | 2 | 1 | 3 | | 3 | 1 | 1 | ++-+-+ 3 rows in set (0.01 sec) mysql> select a,any_value(d),sum(b) from t0 group by a; ++--+--+ | a | any_value(d) | sum(b) | ++--+--+ | 3 | [3,3,5] | 1 | | 1 | [2,3,4] | 3 | | 2 | [2,3,6] | 3 | ++--+--+ 2 rows in set (0.01 sec) ```
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_use_space.md

title: "Command - devspace use space" sidebar_label: devspace use space Use an existing space for the current configuration ``` devspace use space [flags] ``` ``` Use an existing space for the current configuration Example: devspace use space my-space ``` ``` --get-token Prints the service token to the console -h, --help help for space --provider string The cloud provider to use --space-id string The space id to use ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile string The devspace profile to use (if there is any) --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```
Project: YugabyteDB (App Definition and Development / Database)
File: github.md

<!-- +++ private=true +++ --> Perform the following steps to install `yb_voyager` using an installer script: Clone the yb-voyager repository. ```sh git clone https://github.com/yugabyte/yb-voyager.git ``` Change the directory to `yb-voyager/installer_scripts`. ```sh cd yb-voyager/installer_scripts ``` Install yb-voyager using the following script: ```sh ./install-yb-voyager ``` It is safe to execute the script multiple times. If the script fails, check the `/tmp/install-yb-voyager.log` file. The script generates a `.yb-voyager.rc` file in the home directory. Source the file to ensure that the environment variables are set using the following command: ```sh source ~/.yb-voyager.rc ``` Check that yb-voyager is installed using the following command: ```sh yb-voyager version ```
Project: KICS (Provisioning / Security & Compliance)
File: 60587dbd-6b67-432e-90f7-a8cf1892d968.md

title: Public Security Group Rule All Ports or Protocols hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 60587dbd-6b67-432e-90f7-a8cf1892d968 Query name: Public Security Group Rule All Ports or Protocols Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: Alicloud Security Group Rule should not allow all ports or all protocols to the public<br> ```tf title="Positive test num. 1 - tf file" hl_lines="13" resource "alicloudsecuritygroup" "default" { name = "default" } resource "alicloudsecuritygrouprule" "allowall_tcp" { type = "ingress" ip_protocol = "all" nic_type = "internet" policy = "accept" port_range = "-1/-1" priority = 1 securitygroupid = alicloudsecuritygroup.default.id cidr_ip = "0.0.0.0/0" } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="13" resource "alicloudsecuritygroup" "default" { name = "default" } resource "alicloudsecuritygrouprule" "allowall_tcp" { type = "ingress" ip_protocol = "gre" nic_type = "internet" policy = "accept" port_range = "-1/-1" priority = 1 securitygroupid = alicloudsecuritygroup.default.id cidr_ip = "0.0.0.0/0" } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="13" resource "alicloudsecuritygroup" "default" { name = "default" } resource "alicloudsecuritygrouprule" "allowall_tcp" { type = "ingress" ip_protocol = "tcp" nic_type = "internet" policy = "accept" port_range = "1/65535" priority = 1 securitygroupid = alicloudsecuritygroup.default.id cidr_ip = "0.0.0.0/0" } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudsecuritygroup" "default" { name = "default" } resource "alicloudsecuritygrouprule" "allowall_tcp" { type = "ingress" ip_protocol = "tcp" nic_type = "internet" policy = "accept" port_range = "1/65535" priority = 1 securitygroupid = alicloudsecuritygroup.default.id cidr_ip = "10.159.6.18/12" } ``` ```tf title="Negative test num. 2 - tf file" resource "alicloudsecuritygroup" "default" { name = "default" } resource "alicloudsecuritygrouprule" "allowall_tcp" { type = "ingress" ip_protocol = "icmp" nic_type = "internet" policy = "accept" port_range = "-1/-1" priority = 1 securitygroupid = alicloudsecuritygroup.default.id cidr_ip = "10.159.6.18/12" } ```
Project: CyberArk Conjur (Provisioning / Key Management)
File: authn_ldap.md

Note: This design document has been ported from the original document . LDAP authentication allows a user to authenticate with Conjur using credentials stored in a remote LDAP source rather than their Conjur credentials. LDAP authentication works exactly as regular authentication, returning a JSON hash if the user authenticates successfully. To enable the authenticator, the `CONJURAUTHENTICATORS` environment variable must be set on any Conjur node that may be servicing the authentication request, and it must include the string `authn-ldap/<authenticator-name>` in its comma-separated list of allowed authenticators (for example, `CONJURAUTHENTICATORS=authn-iam/aws,authn-ldap/o365`). The authenticator webservice must be declared in Conjur policy: ```yml !policy id: conjur/authn-ldap/<authenticator-name> body: !webservice !group clients !permit role: !group clients privilege: [ read, authenticate ] resource: !webservice ``` and the `clients` group can be used to entitle a user(s) to use the authenticator: ```yml !grant role: !group conjur/authn-ldap/<authenticator-name>/clients member: !user <username> ``` Once the authenticator has been properly configured, a user will be able to configure their environment to use LDAP authorization through the the Conjur CLI client, UI, or when using Summon by setting the `CONJURAUTHNURL` environment variable: ``` CONJURAUTHNURL = https://conjur.company.com/authn-ldap/<authenticator-name>/<service-account>/<username>/authenticate ``` To successfully use the LDAP authenticator to authenticate to Conjur (if entitled to do so in Conjur policy), a user needs their Conjur User ID to match their LDAP username. The authenticator itself is a class `AuthnLdap` in `lib/authenticators`. It has an `authenticate` method that returns true if the username and password match LDAP, and otherwise returns false. ``` def authenticate(username, password) ``` The core routes will be updated to include ``` post ':authenticator/:service_id(/:account)/:login/authenticate' => 'authenticate#authenticate' ``` The core will be updated to define a `validatesecurityrequirements` method: ``` def validatesecurityrequirements serviceid, userid securityrequirements.validate(serviceid, user_id) end def security_requirements AuthenticatorSecurity.new( authntype: @authntype, account: @account, whitelistedauthenticators: ENV['CONJURAUTHENTICATORS'] ) end ``` and its `authenticate` method must be updated to query the custom authenticator instead of the standard authenticator when there is another authenticator in the request path. In addition, it must be checked that the custom authenticator meets the security standards, so this might look something like: ``` case params[:authenticator] when 'authn_ldap' validatesecurityrequirements service_id, username AuthnLdap.new.authenticate(username, password) else conjur_login(username, password) end ```
Project: StarRocks (App Definition and Development / Database)
File: SHOW_SNAPSHOT.md

displayed_sidebar: "English" Views data snapshots in a specified repository. For more information, see . ```SQL SHOW SNAPSHOT ON <repo_name> [WHERE SNAPSHOT = <snapshotname> [AND TIMESTAMP = <backuptimestamp>]] ``` | Parameter | Description | | - | - | | repo_name | Name of the repository that the snapshot belongs to. | | snapshot_nam | Name of the snapshot. | | backup_timestamp | Backup timestamp of the snapshot. | | Return | Description | | - | | | Snapshot | Name of the snapshot. | | Timestamp | Backup timestamp of the snapshot. | | Status | Displays `OK` if the snapshot is okay. Displays error message if the snapshot is not okay. | | Database | Name of the database that the snapshot belongs to. | | Details | JSON-formatted directory and structure of the snapshot. | Example 1: Views snapshots in repository `example_repo`. ```SQL SHOW SNAPSHOT ON example_repo; ``` Example 2: Views the snapshot named `backup1` in repository `example_repo`. ```SQL SHOW SNAPSHOT ON example_repo WHERE SNAPSHOT = "backup1"; ``` Example 3: Views the snapshot named `backup1` with backup timestamp `2018-05-05-15-34-26` in repository `example_repo`. ```SQL SHOW SNAPSHOT ON example_repo WHERE SNAPSHOT = "backup1" AND TIMESTAMP = "2018-05-05-15-34-26"; ```
Project: TDengine (App Definition and Development / Database)
File: 08-export.md

title: Data Export description: This document describes how to export data from TDengine. There are two ways of exporting data from a TDengine cluster: Using a SQL statement in TDengine CLI Using the `taosdump` tool If you want to export the data of a table or a STable, please execute the SQL statement below, in the TDengine CLI. ```sql select * from <tb_name> >> data.csv; ``` The data of table or STable specified by `tb_name` will be exported into a file named `data.csv` in CSV format. With `taosdump`, you can choose to export the data of all databases, a database, a table or a STable, you can also choose to export the data within a time range, or even only export the schema definition of a table. For the details of using `taosdump` please refer to the taosdump documentation.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: README.md

This package is a fork of the go-yaml library and is intended solely for consumption by kubernetes projects. In this fork, we plan to support only critical changes required for kubernetes, such as small bug fixes and regressions. Larger, general-purpose feature requests should be made in the upstream go-yaml library, and we will reject such changes in this fork unless we are pulling them from upstream. This fork is based on v2.4.0: https://github.com/go-yaml/yaml/releases/tag/v2.4.0 Introduction The yaml package enables Go programs to comfortably encode and decode YAML values. It was developed within as part of the project, and is based on a pure Go port of the well-known C library to parse and generate YAML data quickly and reliably. Compatibility The yaml package supports most of YAML 1.1 and 1.2, including support for anchors, tags, map merging, etc. Multi-document unmarshalling is not yet implemented, and base-60 floats from YAML 1.1 are purposefully not supported since they're a poor design and are gone in YAML 1.2. Installation and usage The import path for the package is gopkg.in/yaml.v2. To install it, run: go get gopkg.in/yaml.v2 API documentation -- If opened in a browser, the import path itself leads to the API documentation: API stability The package API for yaml v2 will remain stable as described in . License The yaml package is licensed under the Apache License 2.0. Please see the LICENSE file for details. Example ```Go package main import ( "fmt" "log" "gopkg.in/yaml.v2" ) var data = ` a: Easy! b: c: 2 d: [3, 4] ` // Note: struct fields must be public in order for unmarshal to // correctly populate the data. type T struct { A string B struct { RenamedC int `yaml:"c"` D []int `yaml:",flow"` } } func main() { t := T{} err := yaml.Unmarshal([]byte(data), &t) if err != nil { log.Fatalf("error: %v", err) } fmt.Printf(" t:\n%v\n\n", t) d, err := yaml.Marshal(&t) if err != nil { log.Fatalf("error: %v", err) } fmt.Printf(" t dump:\n%s\n\n", string(d)) m := make(map[interface{}]interface{}) err = yaml.Unmarshal([]byte(data), &m) if err != nil { log.Fatalf("error: %v", err) } fmt.Printf(" m:\n%v\n\n", m) d, err = yaml.Marshal(&m) if err != nil { log.Fatalf("error: %v", err) } fmt.Printf(" m dump:\n%s\n\n", string(d)) } ``` This example will generate the following output: ``` t: {Easy! {2 [3 4]}} t dump: a: Easy! b: c: 2 d: [3, 4] m: map[a:Easy! b:map[c:2 d:[3 4]]] m dump: a: Easy! b: c: 2 d: 3 4 ```
Project: ClickHouse (App Definition and Development / Database)
File: kafka_consumers.md

slug: /en/operations/system-tables/kafka_consumers Contains information about Kafka consumers. Applicable for (native ClickHouse integration) Columns: `database` (String) - database of the table with Kafka Engine. `table` (String) - name of the table with Kafka Engine. `consumerid` (String) - Kafka consumer identifier. Note, that a table can have many consumers. Specified by `kafkanum_consumers` parameter. `assignments.topic` (Array(String)) - Kafka topic. `assignments.partition_id` (Array(Int32)) - Kafka partition id. Note, that only one consumer can be assigned to a partition. `assignments.current_offset` (Array(Int64)) - current offset. `exceptions.time`, (Array(DateTime)) - timestamp when the 10 most recent exceptions were generated. `exceptions.text`, (Array(String)) - text of 10 most recent exceptions. `lastpolltime`, (DateTime) - timestamp of the most recent poll. `nummessagesread`, (UInt64) - number of messages read by the consumer. `lastcommittime`, (DateTime) - timestamp of the most recent poll. `num_commits`, (UInt64) - total number of commits for the consumer. `lastrebalancetime`, (DateTime) - timestamp of the most recent Kafka rebalance `numrebalancerevocations`, (UInt64) - number of times the consumer was revoked its partitions `numrebalanceassignments`, (UInt64) - number of times the consumer was assigned to Kafka cluster `iscurrentlyused`, (UInt8) - consumer is in use `rdkafkastat` (String) - library internal statistic. See https://github.com/ClickHouse/librdkafka/blob/master/STATISTICS.md . Set `statisticsinterval_ms` to 0 disable, default is 3000 (once in three seconds). Example: ``` sql SELECT * FROM system.kafka_consumers FORMAT Vertical ``` ``` text Row 1: database: test table: kafka consumer_id: ClickHouse-instance-test-kafka-1caddc7f-f917-4bb1-ac55-e28bd103a4a0 assignments.topic: ['systemkafkacons'] assignments.partition_id: [0] assignments.current_offset: [18446744073709550615] exceptions.time: [] exceptions.text: [] lastpolltime: 2006-11-09 18:47:47 nummessagesread: 4 lastcommittime: 2006-11-10 04:39:40 num_commits: 1 lastrebalancetime: 1970-01-01 00:00:00 numrebalancerevocations: 0 numrebalanceassignments: 1 iscurrentlyused: 1 rdkafka_stat: {...} ```
Project: CloudEvents (App Definition and Development / Streaming & Messaging)
File: avro-compact-format.md

The Avro Compact Format for CloudEvents defines how events are expressed in the . This differs from the in that: It is optimized for performance, preferring a more compact representation. It only supports spec version 1.0 (any changes to spec version requires changes to the Avro schema, which changes the fingerprint, breaking compatibility). It does not natively support JSON (JSON can be straight-forwardly serialized to bytes and this was therefore not considered necessary). is a standardized and protocol-agnostic definition of the structure and metadata description of events. This specification defines how the CloudEvents are to be represented as . The section describes the naming conventions and data type mappings for CloudEvents attributes for use as Avro message properties. This specification does not define an envelope format. The Avro type system's intent is primarily to provide a consistent type system for Avro itself and not for message payloads. The Avro event format does not currently define a batch mode format. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in . This section defines how CloudEvents attributes are mapped to the Avro type-system. This specification explicitly maps each attribute. The CloudEvents type system MUST be mapped to Avro types as follows. | CloudEvents | Avro | ||| | Boolean | | | Integer | | | String | | | Binary | | | URI | following | | URI-reference | following | | Timestamp | using `timestamp-micros` logical type | Extension specifications MAY define secondary mapping rules for the values of attributes they define, but MUST also include the previously defined primary mapping. Users of Avro MUST use a message whose binary encoding is identical to the one described by the . Transports that support content identification MUST use the following designation: ```text application/cloudevents+avro-compact ``` The following table shows exemplary mappings: | CloudEvents | Type | Exemplary Avro Value | |--|--|-| | id | string | `7a0dc520-c870-4193c8` | | source | string | `https://github.com/cloudevents` | | specversion | N/A | Spec version is always `1.0`. | | type | string | `com.example.object.deleted.v2` | | datacontenttype | string | `application/octet-stream` | | dataschema | string | `http://registry.com/schema/v1/much.json` | | subject | string | `mynewfile.jpg` | | time | long | `1685121689691000` | | data | bytes | `[bytes]` | Apache Avro 1.9.0 Specification
Project: OpenAPI (App Definition and Development / Application Definition & Image Build)
File: TOB.md

The TOB is responsible for managing conflicts, violations of procedures or guidelines or other issues that cannot be resolved in the TSC for the OAS. For further details please consult the OpenAPI Project Charter. Isabelle Mauny @isamauny Uri Sarid @usarid Marsh Gardiner @earth2marsh Ron Ratovsky @webron Darrel Miller @darrelmiller Jerome Louvel @jlouvel Jeremy Whitlock @whitlockjc
Project: in-toto (Provisioning / Security & Compliance)
File: ACKNOWLEDGEMENTS.md

in-toto is maintained by researchers at , the at as well as researchers from the at the . This research was supported by the US National Science Foundation (NSF), the Defense Advanced Research Projects Agency (DARPA) and the Air Force Research Laboratory (AFRL). Any opinions, findings, and conclusions or recommendations expressed in this material are those of the authors and do not necessarily reflect the views of NSF, DARPA and AFRL. The United States Government is authorized to reproduce and distribute reprints notwithstanding any copyright notice herein.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: CONTRIBUTING.md

First, thank you for contributing to KubeBlocks! This document provides guidelines for how to contribute to KubeBlocks. - - - - - - - Before contributing to KubeBlocks through issues and pull requests, make sure you are familiar with GitHub and the . To submit a proposed change, read the following workflow. Before you create a new issue, please search on the page to see if the issue or feature request has already been filed. If you find your issue already exists, make relevant comments or add your . If you can not find your issue exists, and open a new issue. Currently, there are 4 types of issues: Bug report: Youve found a bug with the code, and want to report or track the bug. Show more details, and let us know about an unexpected error, a crash, or an incorrect behavior. Feature request: Suggest a new feature. This allows feedback from others before the code is written. Improvement request: Suggest an improvement idea for this project. Use this issue type for document related improvements. Report a security vulnerability: Review our security policy first and then report a vulnerability. Fork the KubeBlocks repository to your GitHub account, create a new branch and clone to your host. Branch naming style should match the pattern: `feature/|bugfix/|release/|hotfix/|support/|dependabot/`. KubeBlocks performs a pull request check to verify the pull request branch name. See the for more information about setting up a KubeBlocks development environment. Make your changes. Update relevant documentation for the change. Make sure all tests and checks are passed. ```shell cd kubeblocks make reviewable ``` Submit the branch as a pull request to the main KubeBlocks repository. The pull request title must follow the format outlined in the . Because KubeBlocks squashes commits before merging branches, this means that the pull request title must conform to this format. KubeBlocks performs a pull request check to verify the pull request title in case you forget. The following are all good examples of pull request titles: ```shell feat(apps): add foo bar baz feature fix(kbcli): fix foo bar baz bug chore: tidy up Makefile docs: fix typos ``` Wait for the CI process to finish and make sure all checks are green. All pull requests should be reviewed and a pull request needs at least be approved by two maintainers before merging. All pull requests are squashed and merged. After the code review is finished, the pull request will be merged into the main branch. To protect all users of KubeBlocks, the following legal requirements are made. If you have additional questions, please contact us at `kubeblocks@apecloud.com`. KubeBlocks requires all contributors to sign the Contributor License Agreement (CLA). This gives KubeBlocks the rights to use your contributions as well as ensures that you own your contributions and can use them for other purposes. The full text of the CLA can be found at https://cla-assistant.io/apecloud/kubeblocks. This is covered by the CLA.