cwielenb/CNCF-Dataset huggingface dataset:
Project: Parsec (Provisioning / Security & Compliance)
File: PARTNERS.md

<!-- -- Copyright 2019 Contributors to the Parsec project. -- SPDX-License-Identifier: Apache-2.0 > <p> <a href="https://www.arm.com" border="0" target="blank"><img alt="arm.com" src="doc/images/partners/arm/Armlogoblue150LG.png" height="50"></a>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href="https://www.docker.com" border="0" target="_blank"><img alt="docker.com" src="doc/images/partners/docker/vertical-logo-monochromatic.png" height="100"></a>&nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href="https://www.mirantis.com" border="0" target="_blank"><img alt="mirantis.com" src="doc/images/partners/mirantis/mirantis-logo-2color-rgb-transparent.png" height="100"></a>&nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href="https://www.linaro.org" border="0" target="blank"><img alt="linaro.org" src="doc/images/partners/linaro/Logolinaro.png" height="100"></a>&nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </p> Note: Arm is contributing to Parsec as part of . <p> <a href="https://rancher.com" border="0" target="_blank"><img alt="rancher.com" src="doc/images/partners/rancher/rancher-logo-stacked-color.png" height="100"></a>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href="https://www.redhat.com" border="0" target="_blank"><img alt="redhat.com" src="doc/images/partners/redhat/Logo-RedHat-D-Color-RGB.png" height="100"></a>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href="https://www.nxp.com" border="0" target="blank"><img alt="nxp.com" src="doc/images/partners/nxp/NXPlogoRGBweb.jpg" height="100"></a>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </p>
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.16.md

layout: release date: 2022-10-14 tag: v0.6.16 language: en Upgrade Meshkit and Operator @Revolyssup (#6361) Remove redundant fields from Application and fix lables bug @Revolyssup (#6371) [mesheryctl] Fix incorrect k8s config response handling @gr455 (#6374) Fixing the key prop warnings in the ui/applications and SMI Result @legendarykamal (#6383) [chore] Fix resync cluster on flushing MeshSync data @theBeginner86 (#6355) Revert "[Feat] Add support for visualizing state machines " @leecalcote (#6364) design-yaml: remove redundant fields from the pattern-yaml @Abhishek-kumar09 (#6369) Removed the margin from all SVG. @Harshit-Dandriyal (#6368) [rjsf] Sorting Logic for rjsf @harkiratsm (#6362) [chore] Fix resync cluster on flushing MeshSync data @theBeginner86 (#6355) [CI] Go dependencies: upgrade meshery pkgs @leecalcote (#6351) [Docs] Consul adapter added to matrix and (NA) icon introduced @asubedy (#6376) Added Artifact hub/Clomonitor badge to Meshery repo @legendarykamal (#6354) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Harshit-Dandriyal, @Nikhil-Ladha, @Revolyssup, @asubedy, @gr455, @harkiratsm, @l5io, @leecalcote, @legendarykamal, @theBeginner86 and l5io
Project: YDB (App Definition and Development / Database)
File: general.md

Group the `SELECT` results by the values of the specified columns or expressions. `GROUP BY` is often combined with (`COUNT`, `MAX`, `MIN`, `SUM`, `AVG`) to perform calculations in each group. Syntax ```sql SELECT -- In SELECT, you can use: column1, -- key columns specified in GROUP BY key_n, -- named expressions specified in GROUP BY column1 + key_n, -- arbitrary non-aggregate functions on them Aggr_Func1( column2 ), -- aggregate functions containing any columns as arguments, AggrFunc2( keyn + column2 ), -- including named expressions specified in GROUP BY ... FROM table GROUP BY column1, column2, ..., <expr> AS key_n -- When grouping by expression, you can set a name for it using AS, -- and use it in SELECT ``` The query in the format `SELECT * FROM table GROUP BY k1, k2, ...` returns all columns listed in GROUP BY, i.e., is equivalent to `SELECT DISTINCT k1, k2, ... FROM table`. An asterisk can also be used as an argument for the `COUNT` aggregate function. `COUNT(*)` means "the count of rows in the group". {% note info %} Aggregate functions ignore `NULL` in their arguments, except for `COUNT`. {% endnote %} YQL also provides aggregation factories implemented by the functions and . Examples ```sql SELECT key, COUNT(*) FROM my_table GROUP BY key; ``` ```sql SELECT doublekey, COUNT(*) FROM mytable GROUP BY key + key AS double_key; ``` ```sql SELECT double_key, -- OK: A key column COUNT() AS group_size, -- OK: COUNT() SUM(key + subkey) AS sum1, -- OK: An aggregate function CAST(SUM(1 + 2) AS String) AS sum2, -- OK: An aggregate function with a constant argument SUM(SUM(1) + key) AS sum3, -- ERROR: Nested aggregations are not allowed key AS k1, -- ERROR: Using a non-key column named key without aggregation key * 2 AS dk1, -- ERROR in YQL: using a non-key column named key without aggregation FROM my_table GROUP BY key * 2 AS double_key, subkey as sk, ``` {% note warning %} Specifying a name for a column or expression in `GROUP BY .. AS foo` it is an extension on top of YQL. Such a name becomes visible in `WHERE` despite the fact that filtering by `WHERE` is executed the grouping. For example, if the `T` table includes two columns, `foo` and `bar`, then the query `SELECT foo FROM T WHERE foo > 0 GROUP BY bar AS foo` would actually filter data by the `bar` column from the source table. {% endnote %}
Project: CloudNativePG (App Definition and Development / Database)
File: image_catalog.md

`ImageCatalog` and `ClusterImageCatalog` are essential resources that empower you to define images for creating a `Cluster`. The key distinction lies in their scope: an `ImageCatalog` is namespaced, while a `ClusterImageCatalog` is cluster-scoped. Both share a common structure, comprising a list of images, each equipped with a `major` field indicating the major version of the image. !!! Warning The operator places trust in the user-defined major version and refrains from conducting any PostgreSQL version detection. It is the user's responsibility to ensure alignment between the declared major version in the catalog and the PostgreSQL image. The `major` field's value must remain unique within a catalog, preventing duplication across images. Distinct catalogs, however, may expose different images under the same `major` value. Example of a Namespaced `ImageCatalog`: ```yaml apiVersion: postgresql.cnpg.io/v1 kind: ImageCatalog metadata: name: postgresql namespace: default spec: images: major: 15 image: ghcr.io/cloudnative-pg/postgresql:15.6 major: 16 image: ghcr.io/cloudnative-pg/postgresql:16.3 ``` Example of a Cluster-Wide Catalog using `ClusterImageCatalog` Resource: ```yaml apiVersion: postgresql.cnpg.io/v1 kind: ClusterImageCatalog metadata: name: postgresql spec: images: major: 15 image: ghcr.io/cloudnative-pg/postgresql:15.6 major: 16 image: ghcr.io/cloudnative-pg/postgresql:16.3 ``` A `Cluster` resource has the flexibility to reference either an `ImageCatalog` or a `ClusterImageCatalog` to precisely specify the desired image. ```yaml apiVersion: postgresql.cnpg.io/v1 kind: Cluster metadata: name: cluster-example spec: instances: 3 imageCatalogRef: apiGroup: postgresql.cnpg.io kind: ImageCatalog name: postgresql major: 16 storage: size: 1Gi ``` Clusters utilizing these catalogs maintain continuous monitoring. Any alterations to the images within a catalog trigger automatic updates for all associated clusters referencing that specific entry. The CloudNativePG project maintains `ClusterImageCatalogs` for the images it provides. These catalogs are regularly updated with the latest images for each major version. By applying the `ClusterImageCatalog.yaml` file from the CloudNativePG project's GitHub repositories, cluster administrators can ensure that their clusters are automatically updated to the latest version within the specified major release. You can install the ( repository) with: ```shell kubectl apply \ -f https://raw.githubusercontent.com/cloudnative-pg/postgres-containers/main/Debian/ClusterImageCatalog.yaml ``` You can install the ( repository) with: ```shell kubectl apply \ -f https://raw.githubusercontent.com/cloudnative-pg/postgis-containers/main/PostGIS/ClusterImageCatalog.yaml ```
Project: StarRocks (App Definition and Development / Database)
File: ifnull.md

displayed_sidebar: "English" If `expr1` is NULL, returns expr2. If `expr1` is not NULL, returns `expr1`. ```Haskell ifnull(expr1,expr2); ``` `expr1` and `expr2` must be compatible in data type. The return value has the same type as `expr1`. ```Plain Text mysql> select ifnull(2,4); +--+ | ifnull(2, 4) | +--+ | 2 | +--+ mysql> select ifnull(NULL,2); +--+ | ifnull(NULL, 2) | +--+ | 2 | +--+ 1 row in set (0.01 sec) ```
Project: KICS (Provisioning / Security & Compliance)
File: 89806cdc-9c2e-4bd1-a0dc-53f339bcfb2a.md

title: Password Without Reuse Prevention hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 89806cdc-9c2e-4bd1-a0dc-53f339bcfb2a Query name: Password Without Reuse Prevention Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: Check if IAM account password has the reuse password configured with 24<br> ```tf title="Positive test num. 1 - tf file" hl_lines="10 7" resource "awsiamaccountpasswordpolicy" "positive1" { requirelowercasecharacters = true require_numbers = true requireuppercasecharacters = true require_symbols = true allowuserstochangepassword = true passwordreuseprevention = 20 } resource "awsiamaccountpasswordpolicy" "positive2" { minimumpasswordlength = 3 requirelowercasecharacters = true require_numbers = true requireuppercasecharacters = true require_symbols = true allowuserstochangepassword = true } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamaccountpasswordpolicy" "negative1" { minimumpasswordlength = 8 requirelowercasecharacters = true require_numbers = true requireuppercasecharacters = true require_symbols = true allowuserstochangepassword = true passwordreuseprevention = 24 } ```
Project: Flink (App Definition and Development / Streaming & Messaging)
File: java_compatibility.md

title: Java Compatibility weight: 2 type: docs <!-- 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. --> This page lists which Java versions Flink supports and what limitations apply (if any). Support for Java 8 has been deprecated in 1.15.0. It is recommended to migrate to Java 11. Support for Java 11 was added in 1.10.0 and is the recommended Java version to run Flink on. This is the default version for docker images. The following Flink features have not been tested with Java 11: Hive connector Hbase 1.x connector Modularized user jars have not been tested. Experimental support for Java 17 was added in 1.18.0. () These Flink features have not been tested with Java 17: Hive connector Hbase 1.x connector Starting with Java 16 Java applications have to fully cooperate with the JDK modularization, also known as . This means that access to JDK classes/internal must be explicitly allowed by the application when it is started, on a per-module basis, in the form of --add-opens/--add-exports JVM arguments. Since Flink uses reflection for serializing user-defined functions and data (via Kryo), this means that if your UDFs or data types use JDK classes you may have to allow access to these JDK classes. These should be configured via the option. In the default configuration in the Flink distribution this option is configured such that Flink itself works on Java 17. The list of configured arguments must not be shortened, but only extended. Java records are not supported. See for updates. SIGSEGV in C2 Compiler thread: Early Java 17 builds are affected by a bug where the JVM can fail abruptly. Update your Java 17 installation to resolve the issue. See for details.
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: multi.md

This guidebook shows how to offer a checkbox-style selection to users. For example, pretend you are going shopping, what items do you want to purchase? === "Bananas [ ]" Add bananas to your basket. ```shell echo "You have purchased some ${choice}" ``` === "Rice [ ]" Add rice to your basket. ```shell echo "You have purchased some ${choice}" ``` === "Applesauce [ ]" Add applesauce to your basket. ```shell echo "You have purchased some ${choice}" ``` === "Tea [ ]" Add tea to your basket. ```shell echo "You have purchased some ${choice}" ```
Project: Apache Heron (App Definition and Development / Streaming & Messaging)
File: user-manuals-tracker-rest.md

id: version-0.20.5-incubating-user-manuals-tracker-rest title: Heron Tracker REST API sidebar_label: Heron Tracker REST API original_id: user-manuals-tracker-rest <!-- 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 API's documentation is within the application and is served automatically when started. Example of accessing documentation: ```shell heron-tracker --port=8080 ```
Project: ShardingSphere (App Definition and Development / Database)
File: create-sharding-table-reference-rule.en.md

+++ title = "CREATE SHARDING TABLE REFERENCE RULE" weight = 12 +++ The `CREATE SHARDING TABLE REFERENCE RULE` syntax is used to create reference rule for sharding tables {{< tabs >}} {{% tab name="Grammar" %}} ```sql CreateShardingTableReferenceRule ::= 'CREATE' 'SHARDING' 'TABLE' 'REFERENCE' 'RULE' ifNotExists? referenceRelationshipDefinition (',' referenceRelationshipDefinition)* ifNotExists ::= 'IF' 'NOT' 'EXISTS' referenceRelationshipDefinition ::= ruleName '(' tableName (',' tableName)* ')' ruleName ::= identifier tableName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} Sharding table reference rule can only be created for sharding tables; A sharding table can only be associated with one sharding table reference rule; The referenced sharding tables should be sharded in the same storage units and have the same number of sharding nodes. For example `ds${0..1}.torder${0..1}` and `ds${0..1}.torderitem_${0..1}`; The referenced sharding tables should use consistent sharding algorithms. For example `torder{orderid % 2}` and `torderitem{orderitemid % 2}`; `ifNotExists` clause used for avoid `Duplicate sharding table reference rule` error. ```sql -- Before creating a sharding table reference rule, you need to create sharding table rules torder, torder_item CREATE SHARDING TABLE REFERENCE RULE ref0 (torder,torderitem); ``` ```sql -- Before creating sharding table reference rules, you need to create sharding table rules torder, torderitem, tproduct, tproductitem CREATE SHARDING TABLE REFERENCE RULE ref0 (torder,torderitem), ref1 (tproduct,tproductitem); ``` ```sql CREATE SHARDING TABLE REFERENCE RULE IF NOT EXISTS ref0 (torder,torderitem); ``` `CREATE`, `SHARDING`, `TABLE`, `REFERENCE`, `RULE`
Project: Flink (App Definition and Development / Streaming & Messaging)
File: sql.md

title: "SQL" weight: 50 type: docs aliases: /dev/python/table-api-users-guide/sql.html <!-- 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. --> <meta http-equiv="refresh" content="0; url={{< ref "docs/dev/table/sql/overview" >}} "/>
Project: Kyverno (Provisioning / Security & Compliance)
File: kyverno_create_exception.md

Create a Kyverno policy exception file. Create a Kyverno policy exception file. ``` kyverno create exception [name] [flags] ``` ``` kyverno create exception my-exception --namespace my-ns --policy-rules "policy,rule-1,rule-2" --any "kind=Pod,kind=Deployment,name=test-*" ``` ``` --all stringArray List of resource filters --any stringArray List of resource filters -b, --background Set to false when policy shouldn't be considered in background scans (default true) -h, --help help for exception --namespace string Policy exception namespace -o, --output string Output path (uses standard console output if not set) --policy-rules --policy-rules=policy,rule-1,rule-2,... Policy name, followed by rule names (--policy-rules=policy,rule-1,rule-2,...) ``` ``` --adddirheader If true, adds the file directory to the header of the log messages --alsologtostderr log to standard error as well as files (no effect when -logtostderr=true) --logbacktraceat traceLocation when logging hits line file:N, emit a stack trace (default :0) --log_dir string If non-empty, write log files in this directory (no effect when -logtostderr=true) --log_file string If non-empty, use this log file (no effect when -logtostderr=true) --logfilemax_size uint Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800) --logtostderr log to standard error instead of files (default true) --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true) --skip_headers If true, avoid header prefixes in the log messages --skiplogheaders If true, avoid headers when opening log files (no effect when -logtostderr=true) --stderrthreshold severity logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2) -v, --v Level number for the log level verbosity --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging ``` - Helps with the creation of various Kyverno resources.
Project: LinuxKit (Provisioning / Automation & Configuration)
File: 2017-03-12.md

The first weekly development report. Feel free to send PRs if you want to add to these reports (or correct them). At the beginning of the week we removed all the remaining parts of the previous "monolithic" builds that we used for editions, in favour of the new build tool and yaml files. There are a whole lot of parts that need putting back, for example ssh userdata support Docker Will get these restored over the next few days so the system is more useful and usable; it is rather minimal at present. There is an open issue for more reorganisation of the repo structure see https://github.com/docker/moby/issues/1266 Tycho @tych0 joined Docker this week, working on the kernel and security. Thomas @samoht at Docker is working on privilege separation in userspace. We welcome the IBM team, working on support for Bluemix, and look forward to their contributions: Lin Sun @linsun Eric Van Norman @ericvn Dave Freitag @davefreitag Also three of the Docker Captains Phil Estes (also IBM) @estesp Marcos Nils @marcosnils Jonathan Leibiusky @xetorthio Also the VMWare team Ben Corrie @corrieb Volodymyr Burenin @vburenin It is our first week bringing in external contributors, please ask for all the help you need on #moby in the community Slack and with issues and PRs on github, and we look forward to working with all of you (and more coming soon). Added support for more output formats in the yaml config, see https://github.com/docker/moby/pull/1279 and https://github.com/docker/moby/pull/1277 for qcow2, GCE compressed raw image and VHD. More to come such as direct AMI support. You can add these to your yaml config eg ``` outputs: format: vhd ``` Support for setting the kernel command line in the output format, removing the hard coded edition defaults. https://github.com/docker/moby/pull/1264 Support for generating configuration ISO images for hyperkit https://github.com/docker/moby/pull/1276 part of the move to make the hyperkit emulation environment look much more like a real cloud provider with consistent userdata support so that the hyperkit infrakit support can be a close model for real world "works on my laptop" usage https://github.com/docker/moby/tree/master/tools/infrakit.hyperkit The docs for how we maintain the kernel tree were updated https://github.com/docker/moby/blob/master/docs/kernel-patches.md Initial support for running the kernel LTP test suite https://github.com/docker/moby/pull/1282 as part of our roadmap for expanding testing. helping our new contributors get started two tutorials: single host get started guide, multi host get started guide yaml configuration file documentation restoring missing parts (ssh, userdata, docker, disk formatting), currently in progress, so system is more useful documentation there will be a talk by @justincormack on Moby (currently billed as containerd...) there will be a session and lots of time to talk at the Thursday summit - get in touch if you need an invite.