cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-aux-show-tables.md

layout: global title: SHOW TABLES displayTitle: SHOW TABLES license: | 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. The `SHOW TABLES` statement returns all the tables for an optionally specified database. Additionally, the output of this statement may be filtered by an optional matching pattern. If no database is specified then the tables are returned from the current database. ```sql SHOW TABLES [ { FROM | IN } databasename ] [ LIKE regexpattern ] ``` { FROM `|` IN } database_name* Specifies the database name from which tables are listed. regex_pattern* Specifies the regular expression pattern that is used to filter out unwanted tables. Except for `` and `|` character, the pattern works like a regular expression. `` alone matches 0 or more characters and `|` is used to separate multiple different regular expressions, any of which can match. The leading and trailing blanks are trimmed in the input pattern before processing. The pattern match is case-insensitive. ```sql -- List all tables in default database SHOW TABLES; +--++--+ |database|tableName|isTemporary| +--++--+ | default| sam| false| | default| sam1| false| | default| suj| false| +--++--+ -- List all tables from userdb database SHOW TABLES FROM userdb; +--++--+ |database|tableName|isTemporary| +--++--+ | userdb| user1| false| | userdb| user2| false| +--++--+ -- List all tables in userdb database SHOW TABLES IN userdb; +--++--+ |database|tableName|isTemporary| +--++--+ | userdb| user1| false| | userdb| user2| false| +--++--+ -- List all tables from default database matching the pattern `sam*` SHOW TABLES FROM default LIKE 'sam*'; +--++--+ |database|tableName|isTemporary| +--++--+ | default| sam| false| | default| sam1| false| +--++--+ -- List all tables matching the pattern `sam*|suj` SHOW TABLES LIKE 'sam*|suj'; +--++--+ |database|tableName|isTemporary| +--++--+ | default| sam| false| | default| sam1| false| | default| suj| false| +--++--+ ```
Project: SlimToolkit (Provisioning / Security & Compliance)
File: UPGRADING.md

v3 introduced using `!` to negate character classes, in addition to `^`. If any of your patterns include a character class that starts with an exclamation mark (ie, `[!...]`), you'll need to update the pattern to escape or move the exclamation mark. Note that, like the caret (`^`), it only negates the character class if it is the first character in the character class. The change from v1 to v2 was fairly minor: the return type of the `Open` method on the `OS` interface was changed from `*os.File` to `File`, a new interface exported by doublestar. The new `File` interface only defines the functionality doublestar actually needs (`io.Closer` and `Readdir`), making it easier to use doublestar with , , or something similar. If you were using this functionality, updating should be as easy as updating `Open's` return type, since `os.File` already implements `doublestar.File`. If you weren't using this functionality, updating should be as easy as changing your dependencies to point to v2.
Project: CloudEvents (App Definition and Development / Streaming & Messaging)
File: severity.md

This extension defines attributes that MAY be included within a CloudEvent to describe the "severity" or "level" of an event in relation to other events. Often systems produce events in form of logs, and these types of events usually share a common concept of "log-level". This extension aims to provide a standard way for describing this property in a language agnostic form. Sharing a common way to describe severity of events allows for better monitoring systems, tooling and general log consumption. This extension is heavily inspired by the and is intended to interoperate with them. As with the main , 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 . However, the scope of these key words is limited to when this extension is used. For example, an attribute being marked as "REQUIRED" does not mean it needs to be in all CloudEvents, rather it needs to be included only when this extension is being used. When both attributes are used, all `severitytext` values which MAY be produced in a context of a `source` SHOULD be in a relationship with all `severitynumber` values which MAY be produced by the same `source`. Type: `String` Description: Human readable text representation of the event severity (also known as log level name). This is the original string representation of the severity as it is known at the source. If this field is missing and `severitynumber` is present then the that corresponds to the `severitynumber` MAY be used as a substitution. Constraints OPTIONAL if present, MUST be a non-empty string SHOULD be uppercase RECOMMENDED values are `TRACE`, `DEBUG`, `INFO`, `WARN`, `ERROR`, and `FATAL`, but others MAY be used. Type: `Integer` Description: Numerical representation of the event severity (also known as log level number), normalized to values described in this document. Severity of all values MUST be numerically ascending from least-severe to most-severe. An event with a lower numerical value (such as a debug event) MUST be less severe than an event with a higher numerical value (such as an error event). See OpenTelemetry for Constraints REQUIRED if present, MUST NOT be negative - - -
Project: KICS (Provisioning / Security & Compliance)
File: 66c6f96f-2d9e-417e-a998-9058aeeecd44.md

title: S3 Bucket Allows List Action From All Principals hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 66c6f96f-2d9e-417e-a998-9058aeeecd44 Query name: S3 Bucket Allows List Action From All Principals Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: S3 Buckets must not allow List Action From All Principals, as to prevent leaking private information to the entire internet or allow unauthorized data tampering / deletion. This means the 'Effect' must not be 'Allow' when the 'Action' is List, for all Principals.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="4" resource "awss3bucket_policy" "positive1" { bucket = awss3bucket.b.id policy = <<POLICY { "Version": "2012-10-17", "Id": "MYBUCKETPOLICY", "Statement": [ { "Sid": "IPAllow", "Effect": "Allow", "Principal": "*", "Action": "s3:ListObjects", "Resource": "arn:aws:s3:::mytftest_bucket/*", "Condition": { "IpAddress": {"aws:SourceIp": "8.8.8.8/32"} } } ] } POLICY } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="4" resource "awss3bucket_policy" "positive2" { bucket = awss3bucket.b.id policy = <<POLICY { "Version": "2012-10-17", "Id": "MYBUCKETPOLICY", "Statement": [ { "Sid": "IPAllow", "Effect": "Allow", "Principal": { "AWS": "*" }, "Action": "s3:ListObjects", "Resource": "arn:aws:s3:::mytftest_bucket/*", "Condition": { "IpAddress": {"aws:SourceIp": "8.8.8.8/32"} } } ] } POLICY } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="12" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" versioning = { enabled = true } policy = <<POLICY { "Version": "2012-10-17", "Id": "MYBUCKETPOLICY", "Statement": [ { "Sid": "IPAllow", "Effect": "Allow", "Principal": { "AWS": "*" }, "Action": "s3:ListObjects", "Resource": "arn:aws:s3:::mytftest_bucket/*", "Condition": { "IpAddress": {"aws:SourceIp": "8.8.8.8/32"} } } ] } POLICY } ``` ```tf title="Negative test num. 1 - tf file" resource "awss3bucket_policy" "negative1" { bucket = awss3bucket.b.id policy = <<POLICY { "Version": "2012-10-17", "Id": "MYBUCKETPOLICY", "Statement": [ { "Sid": "IPAllow", "Effect": "Deny", "Action": "s3:*", "Resource": "arn:aws:s3:::mytftest_bucket/*", "Condition": { "IpAddress": {"aws:SourceIp": "8.8.8.8/32"} } } ] } POLICY } ``` ```tf title="Negative test num. 2 - tf file" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" versioning = { enabled = true } policy = <<POLICY { "Version": "2012-10-17", "Id": "MYBUCKETPOLICY", "Statement": [ { "Sid": "IPAllow", "Effect": "Deny", "Action": "s3:*", "Resource": "arn:aws:s3:::mytftest_bucket/*", "Condition": { "IpAddress": {"aws:SourceIp": "8.8.8.8/32"} } } ] } POLICY } ```
Project: Packer (App Definition and Development / Application Definition & Image Build)
File: PULL_REQUEST_TEMPLATE.md

DELETE THIS TEMPLATE BEFORE SUBMITTING In order to have a good experience with our community, we recommend that you read the contributing guidelines for making a PR, and understand the lifecycle of a Packer PR: https://github.com/hashicorp/packer/blob/master/.github/CONTRIBUTING.md#opening-an-pull-request Describe the change you are making here! Please include tests. Check out these examples: https://github.com/hashicorp/packer/blob/master/builder/parallels/common/sshconfigtest.go#L34 https://github.com/hashicorp/packer/blob/master/post-processor/compress/post-processor_test.go#L153-L182 If your PR resolves any open issue(s), please indicate them like this so they will be closed when your PR is merged: Closes #xxx Closes #xxx
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: apache-apisix.md

title: Authorization Integration with Apache APISIX software: apache-apisix labels: category: gateway layer: network code: https://github.com/apache/apisix blogs: https://apisix.apache.org/blog/2021/12/24/open-policy-agent https://medium.com/@ApacheAPISIX/apache-apisix-integrates-with-open-policy-agent-to-enrich-its-ecosystem-15569fe3ab9c docs_features: rest-api-integration: note: | Apache APISIX routes can be configured to call an OPA instance over the REST API. explains how such a configuration can be achieved. Apache APISIX provides a plugin for delegating fine-grained authorization decisions to OPA.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: stop-start-a-redis-cluster.md

title: Stop/Start a Redis cluster description: How to start/stop a Redis cluster keywords: [redis, stop a cluster, start a cluster] sidebar_position: 5 sidebar_label: Stop/Start You can stop/start a cluster to save computing resources. When a cluster is stopped, the computing resources of this cluster are released, which means the pods of Kubernetes are released, but the storage resources are reserved. Start this cluster again if you want to restore the cluster resources from the original storage by snapshots. Configure the name of your cluster and run the command below to stop this cluster. ```bash kbcli cluster stop <name> ``` *Example* ```bash kbcli cluster stop redis-cluster ``` Run the command below to stop a cluster. ```bash kubectl apply -f - <<EOF apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: stop- spec: clusterRef: redis-cluster type: Stop EOF ``` Configure replicas as 0 to delete pods. ```yaml apiVersion: apps.kubeblocks.io/v1alpha1 kind: Cluster metadata: name: redis-cluster spec: clusterDefinitionRef: redis clusterVersionRef: redis-7.0.6 terminationPolicy: Delete componentSpecs: name: redis componentDefRef: redis monitor: true replicas: 0 volumeClaimTemplates: name: data spec: storageClassName: standard accessModes: ReadWriteOnce resources: requests: storage: 1Gi name: redis-sentinel componentDefRef: redis-sentinel monitor: true replicas: 0 volumeClaimTemplates: name: data spec: storageClassName: standard accessModes: ReadWriteOnce resources: requests: storage: 1Gi ``` Configure the name of your cluster and run the command below to start this cluster. ```bash kbcli cluster start <name> ``` *Example* ```bash kbcli cluster start redis-cluster ``` Run the command below to start a cluster. ```yaml kubectl apply -f - <<EOF apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: start- spec: clusterRef: redis-cluster type: Start EOF ``` Change replicas back to the original amount to start this cluster again. ```yaml apiVersion: apps.kubeblocks.io/v1alpha1 kind: Cluster metadata: name: redis-cluster spec: clusterDefinitionRef: redis clusterVersionRef: redis-7.0.6 terminationPolicy: Delete componentSpecs: name: redis componentDefRef: redis monitor: true replicas: 2 volumeClaimTemplates: name: data spec: storageClassName: standard accessModes: ReadWriteOnce resources: requests: storage: 1Gi name: redis-sentinel componentDefRef: redis-sentinel monitor: true replicas: 3 volumeClaimTemplates: name: data spec: storageClassName: standard accessModes: ReadWriteOnce resources: requests: storage: 1Gi ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.8.32.md

RabbitMQ `3.8.32` is a maintenance release. All users are recommended to upgrade to this release. RabbitMQ releases are distributed via , , and . This release and . explains what package repositories and tools can be used to provision modern Erlang versions. See the for general documentation on upgrades and for release notes of other releases. If upgrading from a `3.7.x` release, see upgrade and compatibility notes first. If upgrading from a `3.6.x` or older , first upgrade to and then to this version. Any questions about this release, upgrades or RabbitMQ in general are welcome on the and . Release notes can be found on GitHub at . Configuration of fallback secrets for Shovel and Federation credential obfuscation. This feature allows for secret rotation during rolling cluster node restarts. Contributed by Lajos @luos Gerecs. GitHub issue: `rabbitmq-diagnostics status` now reports crypto library (OpenSSL, LibreSSL, etc) used by the runtime, as well as its version details. GitHub issue: CLI tools failed to run on Erlang 25 because of an old version of Elixir (compiled on Erlang 21) was used in the release pipeline. Erlang 25 no longer loads modules compiled on Erlang 21 or older. `rabbitmqctl setloglevel` documentation clarification. Contributed by Pter @gomoripeti Gmri (CloudAMQP). GitHub issue: `aten` was upgraded `credentials_obfuscation` was upgraded To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.8.32.tar.xz` instead of the source tarball produced by GitHub.
Project: KICS (Provisioning / Security & Compliance)
File: 66f130d9-b81d-4e8e-9b08-da74b9c891df.md

title: Missing Cluster Log Types hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 66f130d9-b81d-4e8e-9b08-da74b9c891df Query name: Missing Cluster Log Types Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Amazon EKS control plane logging don't enabled for all log types<br> ```tf title="Positive test num. 1 - tf file" hl_lines="9" variable "cluster_name" { default = "example" type = string } resource "awsekscluster" "positive1" { dependson = [awscloudwatchloggroup.example] enabledclusterlog_types = ["api", "audit"] name = var.cluster_name } resource "awscloudwatchlog_group" "positive2" { name = "/aws/eks/${var.cluster_name}/cluster" retentionindays = 7 } ``` ```tf title="Negative test num. 1 - tf file" variable "cluster_name" { default = "example" type = string } resource "awsekscluster" "negative1" { dependson = [awscloudwatchloggroup.example] enabledclusterlog_types = ["api", "audit", "authenticator", "controllerManager", "scheduler"] name = var.cluster_name } resource "awscloudwatchlog_group" "negative2" { name = "/aws/eks/${var.cluster_name}/cluster" retentionindays = 7 } ```
Project: YDB (App Definition and Development / Database)
File: ip.md

The `Ip` module supports both the IPv4 and IPv6 addresses. By default, they are represented as binary strings of 4 and 16 bytes, respectively. List of functions ```Ip::FromString(String{Flags:AutoMap}) -> String?``` - From a human-readable representation to a binary representation. ```Ip::SubnetFromString(String{Flags:AutoMap}) -> String?``` - From a human-readable representation of subnet to a binary representation. ```Ip::ToString(String{Flags:AutoMap}) -> String?``` - From a binary representation to a human-readable representation. ```Ip::SubnetToString(String{Flags:AutoMap}) -> String?``` - From a binary representation of subnet to a human-readable representation. ```Ip::IsIPv4(String?) -> Bool``` ```Ip::IsIPv6(String?) -> Bool``` ```Ip::IsEmbeddedIPv4(String?) -> Bool``` ```Ip::ConvertToIPv6(String{Flags:AutoMap}) -> String```: IPv6 remains unchanged, and IPv4 becomes embedded in IPv6 ```Ip::GetSubnet(String{Flags:AutoMap}, [Uint8?]) -> String```: The second argument is the subnet size, by default it's 24 for IPv4 and 64 for IPv6 ```Ip::GetSubnetByMask(String{Flags:AutoMap}, String{Flags:AutoMap}) -> String```: The first argument is the base address, the second argument is the bit mask of a desired subnet. ```Ip::SubnetMatch(String{Flags:AutoMap}, String{Flags:AutoMap}) -> Bool```: The first argument is a subnet, the second argument is a subnet or an address. Examples ```sql SELECT Ip::IsEmbeddedIPv4( Ip::FromString("::ffff:77.75.155.3") ); -- true SELECT Ip::ToString( Ip::GetSubnet( Ip::FromString("213.180.193.3") ) ); -- "213.180.193.0" SELECT Ip::SubnetMatch( Ip::SubnetFromString("192.168.0.1/16"), Ip::FromString("192.168.1.14"), ); -- true SELECT Ip::ToString( Ip::GetSubnetByMask( Ip::FromString("192.168.0.1"), Ip::FromString("255.255.0.0") ) ); -- "192.168.0.0" ```
Project: ClickHouse (App Definition and Development / Database)
File: maxintersectionsposition.md

slug: /en/sql-reference/aggregate-functions/reference/maxintersectionsposition sidebar_position: 361 title: maxIntersectionsPosition Aggregate function that calculates the positions of the occurrences of the . The syntax is: ```sql maxIntersectionsPosition(startcolumn, endcolumn) ``` Arguments `startcolumn` the numeric column that represents the start of each interval. If `startcolumn` is `NULL` or 0 then the interval will be skipped. `endcolumn` - the numeric column that represents the end of each interval. If `endcolumn` is `NULL` or 0 then the interval will be skipped. Returned value Returns the start positions of the maximum number of intersected intervals. Example ```sql CREATE TABLE my_events ( start UInt32, end UInt32 ) Engine = MergeTree ORDER BY tuple(); INSERT INTO my_events VALUES (1, 3), (1, 6), (2, 5), (3, 7); ``` The intervals look like the following: ```response 1 - 3 1 - - - - 6 2 - - 5 3 - - - 7 ``` Notice that three of these intervals have the value 4 in common, and that starts with the 2nd interval: ```sql SELECT maxIntersectionsPosition(start, end) FROM my_events; ``` Response: ```response 2 ``` In other words, the `(1,6)` row is the start of the 3 intervals that intersect, and 3 is the maximum number of intervals that intersect.
Project: VMClarity (Provisioning / Security & Compliance)
File: README.md

KICS is a scanner application that uses (Keeping Infrastructure as Code Secure) to scan your Infrastructure as Code (IaC) files for misconfigurations. It's designed to be used as a plugin for the platform. Make a POST request with config below to the VMClarity API `/assetScans` endpoint to initiate a KICS scan. The body of the POST request should include a JSON object with the configuration for the scan. NOTE: Below is a minimal example. Your actual configuration should have additional properties. ```json { "name": "scan-name", "scanTemplate": { "scope": "contains(assetInfo.labels, '{\"key\":\"scanconfig\",\"value\":\"test\"}')", "assetScanTemplate": { "scanFamiliesConfig": { "plugins": { // TODO(ramizpolic): Update with request data once decided in plugin integrations work } } } } } ``` The KICS scanner is designed to be started by VMClarity, therefore running it as a standalone tool is not recommended. The value of the `scannerConfig` property in the POST request should contain the that the KICS client will use. Please note that not all scan parameters are currently supported by the scanner. When the scan is done, the output can be found at the `<specified output JSON file>`. KICS scan findings are exported via `Result` model defined in Scanner Plugin OpenAPI specs. They are saved to the specified output file in JSON format. KICS outputs all its findings as `Misconfiguration` models under `Result.vmclarity.misconfigurations` property. See .
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: compose_alpha_publish.md

<!MARKERGENSTART--> Publish compose application | Name | Type | Default | Description | |:--|:|:--|:-| | `--dry-run` | | | Execute command in dry run mode | | `--oci-version` | `string` | | OCI Image/Artifact specification version (automatically determined by default) | | `--resolve-image-digests` | | | Pin image tags to digests | <!MARKERGENEND-->
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_bigquery_tables.md

+++ title = "googlebigquerytables resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlebigquerytables" identifier = "inspec/resources/gcp/googlebigquerytables.md googlebigquerytables resource" parent = "inspec/resources/gcp" +++ A `googlebigquerytables` is used to test a Google Table resource ```ruby describe.one do googlebigquerytables(project: 'chef-gcp-inspec', dataset: 'inspecgcpdataset').tablereferences.each do |tablereference| describe googlebigquerytable(project: 'chef-gcp-inspec', dataset: 'inspecgcpdataset', name: tablereference.tableid) do its('expiration_time') { should cmp '1738882264000' } its('description') { should eq 'A BigQuery table' } end end end ``` Properties that can be accessed from the `googlebigquerytables` resource: See the resource for more information. `table_references` : an array of `googlebigquerytable` table_reference `clusterings` : an array of `googlebigquerytable` clustering `creation_times` : an array of `googlebigquerytable` creation_time `friendly_names` : an array of `googlebigquerytable` friendly_name `ids` : an array of `googlebigquerytable` id `labels` : an array of `googlebigquerytable` labels `lastmodifiedtimes` : an array of `googlebigquerytable` lastmodifiedtime `locations` : an array of `googlebigquerytable` location `num_bytes` : an array of `googlebigquerytable` num_bytes `numlongterm_bytes` : an array of `googlebigquerytable` numlongterm_bytes `num_rows` : an array of `googlebigquerytable` num_rows `requirepartitionfilters` : an array of `googlebigquerytable` requirepartitionfilter `types` : an array of `googlebigquerytable` type `views` : an array of `googlebigquerytable` view `time_partitionings` : an array of `googlebigquerytable` time_partitioning `streaming_buffers` : an array of `googlebigquerytable` streaming_buffer `schemas` : an array of `googlebigquerytable` schema `encryption_configurations` : an array of `googlebigquerytable` encryption_configuration `expiration_times` : an array of `googlebigquerytable` expiration_time `externaldataconfigurations` : an array of `googlebigquerytable` externaldataconfiguration `datasets` : an array of `googlebigquerytable` dataset This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.