cwielenb/CNCF-Dataset huggingface dataset:
Project: Dragonfly (Provisioning / Container Registry)
File: MAINTAINERS.md

<!-- markdownlint-disable --> | GitHub ID | Name | Email | Company | | :--: | :-: | :--: | :--: | | | Allen Sun | shlallen1990@gmail.com | Alibaba Group | | | Zuozheng Hu | zuozheng.hzz@alibaba-inc.com | Alibaba Group | | | Yuan Yang | qiguo.yy@alibaba-inc.com | Alibaba Group | | | Peng Tao | bergwolf@hyper.sh | Ant Group | | | Jim Ma | majinjing3@gmail.com | Ant Group | | | Gaius Qi | gaius.qi@gmail.com | Ant Group | | | Garen Wen | wenmxiang@gmail.com | Baidu Group | | | fcgxz2003 | 834756128@qq.com | Dalian University of Technology | | | Yiyang Huang | 691795636@qq.com | ByteDance | | | Mohammed Farooq | mfarooq.ta@gmail.com | Intel | | | Akash HR | akashhr2021@gmail.com | Intel | | | yxxhero | aiopsclub@163.com | JiHu | <!-- markdownlint-restore -->
Project: StarRocks (App Definition and Development / Database)
File: data_compression.md

displayed_sidebar: "English" StarRocks supports data compression for table and index storage. Data compression not only helps save storage space, but also improves performance of I/O intensive tasks because StarRocks can read fewer pages from disk for each request. Note that extra CPU resource is required to compress and decompress the data. StarRocks supports four data compression algorithms: LZ4, Zstandard (or zstd), zlib, and Snappy. These data compression algorithms differ in compression ratio and compression/decompression performance. Generally, the compression ratios of these algorithms rank as follows: zlib > Zstandard > LZ4 > Snappy. Among them, zlib has shown relatively high compression ratios. As a result of the highly compressed data, the loading and query performances on tables with the zlib compression algorithm are also affected. LZ4 and Zstandard, especially, have well-balanced compression ratios and decompression performances. You can choose among these compression algorithms to cater to your business needs for less storage space or better performance. We recommend LZ4 or Zstandard if you do not have specific demands for less storage space. NOTE Different data types can affect the compression ratio. You can specify a data compression algorithm for a table only when creating the table, and you cannot change it afterwards. The following example creates a table `data_compression` with the Zstandard algorithm. For detailed instructions, see . ```SQL CREATE TABLE `data_compression` ( `id` INT(11) NOT NULL COMMENT "", `name` CHAR(200) NULL COMMENT "" ) ENGINE=OLAP UNIQUE KEY(`id`) COMMENT "OLAP" DISTRIBUTED BY HASH(`id`) PROPERTIES ( "compression" = "ZSTD" ); ``` NOTE If no data compression algorithm is specified, StarRocks uses LZ4 by default. You can view the compression algorithm of a table using .
Project: YugabyteDB (App Definition and Development / Database)
File: managed-terraform.md

title: YugabyteDB Managed Terraform Provider headerTitle: Terraform Provider linkTitle: Terraform Provider description: Terraform Provider for YugabyteDB Managed. headcontent: Manage YugabyteDB Managed accounts and deployments using the Terraform Provider menu: preview_yugabyte-cloud: parent: managed-automation identifier: managed-terraform weight: 10 type: docs Use the YugabyteDB Managed Terraform Provider to deploy and manage clusters programmatically. Some examples of what you can accomplish using this provider include: Deploy and manage clusters Deploy and manage read replicas Pause and resume clusters automatically, based on a schedule or external events Run on-demand backups and restores Change backup and maintenance schedules Configure monitoring and alerts {{< youtube id="cHPMDLeVkFU?si=GcZBrV27HDqPpezs" title="YugabyteDB Managed Terraform Provider" >}} {{< sections/2-boxes >}} {{< sections/bottom-image-box title="Get Started" description="Manage YugabyteDB Managed using the Terraform Provider." buttonText="Provider Documentation" buttonUrl="https://registry.terraform.io/providers/yugabyte/ybm/latest/docs/" >}} {{< /sections/2-boxes >}}
Project: YugabyteDB (App Definition and Development / Database)
File: to-jsonb.md

title: tojsonb() and tojson() headerTitle: to_jsonb() linkTitle: to_jsonb() description: Convert a single SQL value of any primitive or compound data type, that allows a JSON representation, to a semantically equivalent jsonb value. menu: v2.18: identifier: to-jsonb parent: json-functions-operators type: docs Purpose: Convert a single SQL value of any primitive or compound data type, that allows a JSON representation, to a semantically equivalent `jsonb` value. Signature For the `jsonb` variant: ``` input value: anyelement return value: jsonb ``` Use this `ysqlsh` script to create types "t1" and "t2" and then to execute the `DO` block that asserts that the behavior is as expected. For an arbitrary nest of SQL `record` and SQL array values, readability is improved by building the compound value from the bottom up. ```plpgsql create type t1 as(a int, b text); create type t2 as(x text, y boolean, z t1[]); do $body$ declare j1dog constant jsonb := tojsonb('In the'||Chr(10)||'"dog house"'::text); j2_dog constant jsonb := '"In the\n\"dog house\""'; j142 constant jsonb := tojsonb(42::numeric); j2_42 constant jsonb := '42'; j1true constant jsonb := tojsonb(true::boolean); j2_true constant jsonb := 'true'; j1null constant jsonb := tojsonb(null::boolean); j2_null constant jsonb := 'null'; j1array constant jsonb := tojsonb(array['a', 42, true]::text[]); j2_array constant jsonb := '["a", "42", "true"]'; v1 t1 := (17::int, 'dog'::text); v2 t1 := (42::int, 'cat'::text); v3 t1[] := array[v1, v2]; v4 t2 := ('frog', true, v3); j1object constant jsonb := tojsonb(v4::t2); j2_object constant jsonb := '{"x": "frog", "y": true, "z": [{"a": 17, "b": "dog"}, {"a": 42, "b": "cat"}]}'; begin assert j1dog = j2dog and j142 = j242 and j1true = j2true and j1array = j2array and j1object = j2object, 'unexpected'; end; $body$; ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.4.md

RabbitMQ `3.9.4` is a maintenance release in the `3.9.x` release series. Please refer to the Upgrading to 3.9 section from if upgrading from a version prior to 3.9.0. This release requires at least Erlang 23.2, and supports the latest Erlang 24 version, 24.0.5 at the time of release. has more details on Erlang version requirements for RabbitMQ. Release notes are kept under . Contributors are encouraged to update them together with their changes. This helps with release automation and more consistent release schedule. Nodes will now use four more environment variables, if set: `RABBITMQDEFAULTUSER` (overrides `defaultuser` in `rabbitmq.conf`), `RABBITMQDEFAULTPASS` (overrides `defaultpass`), `RABBITMQDEFAULTVHOST` (overrides `defaultvhost`) and `RABBITMQERLANG_COOKIE` (sets ). These variables are not recommended to be used in production but can be the only realistic option in some environment, such as service containers, ECS, and so on. Most users should continue using `rabbitmq.conf` and a securely generated local cookie file. GitHub issue: Definitions now can be imported from different sources, including those provided by plugins. Original local filesystem source is still supported in a backwards-compatible way. The following `rabbitmq.conf` example uses a local file as the source: ``` ini definitions.importbackend = localfilesystem definitions.local.path = /path/to/definitions.json ``` This `rabbitmq.conf` example uses a local directory with definition files: ``` ini definitions.importbackend = localfilesystem definitions.local.path = /path/to/rabbitmq/definitions.d ``` In this example config file, definitions are loaded from a URL accessible over HTTPS: ``` ini definitions.import_backend = https definitions.https.url = https://rabbitmq.eng.megacorp.local/env-1/definitions.json definitions.tls.versions.1 = tlsv1.2 definitions.tls.log_level = error ``` GitHub issue: New Prometheus metrics for alarms: `rabbitmqalarmsfiledescriptorlimit` 1|0 `rabbitmqalarmsfreediskspace_watermark` 1|0 `rabbitmqalarmsmemoryusedwatermark` 1|0 While some of the alarms have cluster-wide effect, these metrics are node-local. GitHub issue: No dependency changes in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.4.tar.xz` instead of the source tarball produced by GitHub.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.7.25.md

RabbitMQ `3.7.25` is a maintenance release. It focuses on bug fixes and usability improvements. This is the last generally supported `3.7.x` release. RabbitMQ `3.7.x` series are now covered by the policy. Please consider to . This release . Previously recent `3.7.x` nodes could start on Erlang 20.3 and to some extent tested on it despite the Erlang `21.3+` requirements in release notes and documentation. Starting with this release, `21.3+` is a hard requirement enforced in the code to . Make sure a is used before upgrading. explains what package repositories and tools can be used to provision latest patch versions of Erlang `21.3.x` and `22.x`. When upgrading to this release and upgrading Erlang to 21.x or later at the same time, extra care has to be taken. Since CLI tools from RabbitMQ releases older than 3.7.7 will fail on Erlang 21 or later, RabbitMQ must be upgraded before Erlang. See upgrade and compatibility notes first if upgrading from an earlier release. See the for general documentation on upgrades and for release notes of other releases. Any questions about this release, upgrades or RabbitMQ in general are welcome on the . Erlang `20.3` and earlier version support has been completely removed after months of being documented as unsupported. This release, however, gains Erlang `23.0` forward compatibility. GitHub issue: More frequent garbage collection by stats DB cache processes in environments where HTTP API queries produced large data sets. GitHub issue: `rabbitmqadmin` binding deletion now defaults to the same property key value as binding creation. Contributed by Ivan Kaloyanov. GitHub issue: `rabbitmqadmin import` mangled non-ASCII characters. GitHub issue: Internal resources cleanup is now more selective on abnormal link termination. A new upstream parameter, `resource-cleanup-mode`, can be set to `"never"` used to prevent internal queues from being deleted by exchange federation links on termination. Use this when data safety is more important than protection from resource leaks. It then will be up to the operator to make sure such resources are periodically deleted or use a suitable . GitHub issue: Shovels are now correctly removed even when deletion commands are executed against a different node (not the one on which the target Shovel has been created). GitHub issue: HTTPS certificate provider will no longer terminate if upstream service response contains invalid JSON. GitHub issue: Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-server-3.7.25.tar.xz`.
Project: ShardingSphere (App Definition and Development / Database)
File: show-sharding-auditors.en.md

+++ title = "SHOW SHARDING AUDITORS" weight = 7 +++ `SHOW SHARDING AUDITORS` syntax is used to query sharding auditors in specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowShardingAuditors::= 'SHOW' 'SHARDING' 'AUDITORS' ('FROM' databaseName)? databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When databaseName is not specified, the default is the currently used DATABASE. If DATABASE is not used, No database selected will be prompted. | column | Description | |--|| | name | Sharding auditor name | | type | Sharding auditor algorithm type | | props | Sharding auditor algorithm properties | Query sharding auditors for the specified logical database ```sql SHOW SHARDING AUDITORS FROM sharding_db; ``` ```sql mysql> SHOW SHARDING AUDITORS FROM sharding_db; +-+-+-+ | name | type | props | +-+-+-+ | shardingkeyrequiredauditor | dmlsharding_conditions | | +-+-+-+ 1 row in set (0.01 sec) ``` Query sharding auditors for the current logical database ```sql SHOW SHARDING AUDITORS; ``` ```sql mysql> SHOW SHARDING AUDITORS; +-+-+-+ | name | type | props | +-+-+-+ | shardingkeyrequiredauditor | dmlsharding_conditions | | +-+-+-+ 1 row in set (0.00 sec) ``` `SHOW`, `SHARDING`, `AUDITORS`, `FROM`
Project: secureCodeBox (Provisioning / Security & Compliance)
File: scanner-dir.md

title: scanner (Directory) sidebar_position: 5 If it is not possible to use the official Docker Image of your scanner (e.g. there is no official repository) you will need to create a `scanner` directory containing a Dockerfile and maybe a `wrapper.sh`. The Dockerfile should be minimal and based on the official alpine baseimage. Please make sure to add a new user for your scanner. Please change the user using `UID`. This enables the Image to run in clusters which have a strict `runAsNonRoot` policy (See ). Use the Docker build argument `scannerVersion` to retrieve a specific version of your scanner. `scannerVersion` should be populated by your scanner's chart `AppVersion` field (see ). A Docker image for nmap would look the following: ```dockerfile FROM alpine:3.12 ARG scannerVersion=latest RUN apk add --no-cache nmap=$scannerVersion nmap-scripts=$scannerVersion RUN addgroup --system --gid 1001 nmap && adduser nmap --system --uid 1001 --ingroup nmap USER 1001 CMD [nmap] ``` See for instructions on how to build and deploy your scanner. Sometimes it will be necessary to wrap the scanner e.g. the scanner returns bad exit codes when they identify findings. This would cause the Kubernetes jobs to fail even thought the scanner has actually run successfully, after all it's "their job" to identify findings. Please provide this script as `wrapper.sh` and use it as `CMD` value in your Dockerfile. Furthermore, note that the scanner should output the findings to `/home/securecodebox/<your_scanner>.<filetype>`. This should be the same as in `ScanType` `Spec.ExtractResults.Location`. Please take a look at on how to configure your `ScanType`. Outputting results to a file is usually specified as a command line option to your scanner (e.g. `nmap -oX file.xml`), but in the case that the scanner does not provide such an options, you could write the wrapper as follows: ```shell python scanner.py "$@" 1> /home/securecodebox/<your_scanner>.<filetype> ```
Project: KICS (Provisioning / Security & Compliance)
File: 5e92d816-2177-4083-85b4-f61b4f7176d9.md

title: Public Lambda via API Gateway hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 5e92d816-2177-4083-85b4-f61b4f7176d9 Query name: Public Lambda via API Gateway Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Allowing to run lambda function using public API Gateway<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="9" name: Lambda S3 event notification lambda_policy: state: "{{ state | default('present') }}" function_name: functionName alias: Dev statement_id: lambda-s3-myBucket-create-data-log action: lambda:InvokeFunction principal: apigateway.amazonaws.com source_arn: arn:aws:s3:eu-central-1:123456789012// ``` ```yaml title="Negative test num. 1 - yaml file" name: Lambda S3 event notification lambda_policy: state: "{{ state | default('present') }}" function_name: functionName alias: Dev statement_id: lambda-s3-myBucket-create-data-log action: lambda:InvokeFunction principal: s3.amazonaws.com source_arn: arn:aws:s3:eu-central-1:123456789012:bucketname ```
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-context.md

layout: default title: mesheryctl-system-context permalink: reference/mesheryctl/system/context redirect_from: reference/mesheryctl/system/context/ type: reference display-title: "false" language: en command: system subcommand: context Configure your Meshery deployment(s) Configure and switch between different named Meshery server and component versions and deployments. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system context [command] [flags] </div> </pre> Base command <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system context </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -c, --context string (optional) temporarily change the current context. -h, --help help for context </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -v, --verbose verbose output -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: awesome-opa.md

title: Awesome OPA List software: [] labels: category: learning type: poweredbyopa code: https://github.com/StyraInc/awesome-opa inventors: styra docs_features: learning-rego: note: | The Awesome OPA project maintains a list of , and which can be helpful references for learning Rego. allowmissingimage: true A curated list of awesome OPA related tools, frameworks and articles.
Project: YugabyteDB (App Definition and Development / Database)
File: graph-representation.md

title: Representing a graph in a SQL database headerTitle: Representing different kinds of graph in a SQL database linkTitle: Graph representation description: This section shows how to represent different kinds of graph in a SQL database, menu: v2.18: identifier: graph-representation parent: traversing-general-graphs weight: 10 type: docs Look at the diagram of an example on this page's parent page. You can see that it has seven edges thus: (n1-n2), (n2-n3), (n2-n4), (n3-n5), (n4-n5), (n4-n6), (n5-n6) The minimal representation in a SQL database uses just a table of table of edges, created thus: ```plpgsql drop table if exists edges cascade; create table edges( node_1 text not null, node_2 text not null, constraint edgespk primary key(node1, node_2)); ``` A typical special case, like , would specify "node1" and "node2" with names that are specific to the use case (like "actor" and "coactor") whose values are the primary keys in a separate "actors" table. This implies foreign key constraints, of course. The "actors" table would have other columns (like "givenname", "familyname", and so on). Similarly, the "edges"_ table would have at least one other column: the array of movies that the two connected actors have been in. There are two obvious design choices. One design populates the "edges" table sparsely by recording each edge just once. For example, if node "a" is recorded in column "node1", then it must not be recorded in column "node2". Then you must understand that though the column names "node1" and "node2" imply a direction, this is not the case. Though this design has the appeal of avoiding denormalization, it makes the SQL design tricky. When the traversal arrives at a node and needs to find the nodes at the other ends of the edges that have the present node at one of their ends, you don't know whether to restrict on "node1" and read "node2" or to restrict on "node2" and read "node1" and so you must try both. The other design records each edge twice. For example, the edge between nodes "a" and "b" will be recorded both as (node1 = 'a', node2 = 'b') and as (node1 = 'b', node2 = 'a'). This denormalization makes the SQL straightforwardand is therefore preferred. An implementation of the is described for completeness. But the approach that leads to simpler SQL, the is described first. The representations for the more specialized kinds of graph, , and all use the same table structure but with appropriately different rules to which the content must conform.
Project: YugabyteDB (App Definition and Development / Database)
File: test-yedis.md

<!-- +++ private = true +++ --> Initialize the YEDIS API. Set up the `rediskeyspace` keyspace and the `.redis` table so that this cluster becomes ready for Redis clients. Detailed output for the `setupredis` command is available in the . ```sh $ ./bin/yb-ctl setup_redis ``` Run redis-cli to connect to the service. ```sh $ ./bin/redis-cli ``` ```output 127.0.0.1:6379> ``` Run a Redis command to verify it is working. ```sql 127.0.0.1:6379> PING ``` ```output "PONG" ```
Project: KICS (Provisioning / Security & Compliance)
File: 85da374f-b00f-4832-9d44-84a1ca1e89f8.md

title: App Service FTPS Enforce Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 85da374f-b00f-4832-9d44-84a1ca1e89f8 Query name: App Service FTPS Enforce Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Azure App Service should only enforce FTPS when 'ftps_state' is enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="10" resource "azurermappservice" "positive1" { name = "example-app-service" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name appserviceplanid = azurermappserviceplan.example.id site_config { dotnetframeworkversion = "v4.0" scm_type = "LocalGit" ftps_state = "AllAllowed" } } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermappservice" "negative1" { name = "example-app-service" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name appserviceplanid = azurermappserviceplan.example.id site_config { dotnetframeworkversion = "v4.0" scm_type = "LocalGit" ftps_state = "FtpsOnly" } } ``` ```tf title="Negative test num. 2 - tf file" resource "azurermappservice" "negative2" { name = "example-app-service" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name appserviceplanid = azurermappserviceplan.example.id site_config { dotnetframeworkversion = "v4.0" scm_type = "LocalGit" ftps_state = "Disabled" } } ```
Project: KICS (Provisioning / Security & Compliance)
File: d4a73c49-cbaa-4c6f-80ee-d6ef5a3a26f5.md

title: CloudTrail Logging Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d4a73c49-cbaa-4c6f-80ee-d6ef5a3a26f5 Query name: CloudTrail Logging Disabled Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Checks if logging is enabled for CloudTrail.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="5" name: example community.aws.cloudtrail: state: present name: default enable_logging: false ``` ```yaml title="Negative test num. 1 - yaml file" name: example community.aws.cloudtrail: state: present name: default enable_logging: true ```
Project: StarRocks (App Definition and Development / Database)
File: ALTER_PIPE.md

displayed_sidebar: "English" Alters the settings of the properties of a pipe. This command is supported from v3.2 onwards. ```SQL ALTER PIPE [dbname.]<pipename> SET PROPERTY ( "<key>" = <value>[, "<key>" = "<value>" ...] ) ``` The name of the database to which the pipe belongs. The name of the pipe. The properties whose settings you want to alter for the pipe. Format: `"key" = "value"`. For more information about the properties supported, see . Change the setting of the `AUTOINGEST` property to `FALSE` for the pipe named `userbehavior_replica` in the database named `mydatabase`: ```SQL USE mydatabase; ALTER PIPE userbehaviorreplica SET ( "AUTO_INGEST" = "FALSE" ); ```