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

title: Network security headerTitle: Network security linkTitle: Network security description: Network security menu: v2.18_yugabyte-platform: parent: security identifier: network-security weight: 30 type: docs You need to ensure that YugabyteDB Anywhere and the database run in a trusted network environment. You should restrict machine and port access, based on the following guidelines: Servers running YugabyteDB services are directly accessible only by YugabyteDB Anywhere, servers running the application, and database administrators. Only YugabyteDB Anywhere and servers running applications can connect to YugabyteDB services on the RPC ports. Access to the YugabyteDB ports should be denied to everybody else. For information on ports that need to be opened on the YugabyteDB servers for YugabyteDB Anywhere and other applications to connect, see .
Project: Buildpacks (App Definition and Development / Application Definition & Image Build)
File: RELEASE.md

Pack follows a 6 week release cadence, composed of 3 phases: - One of the is designated as the release manager. They communicate the release status to the working group meetings, schedule additional meetings with the `pack` as needed, and finalize the release. They also take care of whatever release needs may arise. Our development flow is detailed in . 5 business days prior to a scheduled release, we enter `feature complete`. During this period, a Release Candidate (RC) is published and used for further User Acceptance testing (`UAT`). Furthermore, additional RCs may be published based on assessment by the `pack` of the impact, effort and risk of including the changes in the upcoming release. Any other changes may be merged into the `main` branch through the normal process, and will make it into the next release. To produce the release candidate the will: Create a new release branch in form `release/<VERSION>-rc<NUMBER>` yielding a draft GitHub release to be published. Publish the : Tag release branch as `v<VERSION>-rc<NUMBER>`. Release should be marked as "pre-release". The GitHub release will contain the following: artifacts release notes The release notes should be edited and cleaned Merge the release branch into `main`. The will: Create a new release branch in form `release/<VERSION>` yielding a draft GitHub release to be published. Publish the while tagging the release branch as `v<VERSION>`. Tag release branch as `v<VERSION>`. The GitHub release will contain the following: artifacts release notes migration guide (if necessary) Merge the release branch into `main`. Create a new for the next version, and set the delivery time in 6 weeks. Move all still open PRs/issues in the delivered milestone to the new milestone Close the delivered milestone Send out release notifications, if deemed necessary, on The Twitter Post release, you should be able to remove any acceptance test constraints (in ) in the `featureTests` struct. Create a PR removing them, in order to ensure our acceptance tests are clean. And with that, you're done! We release pack to a number of systems, including `homebrew`, `docker`, and `archlinux`. All of our delivery pipelines have workflow_dispatch triggers, if a maintainer needs to manually trigger them. To activate it, go to the , and select the desired workflow. Run it by providing the pack version to release, in the format `v<version>`. For more information, see the
Project: YugabyteDB (App Definition and Development / Database)
File: create_policy.grammar.md

```output.ebnf createpolicy ::= CREATE POLICY name ON tablename [ AS { PERMISSIVE | RESTRICTIVE } ] [ FOR { ALL | SELECT | INSERT | UPDATE | DELETE } ] [ TO { role_name | PUBLIC | CURRENT_USER | SESSION_USER } [ , ... ] ] [ USING ( using_expression ) ] [ WITH CHECK ( check_expression ) ] ```
Project: StarRocks (App Definition and Development / Database)
File: greatest.md

displayed_sidebar: "English" Returns the largest value from a list of one or more parameters. Generally, the return value has the same data type as the input. The parameters are compared based on the following rules: NULL is returned if any of the input parameters is NULL. If at least one parameter is of the DOUBLE type, all the parameters are compared as DOUBLE values. The same rule applies to the DECIMAL and FLOAT data types. If the parameters are a mix of numbers and strings but the strings can be converted into numbers, the parameters are compared as numbers. If the strings cannot be converted into numbers, the parameters are compared as strings. If the parameters are characters, they are compared based on the alphabetical order of the first letter. ```Haskell GREATEST(expr1,...); ``` `expr1`: the expression to compare. It supports the following data types: SMALLINT TINYINT INT BIGINT LARGEINT FLOAT DOUBLE DECIMALV2 DECIMAL32 DECIMAL64 DECIMAL128 DATETIME VARCHAR Example 1: Return the largest value for a single input. ```Plain mysql> select greatest(3); +-+ | greatest(3) | +-+ | 3 | +-+ 1 row in set (0.01 sec) ``` Example 2: Return the largest value from a list of values. ```Plain mysql> select greatest(3,4,5,5,6); +-+ | greatest(3, 4, 5, 5, 6) | +-+ | 6 | +-+ 1 row in set (0.00 sec) ``` Example 3: One parameter is of the DOUBLE type and a DOUBLE value is returned. ```Plain mysql> select greatest(7,4.5); ++ | greatest(7, 4.5) | ++ | 7.0 | ++ 1 row in set (0.05 sec) ``` Example 4: The input parameters are a mix of number and string but the string can be converted into a number. The parameters are compared as numbers. ```Plain mysql> select greatest(7,'9'); ++ | greatest(7, '9') | ++ | 9 | ++ 1 row in set (0.04 sec) ``` Example 5: The input parameters are a mix of number and string but the string cannot be converted into a number. The parameters are compared as strings. The string `'1'` is less than `'at'`. ```Plain select greatest(1,'at'); +-+ | greatest(1, 'at') | +-+ | at | +-+ ``` Example 6: The input parameters are characters. The letter `Z` has the largest value. ```Plain mysql> select greatest('A','B','Z'); +-+ | greatest('A', 'B', 'Z') | +-+ | Z | +-+ 1 row in set (0.00 sec) ``` GREATEST, greatest
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-system-migrate.1.md

% podman-system-migrate 1 podman\-system\-migrate - Migrate existing containers to a new podman version podman system migrate [options] podman system migrate migrates containers to the latest podman version. podman system migrate takes care of migrating existing containers to the latest version of podman if any change is necessary. "Rootless Podman uses a pause process to keep the unprivileged namespaces alive. This prevents any change to the `/etc/subuid` and `/etc/subgid` files from being propagated to the rootless containers while the pause process is running. For these changes to be propagated, it is necessary to first stop all running containers associated with the user and to also stop the pause process and delete its pid file. Instead of doing it manually, `podman system migrate` can be used to stop both the running containers and the pause process. The `/etc/subuid` and `/etc/subgid` files can then be edited or changed with usermod to recreate the user namespace with the newly configured mappings. Set a new OCI runtime for all containers. This can be used after a system upgrade which changes the default OCI runtime to move all containers to the new runtime. There are no guarantees that the containers continue to work under the new runtime, as some runtimes support differing options and configurations. , , usermod(8) April 2019, Originally compiled by Giuseppe Scrivano (gscrivan at redhat dot com)
Project: MongoDB (App Definition and Development / Database)
File: ABSEIL_ISSUE_TEMPLATE.md

Please submit a new Abseil Issue using the template below: -- -- [Provide the background information that is required in order to evaluate the proposed API changes. No controversial claims should be made here. If there are design constraints that need to be considered, they should be presented here along with justification for those constraints. Linking to other docs is good, but please keep the pertinent information as self contained as possible in this section.] [Please clearly describe the API change(s) being proposed. If multiple changes, please keep them clearly distinguished. When possible, use example code snippets to illustrate before-after API usages. List pros-n-cons. Highlight the main questions that you want to be answered. Given the Abseil project compatibility requirements, describe why the API change is safe.]
Project: ClickHouse (App Definition and Development / Database)
File: user_processes.md

slug: /en/operations/system-tables/user_processes This system table can be used to get overview of memory usage and ProfileEvents of users. Columns: `user` () User name. `memory_usage` () Sum of RAM used by all processes of the user. It might not include some types of dedicated memory. See the setting. `peakmemoryusage` () The peak of memory usage of the user. It can be reset when no queries are run for the user. `ProfileEvents` () Summary of ProfileEvents that measure different metrics for the user. The description of them could be found in the table ```sql SELECT * FROM system.user_processes LIMIT 10 FORMAT Vertical; ``` ```response Row 1: user: default memory_usage: 9832 peakmemoryusage: 9832 ProfileEvents: {'Query':5,'SelectQuery':5,'QueriesWithSubqueries':38,'SelectQueriesWithSubqueries':38,'QueryTimeMicroseconds':842048,'SelectQueryTimeMicroseconds':842048,'ReadBufferFromFileDescriptorRead':6,'ReadBufferFromFileDescriptorReadBytes':234,'IOBufferAllocs':3,'IOBufferAllocBytes':98493,'ArenaAllocChunks':283,'ArenaAllocBytes':1482752,'FunctionExecute':670,'TableFunctionExecute':16,'DiskReadElapsedMicroseconds':19,'NetworkSendElapsedMicroseconds':684,'NetworkSendBytes':139498,'SelectedRows':6076,'SelectedBytes':685802,'ContextLock':1140,'RWLockAcquiredReadLocks':193,'RWLockReadersWaitMilliseconds':4,'RealTimeMicroseconds':1585163,'UserTimeMicroseconds':889767,'SystemTimeMicroseconds':13630,'SoftPageFaults':1947,'OSCPUWaitMicroseconds':6,'OSCPUVirtualTimeMicroseconds':903251,'OSReadChars':28631,'OSWriteChars':28888,'QueryProfilerRuns':3,'LogTrace':79,'LogDebug':24} 1 row in set. Elapsed: 0.010 sec. ```
Project: StarRocks (App Definition and Development / Database)
File: dayofmonth.md

displayed_sidebar: "English" Obtains the day part in a date and returns a value that ranges from 1 to 31. The `date` parameter must be of the DATE or DATETIME type. ```Haskell INT DAYOFMONTH(DATETIME date) ``` ```Plain Text MySQL > select dayofmonth('1987-01-31'); +--+ | dayofmonth('1987-01-31 00:00:00') | +--+ | 31 | +--+ ``` DAYOFMONTH
Project: Druid (App Definition and Development / Database)
File: datasketches-extension.md

id: datasketches-extension title: "DataSketches extension" <!-- ~ 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. --> Apache Druid aggregators based on library. Sketches are data structures implementing approximate streaming mergeable algorithms. Sketches can be ingested from the outside of Druid or built from raw data at ingestion time. Sketches can be stored in Druid segments as additive metrics. To use the datasketches aggregators, make sure you the extension in your config file: ``` druid.extensions.loadList=["druid-datasketches"] ``` The following modules are available: - approximate distinct counting with set operations (union, intersection and set difference). - extension of Theta sketch to support values associated with distinct keys (arrays of numeric values in this specialized implementation). - approximate distribution of comparable values to obtain ranks, quantiles and histograms. This is a specialized implementation for numeric values. - approximate distribution of comparable values to obtain ranks, quantiles and histograms. This is a specialized implementation for numeric values. This is a more advanced algorithm compared to the classic quantiles above, sketches are more compact for the same accuracy, or more accurate for the same size. - approximate distinct counting using very compact HLL sketch.
Project: CloudMatos (Provisioning / Security & Compliance)
File: QUICKSTART.md

Python language : Python server Create a local directory and navigate to it Clone the matos code to the local directory Setup a virtual environment: python -m venv /path/to/env Activate virtual environment: source /path/to/env/activate Setup requirements: pip install -r requirements.txt Run flask server: python -m flask run (Default Flask Part) Unittests: python -m unittest Home API: Visit http://localhost:5000/api Resources API: - http://localhost:5000/resources/gcp Documentation: Visit http://localhost:5000/apidocs Flask app file is named as matos.py
Project: KICS (Provisioning / Security & Compliance)
File: be3e170e-1572-461e-a8b6-d963def581ec.md

title: Operation Object Without 'produces' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: be3e170e-1572-461e-a8b6-d963def581ec Query name: Operation Object Without 'produces' Platform: OpenAPI Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Operation Object should have 'produces' feild defined for 'GET'operation<br> ```json title="Positive test num. 1 - json file" hl_lines="9" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "$ref": "#/definitions/User" } }, "parameters": [ { "$ref": "#/parameters/limitParam" } ] } } }, "parameters": { "limitParam": { "name": "limit", "in": "query", "description": "max records to return", "required": true, "schema": { "type": "integer" } } }, "definitions": { "User": { "type": "object", "required": [ "id", "name" ], "properties": { "id": { "type": "integer", "format": "int64" }, "name": { "type": "string" } } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="7" swagger: "2.0" info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": "$ref": "#/definitions/User" parameters: "$ref": "#/parameters/limitParam" parameters: limitParam: name: limit in: query description: max records to return required: true schema: type: integer definitions: User: type: object required: id name properties: id: type: integer format: int64 name: type: string ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "produces": [ "application/json" ], "responses": { "200": { "$ref": "#/definitions/User" } }, "parameters": [ { "$ref": "#/parameters/limitParam" } ] } } }, "parameters": { "limitParam": { "name": "limit", "in": "query", "description": "max records to return", "required": true, "schema": { "type": "integer" } } }, "definitions": { "User": { "type": "object", "required": [ "id", "name" ], "properties": { "id": { "type": "integer", "format": "int64" }, "name": { "type": "string" } } } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: "2.0" info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions produces: application/json responses: "200": "$ref": "#/definitions/User" parameters: "$ref": "#/parameters/limitParam" parameters: limitParam: name: limit in: query description: max records to return required: true schema: type: integer definitions: User: type: object required: id name properties: id: type: integer format: int64 name: type: string ```
Project: KICS (Provisioning / Security & Compliance)
File: fcb1b388-f558-4b7f-9b6e-f4e98abb7380.md

title: BOM - AWS MQ hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: fcb1b388-f558-4b7f-9b6e-f4e98abb7380 Query name: BOM - AWS MQ Platform: Terraform Severity: <span style="color:#CCCCCC">Trace</span> Category: Bill Of Materials URL: A list of MQ resources found. Amazon MQ is a managed message broker service for Apache ActiveMQ and RabbitMQ that makes it easy to set up and operate message brokers on AWS.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsmqbroker" "positive1" { broker_name = "example" configuration { id = awsmqconfiguration.test.id revision = awsmqconfiguration.test.latest_revision } engine_type = "ActiveMQ" engine_version = "5.15.9" hostinstancetype = "mq.t2.micro" securitygroups = [awssecurity_group.test.id] user { username = "ExampleUser" password = "MindTheGap" } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "awsmqbroker" "positive2" { broker_name = "example" configuration { id = awsmqconfiguration.test.id revision = awsmqconfiguration.test.latest_revision } engine_type = "RabbitMQ" engine_version = "5.15.9" hostinstancetype = "mq.t2.micro" securitygroups = [awssecurity_group.test.id] user { username = "ExampleUser" password = "111111111111" } user { username = "ExampleUser" password = "MindTheGap" } encryption_options { kmskeyid = var.encryptionoptions.kmskey_id } } ``` ```tf title="Negative test num. 1 - tf file" module "mq_broker" { source = "cloudposse/mq-broker/aws" version = "0.14.0" namespace = "eg" stage = "test" name = "mq-broker" apply_immediately = true autominorversion_upgrade = true deploymentmode = "ACTIVESTANDBYMULTIAZ" engine_type = "ActiveMQ" engine_version = "5.15.14" hostinstancetype = "mq.t3.micro" publicly_accessible = false generallogenabled = true auditlogenabled = true encryption_enabled = true useawsowned_key = true vpcid = var.vpcid subnetids = var.subnetids securitygroups = var.securitygroups } ```
Project: KICS (Provisioning / Security & Compliance)
File: ed6cf6ff-9a1f-491c-9f88-e03c0807f390.md

title: Log Retention Is Not Greater Than 90 Days hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ed6cf6ff-9a1f-491c-9f88-e03c0807f390 Query name: Log Retention Is Not Greater Than 90 Days Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: OSS Log Store should have logging enabled for longer than 90 days, for better visibility of resources and objects.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="6" resource "alicloudlogproject" "example2" { name = "tf-log" description = "created by terraform" } resource "alicloudlogstore" "example2" { project = alicloudlogproject.example.name name = "tf-log-store" shard_count = 3 auto_split = true maxsplitshard_count = 60 append_meta = true } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="9" resource "alicloudlogproject" "example4" { name = "tf-log" description = "created by terraform" } resource "alicloudlogstore" "example4" { project = alicloudlogproject.example.name name = "tf-log-store" retention_period = 60 shard_count = 3 auto_split = true maxsplitshard_count = 60 append_meta = true } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudlogproject" "example1" { name = "tf-log" description = "created by terraform" } resource "alicloudlogstore" "example1" { project = alicloudlogproject.example.name name = "tf-log-store" retention_period = 91 shard_count = 3 auto_split = true maxsplitshard_count = 60 append_meta = true } ```
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: SECURITY.md

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

displayed_sidebar: "English" Configures the properties of the specified database. :::tip This operation requires the ALTER privilege on the target database. You can follow the instructions in to grant this privilege. ::: Set database data quota in B/K/KB/M/MB/G/GB/T/TB/P/PB. ```sql ALTER DATABASE <db_name> SET DATA QUOTA <quota>; ``` Rename a database. ```sql ALTER DATABASE <dbname> RENAME <newdb_name>; ``` Set database replica quota. ```sql ALTER DATABASE <db_name> SET REPLICA QUOTA <quota>; ``` Note: ```plain text After renaming the database, use REVOKE and GRANT commands to modify the corresponding user permission if necessary. The database's default data quota and the default replica quota are 2^63-1. ``` Set data quota for a database. ```SQL ALTER DATABASE example_db SET DATA QUOTA 10995116277760B; -- The above unit is bytes, equivalent to the following statement. ALTER DATABASE example_db SET DATA QUOTA 10T; ALTER DATABASE example_db SET DATA QUOTA 100G; ALTER DATABASE example_db SET DATA QUOTA 200M; ``` Rename the database `exampledb` as `exampledb2`. ```SQL ALTER DATABASE exampledb RENAME exampledb2; ``` Set database replica quota. ```SQL ALTER DATABASE example_db SET REPLICA QUOTA 102400; ```
Project: StarRocks (App Definition and Development / Database)
File: table_privileges.md

displayed_sidebar: "English" `table_privileges` provides information about table privileges. The following fields are provided in `table_privileges`: | Field | Description | | -- | | | GRANTEE | The name of the user to which the privilege is granted. | | TABLE_CATALOG | The name of the catalog to which the table belongs. This value is always `def`. | | TABLE_SCHEMA | The name of the database to which the table belongs. | | TABLE_NAME | The name of the table. | | PRIVILEGE_TYPE | The privilege granted. The value can be any privilege that can be granted at the table level. | | ISGRANTABLE | `YES` if the user has the `GRANT OPTION` privilege, `NO` otherwise. The output does not list `GRANT OPTION` as a separate row with `PRIVILEGETYPE='GRANT OPTION'`. |