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

title: CREATE MATERIALIZED VIEW statement [YSQL] headerTitle: CREATE MATERIALIZED VIEW linkTitle: CREATE MATERIALIZED VIEW description: Use the CREATE MATERIALIZED VIEW statement to create a materialized view. menu: v2.18: identifier: ddlcreatematview parent: statements type: docs Use the `CREATE MATERIALIZED VIEW` statement to create a materialized view. {{%ebnf%}} create_matview {{%/ebnf%}} Create a materialized view named matview_name. If `matview_name` already exists in the specified database, an error will be raised unless the `IF NOT EXISTS` clause is used. Used to specify the tablespace for the materialized view. COLOCATION Specify `COLOCATION = true` for the materialized view to be colocated. The default value of this option is false. Basic example. ```plpgsql yugabyte=# CREATE TABLE t1(a int4, b int4); yugabyte=# INSERT INTO t1 VALUES (2, 4), (3, 4); yugabyte=# CREATE MATERIALIZED VIEW m1 AS SELECT * FROM t1 WHERE a = 3; yugabyte=# SELECT * FROM t1; ``` ```output a | b 3 | 4 2 | 4 (2 rows) ``` ```plpgsql yugabyte=# SELECT * FROM m1; ``` ```output a | b 3 | 4 (1 row) ``` Materialized views are not supported in YCQL
Project: OpenTofu (Provisioning / Automation & Configuration)
File: README.md

[!WARNING] This file is not an end-user documentation, it is intended for developers. Please follow the user documentation on the OpenTofu website unless you want to work on the encryption code. This folder contains the state encryption implementation of the AES-GCM encryption method. This is implemented following the guidance of the following document: (). You can configure the encryption by specifying the following method block: ```hcl2 terraform { encryption { method "aes_gcm" "mymethod" { keys = key_provider.someprovider.somename aad = [1,2,3,4,...] } } } ``` | Field | Description | ||--| | `keys` (required) | Encryption and decryption key in the standard output structure of the key providers (`{"encryptionkey":[]byte, "decryptionkey":[]byte}`). | | `aad` | Additional Authenticated Data. This data is stored along the encrypted form and authenticated. The AAD value of the encrypted form must match the configuration, otherwise the decryption fails. | AES-GCM keys have a limited lifetime of `2^32` blocks, equaling roughly 64 GB of data that can be encrypted before the keys should be considered compromised. The end-user documentation of this method should guide users to use either a key-derivation function, such as PBKDF2 or Argon2 with a sufficiently long passphrase, or a key management system that can automatically rotate the keys. The AES-GCM implementation protects data at rest from being accessed. It does not, however, protect against malicious actors reusing old data (replay attacks) to compromise the integrity of the system. Users with the need for payload authentication should rotate their key and/or AAD frequently to ensure that old data cannot be used in this manner. The AAD in AES-GCM is a general-purpose authenticated, but not encrypted field in the encrypted payload. The Go implementation only supports using this field as a canary value, rejecting decryption if the value mismatches. AES-GCM would support using this field as a means to store data. Since Go does not support it, neither do we. The current Go implementation of AES-GCM uses `panic()` to handle some input errors.
Project: KICS (Provisioning / Security & Compliance)
File: 741f1291-47ac-4a85-a07b-3d32a9d6bd3e.md

title: DynamoDB Table Point In Time Recovery Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 741f1291-47ac-4a85-a07b-3d32a9d6bd3e Query name: DynamoDB Table Point In Time Recovery Disabled Platform: Terraform Severity: <span style="color:#5bc0de">Info</span> Category: Best Practices URL: It's considered a best practice to have point in time recovery enabled for DynamoDB Table<br> ```tf title="Positive test num. 1 - tf file" hl_lines="10" resource "awsdynamodbtable" "basic-dynamodb-table" { name = "GameScores" billing_mode = "PROVISIONED" read_capacity = 20 write_capacity = 20 hash_key = "UserId" range_key = "GameTitle" pointintime_recovery { enabled = false } attribute { name = "UserId" type = "S" } attribute { name = "GameTitle" type = "S" } attribute { name = "TopScore" type = "N" } ttl { attribute_name = "TimeToExist" enabled = false } globalsecondaryindex { name = "GameTitleIndex" hash_key = "GameTitle" range_key = "TopScore" write_capacity = 10 read_capacity = 10 projection_type = "INCLUDE" nonkeyattributes = ["UserId"] } tags = { Name = "dynamodb-table-1" Environment = "production" } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "awsdynamodbtable" "basic-dynamodb-table" { name = "GameScores" billing_mode = "PROVISIONED" read_capacity = 20 write_capacity = 20 hash_key = "UserId" range_key = "GameTitle" attribute { name = "UserId" type = "S" } attribute { name = "GameTitle" type = "S" } attribute { name = "TopScore" type = "N" } ttl { attribute_name = "TimeToExist" enabled = false } globalsecondaryindex { name = "GameTitleIndex" hash_key = "GameTitle" range_key = "TopScore" write_capacity = 10 read_capacity = 10 projection_type = "INCLUDE" nonkeyattributes = ["UserId"] } tags = { Name = "dynamodb-table-1" Environment = "production" } } ``` ```tf title="Negative test num. 1 - tf file" resource "awsdynamodbtable" "basic-dynamodb-table" { name = "GameScores" billing_mode = "PROVISIONED" read_capacity = 20 write_capacity = 20 hash_key = "UserId" range_key = "GameTitle" pointintime_recovery { enabled = true } attribute { name = "UserId" type = "S" } attribute { name = "GameTitle" type = "S" } attribute { name = "TopScore" type = "N" } ttl { attribute_name = "TimeToExist" enabled = false } globalsecondaryindex { name = "GameTitleIndex" hash_key = "GameTitle" range_key = "TopScore" write_capacity = 10 read_capacity = 10 projection_type = "INCLUDE" nonkeyattributes = ["UserId"] } tags = { Name = "dynamodb-table-1" Environment = "production" } } ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: http-proxy.md

By default proxy environment variables are passed into the container if set for the Podman process. This can be disabled by setting the value to false. The environment variables passed in include http_proxy, https_proxy, ftp_proxy, no_proxy, and also the upper case versions of those. This option is only needed when the host system must use a proxy but the container does not use any proxy. Proxy environment variables specified for the container in any other way overrides the values that have been passed through from the host. (Other ways to specify the proxy for the container include passing the values with the --env flag, or hard coding the proxy environment at container build time.) When used with the remote client it uses the proxy environment variables that are set on the server process. Defaults to true.
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: compose_wait.md

<!MARKERGENSTART--> Block until the first service container stops | Name | Type | Default | Description | |:--|:--|:--|:| | `--down-project` | | | Drops project when the first container stops | | `--dry-run` | | | Execute command in dry run mode | <!MARKERGENEND-->
Project: external-secrets (Provisioning / Security & Compliance)
File: 000-template.md

```yaml title: My Shiny New Feature version: v1alpha1 authors: you, me creation-date: 2020-09-01 status: draft ``` <!-- toc --> // autogen please <!-- /toc --> Please provide a summary of this proposal. What is the motivation of this proposal? Why is it useful and relevant? What are the goals of this proposal, what's the problem we want to solve? What are explicit non-goals of this proposal? How does the proposal look like? How would users use this feature, what are their needs? Please describe the API (CRD or other) and show some examples. How should the new CRD or feature behave? Are there edge cases? If we implement this feature, what are drawbacks and disadvantages of this approach? What does it take to make this feature producation ready? Please take the time to think about: how would you rollout this feature and rollback if it causes harm? Test Roadmap: what kinds of tests do we want to ensure a good user experience? observability: Do users need to get insights into the inner workings of that feature? monitoring: How can users tell whether the feature is working as expected or not? can we provide dashboards, metrics, reasonable SLIs/SLOs or example alerts for this feature? troubleshooting: How would users want to troubleshoot this particular feature? Think about different failure modes of this feature. What alternatives do we have and what are their pros and cons?
Project: Vitess (App Definition and Development / Database)
File: VitessSlackGuidelinesv1_0.md

The applies in all areas in addition to these rules: Slack is our best communication medium for the community. Please keep your messages on topic for each channel, and please use the appropriate channel. Spamming channels with unrelated or marketing messages is not allowed. Directly messaging users (unless the user has specifically requested the information) offering services, events, employment opportunities or freelance projects, is not allowed. Abuse of the voice/video calling features to call users without their permission is not allowed. Accidents sometimes happen, let the user know it was a mistake. To report a problem the best way to get attention is to create a GitHub . You may post a follow-up question on the #general channel.
Project: YugabyteDB (App Definition and Development / Database)
File: operating-systems.md

title: Operating system support headerTitle: Operating system support linkTitle: Operating systems description: Operating systems supported by YugabyteDB and YugabyteDB Anywhere. menu: stable: identifier: operating-systems parent: configuration weight: 3000 type: docs The following operating systems and architectures are supported for . Unless otherwise noted, operating systems are supported by all supported versions of YugabyteDB and YugabyteDB Anywhere. YugabyteDB Anywhere added support for deploying YugabyteDB to ARM-based systems for non-Kubernetes platforms in v2.18. | Operating system | x86 | ARM | Notes | | : | :- | :- | :- | | AlmaLinux 8 | {{<icon/yes>}} | {{<icon/yes>}} | Recommended for production<br>Recommended development platform<br>Default for YBA-deployed nodes | | AlmaLinux 9 | {{<icon/yes>}} | {{<icon/yes>}} | | | Amazon Linux 2 | {{<icon/yes>}} | {{<icon/yes>}} | v2.18.0 and later<br>Deprecated in v2.20.0 | | CentOS7 | {{<icon/yes>}} | | Deprecated in v2.20.0 | | Oracle 7 | {{<icon/yes>}} | | | | Oracle 8 | {{<icon/yes>}} | | | | Red Hat Enterprise Linux 7 | {{<icon/yes>}} | | | | Red Hat Enterprise Linux 8 | {{<icon/yes>}} | | Recommended for production | <!-- | Red Hat Enterprise Linux&nbsp;9.3 | {{<icon/yes>}} | | v2.20.3 and later<br>Recommended for production | --> | SUSE Linux Enterprise Server 15 SP5 | {{<icon/yes>}} | | {{<badge/ea>}} | | Ubuntu 18 | {{<icon/yes>}} | {{<icon/yes>}} | Deprecated in v2.20.0 | | Ubuntu 20 | {{<icon/yes>}} | {{<icon/yes>}} | | | Ubuntu 22 | {{<icon/yes>}} | {{<icon/yes>}} | Supported in v2.18.5, v2.20.1 |
Project: YugabyteDB (App Definition and Development / Database)
File: zrangebyscore.md

title: ZRANGEBYSCORE linkTitle: ZRANGEBYSCORE description: ZRANGEBYSCORE menu: preview: parent: api-yedis weight: 2520 aliases: /preview/api/redis/zrangebyscore /preview/api/yedis/zrangebyscore type: docs `ZRANGEBYSCORE key min max [WITHSCORES] [LIMIT offset count]` This command fetches `members` for which `score` is in the given `min` `max` range. `min` and `max` are doubles. If `key` does not exist, an empty range is returned. If `key` corresponds to a non sorted-set, an error is raised. Special bounds `-inf` and `+inf` are also supported to retrieve an entire range. `min` and `max` are inclusive unless they are prefixed with `(`, in which case they are exclusive. Returns a list of `members` found in the range specified by `min`, `max`, unless the WITHSCORES option is specified (see below). WITHSCORES: Makes the command return both the `member` and its `score`. LIMIT offset count: Get a range of the matching elements starting at `offset` up to `count` elements, where `offset` is 0 indexed. You can do this as shown below. ```sh $ ZADD z_key 1.0 v1 2.0 v2 ``` ``` (integer) 2 ``` Retrieve all members. ```sh $ ZRANGEBYSCORE z_key -inf +inf ``` ``` 1) "v1" 2) "v2" ``` Retrieve all member score pairs. ```sh $ ZRANGEBYSCORE z_key -inf +inf WITHSCORES ``` ``` 1) "v1" 2) "1.0" 3) "v2" 4) "2.0" ``` Bounds are inclusive. ```sh $ ZRANGEBYSCORE z_key 1.0 2.0 ``` ``` 1) "v1" 2) "v2" ``` Bounds are exclusive. ```sh $ ZRANGEBYSCORE z_key (1.0 (2.0 ``` ``` (empty list or set) ``` Enforce a limit. ```sh ZRANGEBYSCORE z_key -inf +inf LIMIT 1 1 ``` ``` 1) "v2" ``` , , , ,
Project: ClickHouse (App Definition and Development / Database)
File: zookeeper.md

slug: /en/operations/system-tables/zookeeper The table does not exist unless ClickHouse Keeper or ZooKeeper is configured. The `system.zookeeper` table exposes data from the Keeper cluster defined in the config. The query must either have a path = condition or a `path IN` condition set with the `WHERE` clause as shown below. This corresponds to the path of the children that you want to get data for. The query `SELECT * FROM system.zookeeper WHERE path = '/clickhouse'` outputs data for all children on the `/clickhouse` node. To output data for all root nodes, write path = /. If the path specified in path does not exist, an exception will be thrown. The query `SELECT * FROM system.zookeeper WHERE path IN ('/', '/clickhouse')` outputs data for all children on the `/` and `/clickhouse` node. If in the specified path collection has does not exist path, an exception will be thrown. It can be used to do a batch of Keeper path queries. Columns: `name` (String) The name of the node. `path` (String) The path to the node. `value` (String) Node value. `dataLength` (Int32) Size of the value. `numChildren` (Int32) Number of descendants. `czxid` (Int64) ID of the transaction that created the node. `mzxid` (Int64) ID of the transaction that last changed the node. `pzxid` (Int64) ID of the transaction that last deleted or added descendants. `ctime` (DateTime) Time of node creation. `mtime` (DateTime) Time of the last modification of the node. `version` (Int32) Node version: the number of times the node was changed. `cversion` (Int32) Number of added or removed descendants. `aversion` (Int32) Number of changes to the ACL. `ephemeralOwner` (Int64) For ephemeral nodes, the ID of the session that owns this node. Example: ``` sql SELECT * FROM system.zookeeper WHERE path = '/clickhouse/tables/01-08/visits/replicas' FORMAT Vertical ``` ``` text Row 1: name: example01-08-1 value: czxid: 932998691229 mzxid: 932998691229 ctime: 2015-03-27 16:49:51 mtime: 2015-03-27 16:49:51 version: 0 cversion: 47 aversion: 0 ephemeralOwner: 0 dataLength: 0 numChildren: 7 pzxid: 987021031383 path: /clickhouse/tables/01-08/visits/replicas Row 2: name: example01-08-2 value: czxid: 933002738135 mzxid: 933002738135 ctime: 2015-03-27 16:57:01 mtime: 2015-03-27 16:57:01 version: 0 cversion: 37 aversion: 0 ephemeralOwner: 0 dataLength: 0 numChildren: 7 pzxid: 987021252247 path: /clickhouse/tables/01-08/visits/replicas ```
Project: ClickHouse (App Definition and Development / Database)
File: v22.10.3.27-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Update tzdata to 2022f. Mexico will no longer observe DST except near the US border: https://www.timeanddate.com/news/time/mexico-abolishes-dst-2022.html. Chihuahua moves to year-round UTC-6 on 2022-10-30. Fiji no longer observes DST. See https://github.com/google/cctz/pull/235 and https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1995209. (). Backported in : Before the fix, the user-defined config was preserved by RPM in `$file.rpmsave`. The PR fixes it and won't replace the user's files from packages. (). Backported in : Add a CI step to mark commits as ready for release; soft-forbid launching a release script from branches but master. (). Backported in : Fix lowerUTF8()/upperUTF8() in case of symbol was in between 16-byte boundary (very frequent case of you have strings > 16 bytes long). (). Backported in : Fix rare possible hung on query cancellation. (). Backported in : Fix rare NOTFOUNDCOLUMNINBLOCK error when projection is possible to use but there is no projection available. This fixes . The bug was introduced in https://github.com/ClickHouse/ClickHouse/pull/25563. (). Backported in : Fix lambda parsing. Closes . (). Backported in : - Fix several buffer over-reads. (). Backported in : Fixed queries with `SAMPLE BY` with prewhere optimization on tables using `Merge` engine. (). Fix a bug in CAST function parser (). Fix TSan errors (correctly ignore _exit interception) (). Update SECURITY.md on new stable tags (). Use all parameters with prefixes from ssm ().
Project: Devfile (App Definition and Development / Application Definition & Image Build)
File: SECURITY.md

Join the [kubernetes-security-announce] group for security and vulnerability announcements. You can also subscribe to an RSS feed of the above using . Instructions for reporting a vulnerability can be found on the [Kubernetes Security and Disclosure Information] page. Information about supported Kubernetes versions can be found on the [Kubernetes version and version skew support policy] page on the Kubernetes website.
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: Demo.md

In this Demo, Application application-sample will be converted to appcontext and component The fields in the application spec come from the parametes defined in the definition template , so we must install Definition at first Step 1: Install ComponentDefinition & Trait Definition ``` kubectl apply -f template.yaml ``` Step 2: Create a sample application in the cluster ``` kubectl apply -f application-sample.yaml ``` Step 3: View the application status ``` kubectl get -f application-sample.yaml -oyaml // You can see the following apiVersion: core.oam.dev/v1beta1 kind: Application metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"core.oam.dev/v1beta1","kind":"Application","metadata":{"annotations":{},"name":"application-sample","namespace":"default"},"spec":{"components":[{"name":"myweb","properties":{"cmd":["sleep","1000"],"image":"busybox"},"traits":[{"properties":{"replicas":10},"type":"scaler"},{"properties":{"image":"nginx","name":"sidecar-test"},"type":"sidecar"},{"properties":{"http":{"server":80}},"type":"kservice"}],"type":"worker"}]}} ... spec: components: name: myweb properties: cmd: sleep "1000" image: busybox traits: properties: replicas: 10 type: scaler properties: image: nginx name: sidecar-test type: sidecar properties: http: server: 80 type: kservice type: worker status: batchRollingState: "" components: apiVersion: core.oam.dev/v1alpha2 kind: Component name: myweb conditions: reason: Available status: "True" type: Parsed reason: Available status: "True" type: Built reason: Available status: "True" type: Applied status: running ... ```
Project: BigchainDB (App Definition and Development / Database)
File: set-up-nginx.md

<! Copyright 2020 Interplanetary Database Association e.V., BigchainDB and IPDB software contributors. SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0) Code is Apache-2.0 and docs are CC-BY-4.0 > If you don't want HTTPS (for communications between the external world and your node), then you can skip all the NGINX steps on this page. Note: This simple deployment template uses NGINX for more than just HTTPS. For example, it also does basic rate limiting. SSH into your machine and install NGINX: ``` sudo apt update sudo apt install nginx ``` Get an SSL certificate for your node's subdomain (such as `bnode.example.com`). Copy the SSL private key into `/etc/nginx/ssl/cert.key` Create a "PEM file" (text file) by concatenating your SSL certificate with all intermediate certificates (in that order, with the intermediate certs last). Copy that PEM file into `/etc/nginx/ssl/cert.pem` In the , find the file `nginx/nginx.conf` and copy its contents to `/etc/nginx/nginx.conf` on your machine (i.e. replace the existing file there). Edit that file (`/etc/nginx/nginx.conf`): replace the two instances of the string `example.testnet2.com` with your chosen subdomain (such as `bnode.example.com`). Reload NGINX by doing: ``` sudo service nginx reload ```
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk_completion_fish.md

title: "operator-sdk completion fish" Load fish completions ``` operator-sdk completion fish [flags] ``` ``` $ operator-sdk completion fish | source $ operator-sdk completion fish > ~/.config/fish/completions/operator-sdk.fish ``` ``` -h, --help help for fish ``` ``` --plugins strings plugin keys to be used for this subcommand execution --verbose Enable verbose logging ``` - Load completions for the specified shell
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-image-exists.1.md

% podman-image-exists 1 podman-image-exists - Check if an image exists in local storage podman image exists image podman image exists checks if an image exists in local storage. The ID or Name of the image may be used as input. Podman returns an exit code of `0` when the image is found. A `1` is returned otherwise. An exit code of `125` indicates there was an issue accessing the local storage. Print usage statement Check if an image called `webclient` exists in local storage (the image does actually exist): ``` $ podman image exists webclient $ echo $? 0 ``` Check if an image called `webbackend` exists in local storage (the image does not actually exist): ``` $ podman image exists webbackend $ echo $? 1 ``` , November 2018, Originally compiled by Brent Baude (bbaude at redhat dot com)
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: bug_report.md

name: "\U0001F41B Bug report" about: Create a report to help us improve title: "" labels: kind/bug assignees: '' Describe the bug <!-- A clear and concise description of what the bug is. --> To Reproduce <!-- Steps to reproduce the behavior: The YAML files of Component/Trait I used. The YAML file of Application I applied. Other operations I have done. See error --> Expected behavior <!-- A clear and concise description of what you expected to happen. --> Screenshots <!-- If applicable, add screenshots to help explain your problem. --> KubeVela Version <!-- Describe your KubeVela controller or CLI version information. --> Cluster information <!-- Describe your kubernetes cluster information. Kubernetes Version [e.g. 1.16.9] --> Additional context <!-- Add any other context about the problem here. -->
Project: Tremor (App Definition and Development / Streaming & Messaging)
File: arraypattern.md

The `ArrayPattern` defines structural patterns against array values. Array patterns start with the `%[` operator and end with `]`. Patterns may be empty `%[]`, or a sequence of array predicate patterns. Array patterns are search oriented based on predicate matching. Where ordinal matching is needed then a `TuplePattern` may be preferential.