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

Evaluate an expression before the start of the main calculation and input its result to the query as a literal (constant). In many contexts, where only a constant would be expected in standard SQL (for example, in table names, in the number of rows in , and so on), this functionality is implicitly enabled automatically. EvaluateExpr can be used where the grammar already expects an expression. For example, you can use it to: Round the current time to days, weeks, or months and insert it into the query to ensure correct , although usually when , query caching is completely disabled. Run a heavy calculation with a small result once per query instead of once per job. EvaluateAtom lets you dynamically create an , but since atoms are mainly controlled from a lower level, it's generally not recommended to use this function directly. The only argument for both functions is the expression for calculation and substitution. Restrictions: The expression must not trigger MapReduce operations. This functionality is fully locked in YQL over YDB. Examples: ```yql $now = CurrentUtcDate(); SELECT EvaluateExpr( DateTime::MakeDate(DateTime::StartOfWeek($now) ) ); ```
Project: ClickHouse (App Definition and Development / Database)
File: quotas_usage.md

slug: /en/operations/system-tables/quotas_usage Quota usage by all users. Columns: `quota_name` () Quota name. `quota_key` () Key value. `is_current` () Quota usage for current user. `start_time` (())) Start time for calculating resource consumption. `end_time` (())) End time for calculating resource consumption. `duration` (()) Length of the time interval for calculating resource consumption, in seconds. `queries` (()) The total number of requests in this interval. `max_queries` (()) Maximum number of requests. `query_selects` (()) The total number of select requests in this interval. `maxqueryselects` (()) Maximum number of select requests. `query_inserts` (()) The total number of insert requests in this interval. `maxqueryinserts` (()) Maximum number of insert requests. `errors` (()) The number of queries that threw an exception. `max_errors` (()) Maximum number of errors. `result_rows` (()) The total number of rows given as a result. `maxresultrows` (()) Maximum of source rows read from tables. `result_bytes` (()) RAM volume in bytes used to store a queries result. `maxresultbytes` (()) Maximum RAM volume used to store a queries result, in bytes. `read_rows` (())) The total number of source rows read from tables for running the query on all remote servers. `maxreadrows` (()) Maximum number of rows read from all tables and table functions participated in queries. `read_bytes` (()) The total number of bytes read from all tables and table functions participated in queries. `maxreadbytes` (()) Maximum of bytes read from all tables and table functions. `failedsequentialauthentications` (()) The total count of sequential authentication failures. If the user entered the correct password before exceed `failedsequentialauthentications` threshold then the counter will be reset. `maxfailedsequential_authentications` (()) Maximum count of sequential authentication failures. `execution_time` (()) The total query execution time, in seconds (wall time). `maxexecutiontime` (()) Maximum of query execution time.
Project: kube-bench (Provisioning / Security & Compliance)
File: README.md

][release] ][release] ][docker] ][report-card] ](https://github.com/aquasecurity/kube-bench/actions) ](https://github.com/aquasecurity/kube-bench/blob/main/LICENSE) ][cov] <img src="docs/images/kube-bench.png" width="200" alt="kube-bench logo"> kube-bench is a tool that checks whether Kubernetes is deployed securely by running the checks documented in the . Tests are configured with YAML files, making this tool easy to update as test specifications evolve. , the all in one cloud native security scanner, can be deployed as a inside a cluster. Both, the , and the support CIS Kubernetes Benchmark scanning among several other features. There are multiple ways to run kube-bench. You can run kube-bench inside a pod, but it will need access to the host's PID namespace in order to check the running processes, as well as access to some directories on the host where config files and other files are stored. The supplied `job.yaml` can be applied to run the tests as a job. For example: ```bash $ kubectl apply -f job.yaml job.batch/kube-bench created $ kubectl get pods NAME READY STATUS RESTARTS AGE kube-bench-j76s9 0/1 ContainerCreating 0 3s $ kubectl get pods NAME READY STATUS RESTARTS AGE kube-bench-j76s9 0/1 Completed 0 11s kubectl logs kube-bench-j76s9 [INFO] 1 Master Node Security Configuration [INFO] 1.1 API Server ... ``` For more information and different ways to run kube-bench see kube-bench implements the as closely as possible. Please raise issues here if kube-bench is not correctly implementing the test as described in the Benchmark. To report issues in the Benchmark itself (for example, tests that you believe are inappropriate), please join the . There is not a one-to-one mapping between releases of Kubernetes and releases of the CIS benchmark. See to see which releases of Kubernetes are covered by different releases of the benchmark. By default, kube-bench will determine the test set to run based on the Kubernetes version running on the machine. see the following documentation on for more details. Kindly read before contributing. We welcome PRs and issue reports. Going forward we plan to release updates to kube-bench to add support for new releases of the CIS Benchmark. Note that these are not released as frequently as Kubernetes releases.
Project: Meshery (Provisioning / Automation & Configuration)
File: openkruise.md

layout: integration title: Openkruise subtitle: Collaborative and visual infrastructure as code for OpenEBS image: /assets/img/integrations/openkruise/icons/color/openkruise-color.svg permalink: extensibility/integrations/openkruise docURL: https://docs.meshery.io/extensibility/integrations/openkruise description: integrations-category: App Definition and Development integrations-subcategory: Continuous Integration & Delivery registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Druid (App Definition and Development / Database)
File: streaming.md

id: streaming title: "Streaming ingestion" <!-- ~ 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 can consume data streams from the following external streaming sources: Apache Kafka through the bundled extension. Amazon Kinesis through the bundled extension. Each indexing service provides real-time data ingestion with exactly-once stream processing guarantee. To use either of the streaming ingestion methods, you must first load the associated extension on both the Overlord and the MiddleManager. See for more information. Streaming ingestion is controlled by a continuously running . The supervisor oversees the state of indexing tasks to coordinate handoffs, manage failures, and ensure that scalability and replication requirements are maintained. You start a supervisor by submitting a JSON specification, often referred to as the supervisor spec, either though the Druid web console or using the .
Project: YugabyteDB (App Definition and Development / Database)
File: set_role,reset_role.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="394" height="70" viewbox="0 0 394 70"><path class="connector" d="M0 22h15m43 0h30m75 0h20m-105 25q0 5 5 5h5m59 0h21q5 0 5-5m-100-25q5 0 5 5v33q0 5 5 5h85q5 0 5-5v-33q0-5 5-5m5 0h10m52 0h30m84 0h20m-119 0q5 0 5 5v20q0 5 5 5h5m55 0h34q5 0 5-5v-20q0-5 5-5m5 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="43" height="25" rx="7"/><text class="text" x="25" y="22">SET</text><rect class="literal" x="88" y="5" width="75" height="25" rx="7"/><text class="text" x="98" y="22">SESSION</text><rect class="literal" x="88" y="35" width="59" height="25" rx="7"/><text class="text" x="98" y="52">LOCAL</text><rect class="literal" x="193" y="5" width="52" height="25" rx="7"/><text class="text" x="203" y="22">ROLE</text><a xlink:href="../../../syntaxresources/grammardiagrams#role-name"><rect class="rule" x="275" y="5" width="84" height="25"/><text class="text" x="285" y="22">role_name</text></a><rect class="literal" x="275" y="35" width="55" height="25" rx="7"/><text class="text" x="285" y="52">NONE</text><polygon points="390,29 394,29 394,15 390,15" style="fill:black;stroke-width:0"/></svg> <svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="151" height="35" viewbox="0 0 151 35"><path class="connector" d="M0 22h15m59 0h10m52 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="59" height="25" rx="7"/><text class="text" x="25" y="22">RESET</text><rect class="literal" x="84" y="5" width="52" height="25" rx="7"/><text class="text" x="94" y="22">ROLE</text><polygon points="147,29 151,29 151,15 147,15" style="fill:black;stroke-width:0"/></svg>
Project: YugabyteDB (App Definition and Development / Database)
File: zrevrange.md

title: ZREVRANGE linkTitle: ZREVRANGE description: ZREVRANGE menu: preview: parent: api-yedis weight: 2540 aliases: /preview/api/redis/zrevrange /preview/api/yedis/zrevrange type: docs `ZREVRANGE key start stop [WITHSCORES]` This command returns `members` ordered from highest to lowest score in the specified range at sorted set `key`. `start` and `stop` represent the high and low index bounds respectively and are zero-indexed. They can also be negative numbers indicating offsets from the beginning of the sorted set, with -1 being the first element of the sorted set, -2 the second element and so on. If `key` does not exist, an empty list is returned. If `key` is associated with non sorted-set data, an error is returned. Returns a list of members found in the range specified by `start`, `stop`, unless the WITHSCORES option is specified (see below). WITHSCORES: Makes the command return both the `member` and its `score`. You can do this as shown below. ```sh $ ZADD z_key 1.0 v1 2.0 v2 3.0 v3 ``` ``` (integer) 3 ``` ```sh $ ZREVRANGE z_key 0 2 ``` ``` 1) "v3" 2) "v2" 3) "v1" ``` With negative indices. ```sh $ ZREVRANGE z_key -2 -1 ``` ``` 1) "v2" 2) "v1" ``` Both positive and negative indices. ```sh $ ZREVRANGE z_key 1 -1 WITHSCORES ``` ``` 1) "v2" 2) "2.0" 3) "v1" 4) "1.0" ``` (0 and (2 are exclusive bounds. ```sh $ ZREVRANGE z_key (0 (2 ``` ``` (empty list or set) ``` Empty list returned if key doesn't exist. ```sh $ ZREVRANGE zkeyno_exist 0 2 WITHSCORES ``` ``` (empty list or set) ``` , , , ,
Project: KICS (Provisioning / Security & Compliance)
File: 97707503-a22c-4cd7-b7c0-f088fa7cf830.md

title: AMI Not Encrypted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 97707503-a22c-4cd7-b7c0-f088fa7cf830 Query name: AMI Not Encrypted Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: AWS AMI Encryption is not enabled<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="13 6" name: Basic AMI Creation amazon.aws.ec2_ami: instance_id: i-xxxxxx device_mapping: device_name: /dev/sda encrypted: no wait: yes name: newtest tags: Name: newtest Service: TestService name: Basic AMI Creation2 amazon.aws.ec2_ami: instance_id: i-xxxxxx device_mapping: device_name: /dev/sda wait: yes name: newtest tags: Name: newtest Service: TestService ``` ```yaml title="Negative test num. 1 - yaml file" name: Basic AMI Creation amazon.aws.ec2_ami: instance_id: i-xxxxxx device_mapping: device_name: /dev/sda encrypted: yes wait: yes name: newtest tags: Name: newtest Service: TestService ```
Project: YugabyteDB (App Definition and Development / Database)
File: data-types-ysql.md

title: Data types in YSQL headerTitle: Data types linkTitle: 3. Data types description: Learn about the data types in YSQL. menu: v2.18: identifier: data-types-2-ysql parent: learn weight: 565 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="../data-types-ysql/" class="nav-link active"> <i class="icon-postgres" aria-hidden="true"></i> YSQL </a> </li> <li > <a href="../data-types-ycql/" class="nav-link"> <i class="icon-cassandra" aria-hidden="true"></i> YCQL </a> </li> </ul> YSQL content coming soon.
Project: StarRocks (App Definition and Development / Database)
File: find_in_set.md

displayed_sidebar: "English" This function returns the position of the first str in strlist (start counting with 1). Strlist is a sting separated by commas. If it does not find any str, it returns 0. When the argument is NULL, the result is NULL. ```Haskell INT findinset(VARCHAR str, VARCHAR strlist) ``` ```Plain Text MySQL > select findinset("b", "a,b,c"); ++ | findinset('b', 'a,b,c') | ++ | 2 | ++ ``` FINDINSET,FIND,IN,SET
Project: external-secrets (Provisioning / Security & Compliance)
File: roadmap.md

The following external-secret custom resource APIs are considered stable: `ExternalSecret` `ClusterExternalSecret` `SecretStore` `ClusterSecretStore` These CRDs are currently at `v1beta1` and are considered production ready. Going forward, breaking changes to these APIs will be accompanied by a conversion mechanism. We have identified the following areas of work. This is subject to change while we gather feedback. We have a where we organize issues and milestones on a high level. Conformance testing end to end testing with ArgoCD and Flux end to end testing for all project maintained providers API enhancements consolidate provider fields dataFrom key rewrites provider versioning strategy pushing secrets to a provider Documentation Improvements Troubleshooting Guides FAQ review multi tenancy docs security model for infosec teams security best practices guide provider specific guides Observability Provide Grafana Dashboard and Prometheus alerts add provider-level metrics Pentest SBOM
Project: CockroachDB (App Definition and Development / Database)
File: README.md

``` docker-compose up -d ./import-csv.sh < (curl https://gist.githubusercontent.com/tbg/98d9814f624629833e6cfb7d25cb8258/raw/70a96d50032361f864b240dbd9f1c36c385b7515/sample.csv) open http://127.0.0.1:3000 ``` The source of this could be a `debug zip` (pending [#50432]), or `./cockroach debug tsdump --format=csv --host=... > dump.csv`. Not much more to be said. Unsurprisingly, this needs Docker to work. Omit the `-d` if you want to see what's going on behind the scenes. It may take a moment for the next step to work. This loads the CSV data into your local Postgres instance. Note that it will truncate any existing data you have imported, so you're not accidentally mixing metrics from various sources. If you legitimately want to import multiple csvs at once, use `cat *.csv | ./import-csv` instead. Log in as user `admin`, password `x`. You should be able to find a reference to the CockroachDB dashboard on the landing page. You can edit the provided panel or add panels to plot interesting metrics. A good starting point for learning how to do that is the [Grafana blog]. Replace ./grafana/dashboards/home.json if you want the changes to persist. TODO(tbg): auto-generate a better home.json from `pkg/ts/catalog`. To avoid hogging resources on your machine. The postgres database is on your local file system, so it will remain. If you want to nuke everything, use `down` instead of `stop` and then `git clean -f .`.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_kubeblocks.md

title: kbcli kubeblocks KubeBlocks operation commands. ``` -h, --help help for kubeblocks ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - List the changes between two different version KubeBlocks. - KubeBlocks config. - Describe KubeBlocks config. - Install KubeBlocks. - List KubeBlocks versions. - Run and retrieve preflight checks for KubeBlocks. - Show list of resource KubeBlocks uses or owns. - Uninstall KubeBlocks. - Upgrade KubeBlocks.
Project: ClickHouse (App Definition and Development / Database)
File: v21.12.4.1-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Create parent directories in DiskS3::restoreFileOperations method. (). Backported in : Fix null pointer dereference in low cardinality data when deserializing LowCardinality data in the Native format. (). Backported in : Fix ORC stripe reading. (). Backported in : Fix segfault in Avro that appears after the second insert into file. ().
Project: ShardingSphere (App Definition and Development / Database)
File: start-migration-check.en.md

+++ title = "START MIGRATION CHECK" weight = 12 +++ The `START MIGRATION CHECK` syntax is used to stop migration check process. {{< tabs >}} {{% tab name="Grammar" %}} ```sql StartMigrationCheck ::= 'START' 'MIGRATION' 'CHECK' migrationJobId migrationJobId ::= string ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} `migrationJobId` needs to be obtained through syntax query Stop migration check process ```sql START MIGRATION CHECK 'j010180026753ef0e25d3932d94d1673ba551'; ``` `START`, `MIGRATION`, `CHECK`
Project: YugabyteDB (App Definition and Development / Database)
File: config.md

title: CONFIG linkTitle: CONFIG description: CONFIG menu: preview: parent: api-yedis weight: 2030 type: docs YEDIS only supports the <code>CONFIG</code> command to set the required password(s) for client authentication. All other <code>CONFIG</code> requests would be accepted as valid command without further processing. To enable authentication, one can set a password that would be required for connections to communicate with the redis server. This is done using the following command: `CONFIG SET requirepass password[,password2]` Returns a status string. ```sh $ CONFIG SET requirepass "yugapass" ``` ``` "OK" ``` ```sh $ AUTH "yugapass" ``` ``` "OK" ``` ```sh $ AUTH "bad" ``` ``` "ERR: Bad Password." ``` ```sh $ CONFIG SET requirepass "yugapassA,yugapassB" ``` ``` "OK" ``` ```sh $ AUTH "yugapassA" ``` ``` "OK" ``` ```sh $ AUTH "yugapassB" ``` ``` "OK" ``` ```sh $ AUTH "yugapassC" ``` ``` "ERR: Bad Password." ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-volume-inspect.1.md

% podman-volume-inspect 1 podman\-volume\-inspect - Get detailed information on one or more volumes podman volume inspect [options] volume [...] Display detailed information on one or more volumes. The output can be formatted using the --format flag and a Go template. To get detailed information about all the existing volumes, use the --all flag. Volumes can be queried individually by providing their full name or a unique partial name. Inspect all volumes. Format volume output using Go template Valid placeholders for the Go template are listed below: | Placeholder | Description | | - | | | .Anonymous | Indicates whether volume is anonymous | | .CreatedAt ... | Volume creation time | | .Driver | Volume driver | | .GID | GID the volume was created with | | .Labels ... | Label information associated with the volume | | .LockNumber | Number of the volume's Libpod lock | | .MountCount | Number of times the volume is mounted | | .Mountpoint | Source of volume mount point | | .Name | Volume name | | .NeedsChown | Indicates volume needs to be chowned on first use | | .NeedsCopyUp | Indicates volume needs dest data copied up on first use| | .Options ... | Volume options | | .Scope | Volume scope | | .Status ... | Status of the volume | | .StorageID | StorageID of the volume | | .Timeout | Timeout of the volume | | .UID | UID the volume was created with | Print usage statement Inspect named volume. ``` $ podman volume inspect myvol [ { "Name": "myvol", "Driver": "local", "Mountpoint": "/home/myusername/.local/share/containers/storage/volumes/myvol/_data", "CreatedAt": "2023-03-13T16:26:48.423069028-04:00", "Labels": {}, "Scope": "local", "Options": {}, "MountCount": 0, "NeedsCopyUp": true, "NeedsChown": true } ] ``` Inspect all volumes. ``` $ podman volume inspect --all [ { "Name": "myvol", "Driver": "local", "Mountpoint": "/home/myusername/.local/share/containers/storage/volumes/myvol/_data", "CreatedAt": "2023-03-13T16:26:48.423069028-04:00", "Labels": {}, "Scope": "local", "Options": {}, "MountCount": 0, "NeedsCopyUp": true, "NeedsChown": true } ] ``` Inspect named volume and display its Driver and Scope field. ``` $ podman volume inspect --format "{{.Driver}} {{.Scope}}" myvol local local ``` , , November 2018, Originally compiled by Urvashi Mohnani <umohnani@redhat.com>