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

Welcome! We are glad that you want to contribute to our CloudNativePG project! As you get started, you are in the best position to give us feedbacks on areas of our project that we need help with, including: Problems found while setting up the development environment Gaps in our documentation Bugs in our Github actions Promotion of PostgreSQL on Kubernetes with our operator First, though, it is important that you read the [code of conduct](CODEOFCONDUCT.md). The guidelines below are a starting point. We don't want to limit your creativity, passion, and initiative. If you think there's a better way, please feel free to bring it up in a Github discussion, or open a pull request. We're certain there are always better ways to do things, we just need to start some constructive dialogue! We welcome many types of contributions including: New features Builds, CI/CD Bug fixes Issue Triage Answering questions on Slack or Github Discussions Web design Communications / Social Media / Blog Posts Events participation Release management For development contributions, please refer to the separate section called . The best way to reach us with a question when contributing is to drop a line in our , or start a new Github discussion. When raising issues, please specify the following: Setup details as specified in the issue template A scenario where the issue occurred (with details on how to reproduce it) Errors and log messages that are displayed by the involved software Any other detail that might be useful If you are trying to report a vulnerability, please refer to the . We extend a warm welcome to everyone to join any of our meetings. For further details, please visit the page.
Project: YugabyteDB (App Definition and Development / Database)
File: create_database,create_database_options.grammar.md

```output.ebnf createdatabase ::= CREATE DATABASE name [ createdatabase_options ] createdatabaseoptions ::= [ WITH ] [ OWNER [ = ] user_name ] [ TEMPLATE [ = ] template ] [ ENCODING [ = ] encoding ] [ LCCOLLATE [ = ] lccollate ] [ LCCTYPE [ = ] lcctype ] [ ALLOW_CONNECTIONS [ = ] allowconn ] [ CONNECTION LIMIT [ = ] connlimit ] [ IS_TEMPLATE [ = ] istemplate ] [ COLOCATED [ = ] { 'true' | 'false' } ] ```
Project: Vald (App Definition and Development / Database)
File: network-policy.md

is a Kubernetes feature that controls ingress and egress network traffic for pods. In Vald, you can set network policies as follows. Please note that are required for using network policies. Even if you configure the following settings in a cluster that does not meet the prerequisites, network policies will not be effective. To enable network policies in a Vald cluster, set `defaults.networkPolicy.enabled` to `true` as follows: ```yaml defaults: networkPolicy: enabled: true ``` This sets the following ingress/egress rules between Vald components (these are the minimum required rules for a Vald cluster to work). | from / to | agent | discoverer | filter gateway | lb gateway | index manager | kube-system | | :- | :: | :--: | :: | :--: | :--: | :: | | agent | N/A | | | | | | | discoverer | | N/A | | | | | | filter gateway | | | N/A | | | | | lb gateway | | | | N/A | | | | index manager | | | | | N/A | | There may be cases where you want to connect a Vald cluster to external components. Specifically, for the following cases: Enable egress to `OpenTelemetryCollector` to use Enable egress to an external filter component to use . To handle such cases, Vald allows you to set user custom network policies using the `defaults.networkPolicy.custom` field as follows: ```yaml defaults: networkPolicy: enabled: true custom: ingress: from: podSelector: matchLabels: app.kubernetes.io/name: pyroscope egress: to: podSelector: matchLabels: app.kubernetes.io/name: opentelemetry-collector-collector ``` Please write down the same notation as the `ingress/egress` field of in our `custom` field. Currently, these custom network policies are applied to all Vald components.
Project: StarRocks (App Definition and Development / Database)
File: array_concat.md

displayed_sidebar: "English" Concatenates multiple arrays into one array that contains all the elements in the arrays. Elements in the arrays to concatenate can be of the same type or different types. However, we recommend that the elements be of the same type. Nulls are processed as normal values. ```Haskell array_concat(input0, input1, ...) ``` `input`: one or more arrays that you want to concatenate. Specify arrays in the `(input0, input1, ...)` format. This function supports the following types of array elements: BOOLEAN, TINYINT, SMALLINT, INT, BIGINT, LARGEINT, FLOAT, DOUBLE, VARCHAR, DECIMALV2, DATETIME, DATE, and JSON. JSON is supported from 2.5. Returns an array that contains all the elements held in the arrays that are specified by the `input` parameter. The elements of the returned array are of the same data type as the elements of the input arrays. Additionally, the elements of the returned array follow the order of the input arrays and their elements. Example 1: Concatenate arrays that contain numeric elements. ```plaintext select array_concat([57.73,97.32,128.55,null,324.2], [3], [5]) as res; +-+ | res | +-+ | [57.73,97.32,128.55,null,324.2,3,5] | +-+ ``` Example 2: Concatenate arrays that contain string elements. ```plaintext select array_concat(["sql","storage","execute"], ["Query"], ["Vectorized", "cbo"]); +-+ | array_concat(['sql','storage','execute'], ['Query'], ['Vectorized','cbo']) | +-+ | ["sql","storage","execute","Query","Vectorized","cbo"] | +-+ ``` Example 3: Concatenate two arrays of different types. ```plaintext select array_concat([57,65], ["pear","apple"]); +-+ | array_concat([57, 65], ['pear', 'apple']) | +-+ | ["57","65","pear","apple"] | +-+ ``` Example 4: Process nulls as normal values. ```plaintext select array_concat(["sql",null], [null], ["Vectorized", null]); ++ | array_concat(['sql',NULL], [NULL], ['Vectorized',NULL]) | ++ | ["sql",null,null,"Vectorized",null] | ++ ```
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_version.md

title: "devspace version --help" sidebar_label: devspace version Prints version of devspace ``` devspace version [flags] ``` ``` -h, --help help for version ``` ``` --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems --kube-context string The kubernetes context to use --kubeconfig string The kubeconfig path to use -n, --namespace string The kubernetes namespace to use --no-colors Do not show color highlighting in log output. This avoids invisible output with different terminal background colors --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before --override-name string If specified will override the DevSpace project name provided in the devspace.yaml -p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ``` ``` ```
Project: Kapitan (Provisioning / Automation & Configuration)
File: parameters_interpolation.md

!!! note as a shorthand, when we encounter deep yaml structures like the following: ```yaml parameters: components: nginx: image: nginx:latest ``` Usually when we want to talk about the `image` subkey, we normally use either of the following: `parameters.components.nginx.image` `components.nginx.image` However, when used in parameter expansion, remember to: replace the `.` with `:` omit the `parameters` initial key which is implied wrap it into the `${}` variable interpolation syntax The correct way to reference `parameters.nginx.image` then becomes `${components:nginx:image}`. The allows you to refer to other values defined elsewhere in the structure, using parameter interpolation. Given the example: ```yaml parameters: cluster: location: europe application: location: ${cluster:location} namespace: ${target_name} target_name: dev ``` Here we tell Kapitan that: `namespace` should take the same value defined in `target_name` `target_name` should take the literal string `dev` `application.location` should take the same value as defined in `cluster.location` It is important to notice that the inventory can refer to values defined in other classes, as long as they are imported by the target. So for instance with the following example ```yaml classes: project.production parameters: application: location: ${cluster.location} ``` Here in this case `application.location` refers to a value `location` which has been defined elsewhere, perhaps (but not necessarily) in the `project.production` class. Also notice that the class name (`project.production`) is not in any ways influencing the name or the structed of the yaml it imports into the file
Project: StarRocks (App Definition and Development / Database)
File: duplicate_key_table.md

displayed_sidebar: "English" The Duplicate Key table is the default model in StarRocks. If you did not specify a model when you create a table, a Duplicate Key table is created by default. When you create a Duplicate Key table, you can define a sort key for that table. If the filter conditions contain the sort key columns, StarRocks can quickly filter data from the table to accelerate queries. The Duplicate Key table is suitable for scenarios, such as analyzing logs data. It supports appending new data, but does not support modifying historical data. The Duplicate Key table is suitable for the following scenarios: Analyze raw data, such as raw logs and raw operation records. Query data by using a variety of methods without being limited by the pre-aggregation method. Load log data or time-series data. New data is written in append-only mode, and existing data is not updated. Suppose that you want to analyze the event data over a specific time range. In this example, create a table named `detail` and define `eventtime` and `eventtype` as sort key columns. Statement for creating the table: ```SQL CREATE TABLE detail ( event_time DATETIME NOT NULL COMMENT "datetime of event", event_type INT NOT NULL COMMENT "type of event", user_id INT COMMENT "id of user", device_code INT COMMENT "device code", channel INT COMMENT "") ORDER BY (eventtime, eventtype); ``` Sort key Since v3.3.0, the Duplicate Key table supports specifying the sort key using `ORDER BY`, which can be combination of any columns. If both `ORDER BY` and `DUPLICATE KEY` are used, `DUPLICATE KEY` does not take effect. If neither `ORDER BY` nor `DUPLICATE KEY` is used, the first three columns of the table are used as the sort key by default. Bucketing Bucketing method: Since v3.1.0, StarRocks supports random bucketing for Duplicate Key tables (the default bucketing method). When creating tables or adding partitions, you do not need to set the hash bucketing key (that is the `DISTRIBUTED BY HASH` clause). Before v3.1.0, StarRocks only supports hash bucketing. You need to set the hash bucketing key (that is the `DISTRIBUTED BY HASH` clause) when creating tables or adding partitions, otherwise the table fails to be created. For more information on hash bucketing keys, see . Bucket number: Since v2.5.7, StarRocks can automatically set the number of buckets (BUCKETS) when you create a table or add a partition. You no longer need to manually set the number of buckets. For detailed information, see . When you create a table, you can create Bitmap indexes or Bloom Filter indexes on the all columns of the table. After a table is created, you can use various data ingestion methods to load data into StarRocks. For information about the data ingestion methods that are supported by StarRocks, see . :::note When you load data into a table that uses the Duplicate Key table, you can only append data to the table. You cannot modify the existing data in the table. If two identical records are loaded, the Duplicate Key table retains them as two records, rather than one. :::
Project: Meshery (Provisioning / Automation & Configuration)
File: pg-operator.md

layout: integration title: Percona Postgres Operator subtitle: Create and manage highly available, enterprise-ready MySQL, PostgreSQL, and MongoDB clusters on Kubernetes. image: /assets/img/integrations/pg-operator/icons/color/pg-operator-color.svg permalink: extensibility/integrations/pg-operator docURL: https://docs.meshery.io/extensibility/integrations/pg-operator description: integrations-category: Database integrations-subcategory: App Definition and Development registrant: Artifact Hub components: name: percona-pg-backup colorIcon: assets/img/integrations/pg-operator/components/percona-pg-backup/icons/color/percona-pg-backup-color.svg whiteIcon: assets/img/integrations/pg-operator/components/percona-pg-backup/icons/white/percona-pg-backup-white.svg description: name: percona-pg-cluster colorIcon: assets/img/integrations/pg-operator/components/percona-pg-cluster/icons/color/percona-pg-cluster-color.svg whiteIcon: assets/img/integrations/pg-operator/components/percona-pg-cluster/icons/white/percona-pg-cluster-white.svg description: name: percona-pg-restore colorIcon: assets/img/integrations/pg-operator/components/percona-pg-restore/icons/color/percona-pg-restore-color.svg whiteIcon: assets/img/integrations/pg-operator/components/percona-pg-restore/icons/white/percona-pg-restore-white.svg description: featureList: [ "Create and manage highly available, enterprise-ready MySQL, PostgreSQL, and MongoDB clusters on Kubernetes.", "Percona Operators include backup/restore, high availability, replication, sharding, logging features and more.", "Create ready-to-use database clusters of open source, enterprise-ready versions of MySQL, MongoDB, and PostgreSQL, created and supported by the Percona team." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.63-rc-1.md

layout: release date: 2021-10-04 tag: v0.5.63-rc-1 [Performance] Performance REST API migration to GraphQL @bariqhibat (#3960) added undefined check in columns @manav1403 (#4284) added remote dependency for icon @warunicorn19 (#4282) Kubernetes as default platform to deploy Meshery @navendu-pottekkat (#4328) [mesheryctl] Add unit tests for utils/platform @krithikvaidya (#4134) Fix pinning version on latest channel in Docker platform @navendu-pottekkat (#4276) changed modal styles to maintain consistency @warunicorn19 (#4316) added maximize and minimize to filters @warunicorn19 (#4278) [UI] Add smp icon @sudo-NithishKarthik (#4271) Import using url - Patterns and Filters @Meghana-12 (#4212) Added support for k8s pattern generation @Revolyssup (#4277) use latest version of jsonschema utility in meshery container image @DelusionalOptimist (#4272) [mesheryctl] Add unit tests for utils/platform @krithikvaidya (#4134) Bump nodemon from 2.0.12 to 2.0.13 in /provider-ui @dependabot (#4294) Bump jss from 10.7.1 to 10.8.0 in /provider-ui @dependabot (#4297) Bump glob-parent from 6.0.1 to 6.0.2 in /provider-ui @dependabot (#4293) Bump react-redux from 7.2.4 to 7.2.5 in /ui @dependabot (#4299) Bump immutable from 4.0.0-rc.14 to 4.0.0-rc.15 in /ui @dependabot (#4302) Bump start-server-and-test from 1.13.1 to 1.14.0 in /provider-ui @dependabot (#4291) Bump cypress from 8.3.1 to 8.5.0 in /provider-ui @dependabot (#4288) Bump @cypress/code-coverage from 3.9.10 to 3.9.11 in /provider-ui @dependabot (#4287) Bump eslint-plugin-cypress from 2.11.3 to 2.12.1 in /ui @dependabot (#4292) Bump github.com/layer5io/meshery-operator from 0.2.20 to 0.2.21 @dependabot (#4307) Bump @cypress/code-coverage from 3.9.10 to 3.9.11 in /ui @dependabot (#4300) Bump eslint-plugin-cypress from 2.11.3 to 2.12.1 in /provider-ui @dependabot (#4290) Bump eslint-plugin-react from 7.24.0 to 7.26.1 in /ui @dependabot (#4303) Bump jss from 10.7.1 to 10.8.0 in /ui @dependabot (#4289) Bump github.com/prometheus/common from 0.30.0 to 0.31.1 @dependabot (#4311) Bump @fortawesome/free-regular-svg-icons from 5.15.3 to 5.15.4 in /ui @dependabot (#4304) Bump eslint-plugin-react from 7.25.1 to 7.26.1 in /provider-ui @dependabot (#4296) [CI] e2e tests for multiple k8s versions using meshery-smp-action @DelusionalOptimist (#4279) use latest version of jsonschema utility in meshery container image @DelusionalOptimist (#4272) Kubernetes as default platform to deploy Meshery @navendu-pottekkat (#4328) Update ROADMAP.md @vedant-kakde (#4286) Update perf docs: instructions to download token and update action configuration @navendu-pottekkat (#4281) Add instructions for installing Meshery on EKS cluster @alphaX86 (#4090) first draft on guide to authenticate @warunicorn19 (#4252) Thank you to our contributors for making this release possible: @DelusionalOptimist, @Meghana-12, @Revolyssup, @adithyaakrishna, @alphaX86, @bariqhibat, @dependabot, @dependabot[bot], @dhruv0000, @krithikvaidya, @leecalcote, @manav1403, @navendu-pottekkat, @piyushsingariya, @sudo-NithishKarthik, @utkarsh-pro, @vedant-kakde and @warunicorn19
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.96.md

layout: release date: 2023-06-15 tag: v0.6.96 Update nighthawk binary verison @MUzairS15 (#7872) Update cncf-playground-deploy-meshery.yaml @leecalcote (#7871) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @MUzairS15 and @leecalcote
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-12700.en.md

Support "b" and "B" unit in bytesize hocon fields. For example, all three fields below will have the value of 1024 bytes: ``` bytesize_field = "1024b" bytesize_field2 = "1024B" bytesize_field2 = 1024 ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: LICENSE.md

Copyright (c) 2018-2023, Sylabs Inc. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v1.6.1.md

This hotfix release only updates the MongoDB State Store component to address a data serialization problem. An upgrade to this release is only recommended for users of this component. MongoDB State Store Component: Fixes an issue where actor reminders are broken when using the MongoDB State Store component as actor state store https://github.com/dapr/components-contrib/issues/1355. MongoDB State Store Component: Fixes an issue where array values could not be retrieved due to a serialization error. MongoDB State Store Component: Fixes an issue where MongoDB internal data types are returned in the State Store API response. When using MongoDB as actor state store actor reminders can no longer be loaded or written. Array values (e.g. `[{'item1':'value1'},{'item2':'value2'}]`) can not be retrieved via the State Store API. The JSON response includes unexpected artifacts from the internal BSON representation. For example `{"state":"OR","propertyType":"apartment","id":{"$numberDouble":"1003.1"},"city":"Portland"}` when `{"state":"OR","propertyType":"apartment","id":1003.1,"city":"Portland"}` is expected instead. With the introduction of the State Store Query API preview feature in release 1.5.1 data is no longer stored as a string encoded value, but instead as the MongoDB native BSON data types. Not all possible data types were being serialized correctly upon retrieval via the State Store API. Additionally, the internal BSON response was not correctly converted to JSON, thereby including BSON specific data type information in the final JSON representation. These issues were resolved with an update to the MongoDB component data retrieval serialization to properly convert from MongoDB BSON to JSON representation, also adding a special serialization step for array values at the top level of the document.