cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: LICENSE.md

The MIT License (MIT) Copyright (c) 2014 Mitchell Hashimoto Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Project: OpenYurt (Provisioning / Automation & Configuration)
File: PULL_REQUEST_TEMPLATE.md

<!-- Thanks for sending a pull request! Here are some tips for you: https://github.com/openyurtio/openyurt/blob/master/CONTRIBUTING.md --> Uncomment only one `/kind <>` line, hit enter to put that in a new line, and remove leading whitespace from that line: /kind bug /kind documentation /kind enhancement /kind good-first-issue /kind feature /kind question /kind design /sig ai /sig iot /sig network /sig storage <!-- *Automatically closes linked issue when PR is merged. Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. --> Fixes # <!-- use this label to assign your reviewer /assign @your_reviewer --> <!-- If no, just write "NONE" in the release-note block below. If yes, a release note is required: Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required". --> ```release-note ``` <!-- If your current PR is still working in process, start the PR title name with [WIP], such as: [WIP] add new crd for yurt-app-manager If the PR title name begins with [WIP], OpenYurt-bot automatically adds a do-not-merge/work-in-progress label for your pr -->
Project: Vitess (App Definition and Development / Database)
File: eol-process.md

The lifespan of a major version is one year long, after that time, the version has reached its end-of-life. To properly deprecate a major of Vitess follow the following steps: Update the website documentation > - In the , the EOL version must be moved under the . > - The sidebar of the website must be changed. We need to remove the EOL version from it. To do so, we move the version folder onto the `archive` folder. Delete the `Backport To: ...` label > - Delete the corresponding label for the EOL version, we do not want to motivate anymore backport to the EOL release branch. Make proper announcement on Slack > - Notify the community of this deprecation.
Project: StarRocks (App Definition and Development / Database)
File: ALTER_ROUTINE_LOAD.md

displayed_sidebar: "English" import RoutineLoadPrivNote from '../../../assets/commonMarkdown/RoutineLoadPrivNote.md' Alters a Routine Load job that is in the `PAUSED` state. You can execute PAUSE ROUTINE LOAD to pause a Routine Load job. After successfully altering a Routine Load job, you can: Check the modifications made to the Routine Load job by using . Resume the Routine Load job by using . <RoutineLoadPrivNote /> ```SQL ALTER ROUTINE LOAD FOR [<dbname>.]<jobname> [load_properties] [job_properties] FROM data_source [datasourceproperties] ``` `[<db_name>.]<job_name>` `db_name`: Optional. The name of the StarRocks database. `job_name`: Required. The name of the Routine Load job to be altered. `load_properties` The properties of the source data to be loaded. The syntax is as follows: ```SQL [COLUMNS TERMINATED BY '<column_separator>'], [ROWS TERMINATED BY '<row_separator>'], [COLUMNS ([<columnname> [, ...] ] [, columnassignment [, ...] ] )], [WHERE <expr>], [PARTITION ([ <partition_name> [, ...] ])] [TEMPORARY PARTITION (<temporarypartition1name>[,<temporarypartition2name>,...])] ``` For detailed parameter descriptions, see . `job_properties` The properties of the load job. The syntax is as follows: ```SQL PROPERTIES ("<key1>" = "<value1>"[, "<key2>" = "<value2>" ...]) ``` Only the following parameters can be altered: `desiredconcurrentnumber` `maxerrornumber` `maxbatchinterval` `maxbatchrows` `maxbatchsize` `jsonpaths` `json_root` `stripouterarray` `strict_mode` `timezone` For detailed parameter descriptions, see . `data_source` and `data_source_properties` `data_source` Required. The source of the data you want to load. Valid value: `KAFKA`. `data_source_properties` The properties of the data source. Currently, only the following properties can be altered: `kafkapartitions` and `kafkaoffsets`: Note that StarRocks only supports modifying the offset of Kafka partitions that have already been consumed but does not support adding new Kafka partitions. `property.*`: Custom parameters for the data source Kafka, such as `property.kafkadefaultoffsets`. The following example increases the value of the property `desiredconcurrentnumber` of the load job to `5` in order to increase the parallelism of load tasks. For details on task parallelism, see . ```SQL ALTER ROUTINE LOAD FOR exampletblordertest PROPERTIES ( "desiredconcurrentnumber" = "5" ); ``` The following example alters the load job's properties and data source information at the same time. ```SQL ALTER ROUTINE LOAD FOR exampletblordertest PROPERTIES ( "desiredconcurrentnumber" = "5" ) FROM KAFKA ( "kafka_partitions" = "0, 1, 2", "kafka_offsets" = "100, 200, 100", "property.group.id" = "new_group" ); ``` The following example alters the filtering condition and the StarRocks partitions that data is loaded into at the same time. ```SQL ALTER ROUTINE LOAD FOR exampletblordertest WHERE pay_dt < 2023-06-31 PARTITION (p202306); ```
Project: YugabyteDB (App Definition and Development / Database)
File: create_extension.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="1206" height="50" viewbox="0 0 1206 50"><path class="connector" d="M0 22h15m67 0h10m91 0h30m32 0h10m45 0h10m64 0h20m-196 0q5 0 5 5v8q0 5 5 5h171q5 0 5-5v-8q0-5 5-5m5 0h10m120 0h30m53 0h20m-88 0q5 0 5 5v8q0 5 5 5h63q5 0 5-5v-8q0-5 5-5m5 0h30m71 0h10m108 0h20m-224 0q5 0 5 5v8q0 5 5 5h199q5 0 5-5v-8q0-5 5-5m5 0h30m75 0h10m63 0h20m-183 0q5 0 5 5v8q0 5 5 5h158q5 0 5-5v-8q0-5 5-5m5 0h30m77 0h20m-112 0q5 0 5 5v8q0 5 5 5h87q5 0 5-5v-8q0-5 5-5m5 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="67" height="25" rx="7"/><text class="text" x="25" y="22">CREATE</text><rect class="literal" x="92" y="5" width="91" height="25" rx="7"/><text class="text" x="102" y="22">EXTENSION</text><rect class="literal" x="213" y="5" width="32" height="25" rx="7"/><text class="text" x="223" y="22">IF</text><rect class="literal" x="255" y="5" width="45" height="25" rx="7"/><text class="text" x="265" y="22">NOT</text><rect class="literal" x="310" y="5" width="64" height="25" rx="7"/><text class="text" x="320" y="22">EXISTS</text><a xlink:href="../../../syntaxresources/grammardiagrams#extension-name"><rect class="rule" x="404" y="5" width="120" height="25"/><text class="text" x="414" y="22">extensionname</text></a><rect class="literal" x="554" y="5" width="53" height="25" rx="7"/><text class="text" x="564" y="22">WITH</text><rect class="literal" x="657" y="5" width="71" height="25" rx="7"/><text class="text" x="667" y="22">SCHEMA</text><a xlink:href="../../../syntaxresources/grammardiagrams#schema-name"><rect class="rule" x="738" y="5" width="108" height="25"/><text class="text" x="748" y="22">schemaname</text></a><rect class="literal" x="896" y="5" width="75" height="25" rx="7"/><text class="text" x="906" y="22">VERSION</text><a xlink:href="../../../syntaxresources/grammardiagrams#version"><rect class="rule" x="981" y="5" width="63" height="25"/><text class="text" x="991" y="22">version</text></a><rect class="literal" x="1094" y="5" width="77" height="25" rx="7"/><text class="text" x="1104" y="22">CASCADE</text><polygon points="1202,29 1206,29 1206,15 1202,15" style="fill:black;stroke-width:0"/></svg>
Project: ShardingSphere (App Definition and Development / Database)
File: mode.en.md

+++ title = "Mode" weight = 1 +++ ```yaml mode (?): # Default value is Standalone type: # Type of mode configuration. Values could be: Standalone, Cluster repository (?): # Persist repository configuration ``` ```yaml mode: type: Standalone repository: type: # Type of persist repository props: # Properties of persist repository fookey: foovalue barkey: barvalue ``` ```yaml mode: type: Cluster repository: type: # Type of persist repository props: # Properties of persist repository namespace: # Namespace of registry center server-lists: # Server lists of registry center fookey: foovalue barkey: barvalue ``` Cluster mode deployment is recommended for production environment. The `ZooKeeper` registry center is recommended for cluster mode deployment. If there is configuration information in the `ZooKeeper`, please refer to the config information there. ```yaml mode: type: Standalone repository: type: JDBC ``` ```yaml mode: type: Cluster repository: type: ZooKeeper props: namespace: governance server-lists: localhost:2181 retryIntervalMilliseconds: 500 timeToLiveSeconds: 60 ``` Using the persistent repository requires additional introduction of the corresponding Maven dependencies. It is recommended to use: ```xml <dependency> <groupId>org.apache.shardingsphere</groupId> <artifactId>shardingsphere-cluster-mode-repository-zookeeper</artifactId> <version>${shardingsphere.version}</version> </dependency> ``` Please refer to for more details about the type of repository. Please refer to for more implementations of the persistent repository.
Project: StarRocks (App Definition and Development / Database)
File: json-operators.md

displayed_sidebar: "English" StarRocks supports the following JSON comparison operators: `<`, `<=`, `>`, `>=`, `=`, and `!=`. You can use these operators to query JSON data. However, StarRocks does not allow you to use `IN` to query JSON data. > The operands of an operator must both be JSON values. > If one operand of an operator is a JSON value while the other is not, the operand that is not a JSON value is converted to a JSON value during the arithmetic operation. For more information about the conversion rules, see . JSON operators comply with the following arithmetic rules: When the operands of an operator are JSON values of the same data type: If both operands are JSONs values of a basic data type, such as NUMBER, STRING, or BOOLEAN, the operator performs the arithmetic operation in compliance with the arithmetic rules for the basic data type. Note: If both operands are numbers but one is a DOUBLE value and the other is an INT value, the operator converts the INT value to a DOUBLE value. If both operands are JSON values of a composite data type, such as OBJECT or ARRAY, the operator sorts the keys in the operands in dictionary order based on the sequence of the keys in the first operand and then compares the values of the keys between the operands. Example 1: The first operand is `{"a": 1, "c": 2}`, and the second operand is `{"b": 1, "a": 2}`. In this example, the operator compares the values of the keys `a` between the operands. The value of the key `a` in the first operand is `1`, whereas the value of the key `a` in the second operand is `2`. The value `1` is greater than the value `2`. Therefore, the operator concludes that the first operand `{"a": 1, "c": 2}` is less than the second operand `{"b": 1, "``a``": 2}`. ```plaintext mysql> SELECT PARSEJSON('{"a": 1, "c": 2}') < PARSEJSON('{"b": 1, "a": 2} '); -> 1 ``` Example 2: The first operand is `{"a": 1, "c": 2}`, and the second operand is `{"b": 1, "a": 1}`. In this example, the operator first compares the values of the keys `a` between the operands. The values of the keys `a` in the operands are both `1`. Then, the operator compares the values of the keys `c` in the operands. The second operand does not contain the key `c`. Therefore, the operator concludes that the first operand `{"a": 1, "c": 2}` is greater than the second operand `{"b": 1, "a": 1}`. ```plaintext mysql> SELECT PARSEJSON('{"a": 1, "c": 2}') < PARSEJSON('{"b": 1, "a": 1}'); -> 0 ``` When the operands of an operator are JSON values of two distinct data types, the operator compares the operands in compliance with the following arithmetic rules: NULL < BOOLEAN < ARRAY < OBJECT < DOUBLE < INT < STRING. ```plaintext mysql> SELECT PARSEJSON('"a"') < PARSEJSON('{"a": 1, "c": 2}'); -> 0 ```
Project: YDB (App Definition and Development / Database)
File: storage-device-requirements.md

For {{ ydb-short-name }} to work efficiently, we recommend using physical (not virtual) disks larger than 800 GB as block devices. The minimum disk size is 80 GB, otherwise the {{ ydb-short-name }} node won't be able to use the device. Correct and uninterrupted operation with minimum-size disks is not guaranteed. We recommend using such disks exclusively for informational purposes. {% note warning %} Configurations with disks less than 800 GB or any types of storage system virtualization cannot be used for production services or system performance testing. We don't recommend storing {{ ydb-short-name }} data on disks shared with other processes (for example, the operating system). {% endnote %}
Project: KICS (Provisioning / Security & Compliance)
File: dbe058d7-b82e-430b-8426-992b2e4677e7.md

title: COS Node Image Not Used hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: dbe058d7-b82e-430b-8426-992b2e4677e7 Query name: COS Node Image Not Used Platform: GoogleDeploymentManager Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: The node image should be Container-Optimized OS(COS)<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" resources: name: nodePool type: container.v1.nodePool properties: name: my-node config: imageType: ubuntu ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: nodePool type: container.v1.nodePool properties: name: my-node config: imageType: cos ``` ```yaml title="Negative test num. 2 - yaml file" resources: name: nodePool type: container.v1.nodePool properties: name: my-node config: imageType: cos_containerd ``` ```yaml title="Negative test num. 3 - yaml file" resources: name: nodePool type: container.v1.nodePool properties: name: my-node ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.26.md

layout: release date: 2022-11-15 tag: v0.6.26 language: en Bump loader-utils from 1.4.0 to 1.4.1 in /install/docker-extension/ui @dependabot (#6506) [Server] download package only when user has the capability @Abhishek-kumar09 (#6525) Bump loader-utils and styled-jsx in /provider-ui @dependabot (#6507) node version update to 18 in workflow and remove the platform related npm build @Abhishek-kumar09 (#6531) file:ui/components/Popup.js bug fix for 6488 @franklinekoh (#6515) Fix detection of type of meshery deployment @MUzairS15 (#6431) Bump loader-utils and styled-jsx in /provider-ui @dependabot (#6507) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @MUzairS15, @dependabot, @franklinekoh, @leecalcote and @warunicorn19
Project: Checkov (Provisioning / Security & Compliance)
File: Argo Workflows.md

layout: default published: true title: Argo Workflows configuration scanning nav_order: 20 Checkov supports the evaluation of policies on your Argo Workflows files. When using checkov to scan a directory that contains Argo Workflows specs and templates it will validate if the file is compliant with Argo Workflows best practices such as usage of securityContext and non default serviceAccountName, and more. Full list of Argo Workflows policies checks can be found . ```yaml apiVersion: argoproj.io/v1alpha1 kind: Workflow metadata: generateName: hello-world- spec: entrypoint: whalesay serviceAccountName: custom-sa templates: name: whalesay container: image: docker/whalesay:latest command: [cowsay] args: ["hello world"] ``` ```bash checkov -d . --framework argo_workflows ``` ```bash _| | _ | | / | '_ \ / _ \/ | |/ / _ \ \ / / | (| | | | / (| < (_) \ V / \_|_| |_|\|\|_|\_\/ \/ By Prisma Cloud | version: 2.0.1210 argo_workflows scan results: Passed checks: 1, Failed checks: 1, Skipped checks: 0 Check: CKVARGO1: "Ensure Workflow pods are not using the default ServiceAccount" PASSED for resource: /helloworld.yaml.spec.spec.CKVARGO_1[6:14] File: /hello_world.yaml:6-15 Check: CKVARGO2: "Ensure Workflow pods are running as non-root user" FAILED for resource: /helloworld.yaml.spec.spec.CKVARGO_2[6:14] File: /hello_world.yaml:6-15 6 | entrypoint: whalesay 7 | serviceAccountName: custom-sa 8 | templates: 9 | - name: whalesay 10 | container: 11 | image: docker/whalesay:latest 12 | command: [cowsay] 13 | args: ["hello world"] ```
Project: Veinmind Tools (Provisioning / Security & Compliance)
File: veinmind-runner_authz.md

Authz as docker plugin ``` veinmind-runner authz [flags] ``` ``` -c, --config string authz config path -h, --help help for authz ``` ``` -e, --exit-code int exit-code when veinmind-runner find security issues -g, --glob string specifies the pattern of plugin file to find -o, --output string output filepath of report --threads int threads for scan action (default 5) ``` -
Project: ORY Hydra (Provisioning / Key Management)
File: JsonWebKeySet.md

Name | Type | Description | Notes | - | - | - Keys | Pointer to | List of JSON Web Keys The value of the \&quot;keys\&quot; parameter is an array of JSON Web Key (JWK) values. By default, the order of the JWK values within the array does not imply an order of preference among them, although applications of JWK Sets can choose to assign a meaning to the order for their purposes, if desired. | [optional] `func NewJsonWebKeySet() *JsonWebKeySet` NewJsonWebKeySet instantiates a new JsonWebKeySet object This constructor will assign default values to properties that have it defined, and makes sure properties required by API are set, but the set of arguments will change when the set of required properties is changed `func NewJsonWebKeySetWithDefaults() *JsonWebKeySet` NewJsonWebKeySetWithDefaults instantiates a new JsonWebKeySet object This constructor will only assign default values to properties that have it defined, but it doesn't guarantee that properties required by API are set `func (o *JsonWebKeySet) GetKeys() []JsonWebKey` GetKeys returns the Keys field if non-nil, zero value otherwise. `func (o JsonWebKeySet) GetKeysOk() ([]JsonWebKey, bool)` GetKeysOk returns a tuple with the Keys field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *JsonWebKeySet) SetKeys(v []JsonWebKey)` SetKeys sets Keys field to given value. `func (o *JsonWebKeySet) HasKeys() bool` HasKeys returns a boolean if a field has been set.
Project: ThreatMapper (Provisioning / Security & Compliance)
File: aws-ecr.md

title: AWS ECR You can add your private and public ECR repositories to ThreatMapper to scan for vulnerabilities, secrets and malwares. Select `ECR` registry type from the registries section. Click on Add Registry button to get the following form: Enter `Registry Name` for reference later. Then, enter the other details as per the deployment. 2. Fill in the credentials(`AWS Access Key`, `AWS Secret Key`) for the user with access to the ECR registry. For private registry, fill in the `AWS Region` where the registry is located. Else, for public registry, toggle `Public Registry`. The Deepfence Console needs to be deployed on AWS EC2 instance in the same AWS account as the ECR registry and the EC2 instance needs to be assigned an IAM role with the correct permissions The IAM role to be assigned to the Deepfence Console EC2 instance can be deployed using CloudFormation with . . Change region, if required. Once completed, go to `Outputs` tab and copy the value of `InstanceProfileARN` Assign the instance profile to the EC2 instance on which the Deepfence Console is hosted. For private registry, fill in the `AWS Region` where the registry is located. Else, for public registry, toggle `Public Registry`. Leave the `AWS Account ID` and `Target Account Role ARN` fields blank as they are only used for the cross-account scenario below. If a user has an ECR registry in one AWS account and Deepfence Console is deployed in another AWS account, the user needs to set up cross-account ECR registry access as per the following steps: Create a role in the target ECR registry account which has required pull permissions. This can be deployed using CloudFormation with . Change region, if required. Once completed, go to `Outputs` tab and copy the value of `RoleARN` Create a role in the account where Deepfence Console is deployed to assume the role created in the step above. This can be achieved using CloudFormation with . . Paste the `RoleARN` copied from above step into `ECRAccessRole` box. Once completed, go to `Outputs` tab and copy the value of `InstanceProfileARN`. Assign the instance profile role ARN created above to the Deepfence Console EC2 instance. For private registry, fill in the `AWS Region` where the registry is located. Else, for public registry, toggle `Public Registry`. Fill the account id of the target account where registry is located in the `AWS Account ID` field. In the `Target Account Role ARN` field, paste the value of the `RoleARN` from the above steps.
Project: StarRocks (App Definition and Development / Database)
File: makedate.md

displayed_sidebar: "English" Creates and returns a date based on the given year and day of year values. This function is supported from v3.1. ```Haskell DATE makedate(INT year, INT dayOfYear); ``` `year`: It ranges from 0 to 9999. NULL is returned if this range is exceeded. The supported data type is INT. `dayOfYear`: the day of year. The supported data type is INT. In order to maintain the same semantics as the function , if this number is greater than 366 or is 366 in a non-leap year, it is not a day of year. Returns the date on the dayOfYear-th day of the given year. `year` must be in the range of [0,9999]. Otherwise, NULL is returned. `dayOfYear` must be between 1 and the number of days in the current year (365 in normal years, 366 in leap years). Otherwise, NULL is returned. The result is also NULL if either input parameter is NULL. ```Plain Text mysql> select makedate(2023,0); +-+ | makedate(2023, 0) | +-+ | NULL | +-+ mysql> select makedate(2023,32); +--+ | makedate(2023, 32) | +--+ | 2023-02-01 | +--+ mysql> select makedate(2023,365); ++ | makedate(2023, 365) | ++ | 2023-12-31 | ++ mysql> select makedate(2023,366); ++ | makedate(2023, 366) | ++ | NULL | ++ mysql> select makedate(9999,365); ++ | makedate(9999, 365) | ++ | 9999-12-31 | ++ mysql> select makedate(10000,1); +--+ | makedate(10000, 1) | +--+ | NULL | +--+ ``` MAKEDATE,MAKE