cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_kubeblocks_status.md

title: kbcli kubeblocks status Show list of resource KubeBlocks uses or owns. ``` kbcli kubeblocks status [flags] ``` ``` kbcli kubeblocks status kbcli kubeblocks status --all ``` ``` -A, --all Show all resources, including configurations, storages, etc -h, --help help for status ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - KubeBlocks operation commands.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.32.md

layout: release date: 2022-12-05 tag: v0.6.32 language: en Always redirect to remote provide for playground deployments @Revolyssup (#6633) Improve error message for mesheryctl mesh @PratikforCoding (#6625) Krishna2323/issue/Icons-To_SVG @Krishna2323 (#6630) [Extensions] Meshery logo update for extensions @Chadha93 (#6635) [UI] Make catalog toggling as a user preference @Chadha93 (#6450) [CD] Transition playground deployment VM-based to K8s-based @leecalcote (#6622) Thank you to our contributors for making this release possible: @Chadha93, @Krishna2323, @PratikforCoding, @Revolyssup, @leecalcote and @theBeginner86
Project: ClickHouse (App Definition and Development / Database)
File: role-grants.md

slug: /en/operations/system-tables/role-grants Contains the role grants for users and roles. To add entries to this table, use `GRANT role TO user`. Columns: `user_name` (()) User name. `role_name` (()) Role name. `grantedrolename` () Name of role granted to the `role_name` role. To grant one role to another one use `GRANT role1 TO role2`. `grantedroleisdefault` () Flag that shows whether `grantedrole` is a default role. Possible values: 1 `granted_role` is a default role. 0 `granted_role` is not a default role. `withadminoption` () Flag that shows whether `granted_role` is a role with privilege. Possible values: 1 The role has `ADMIN OPTION` privilege. 0 The role without `ADMIN OPTION` privilege.
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_create_tablespace.md

title: CREATE TABLESPACE [YSQL] headerTitle: CREATE TABLESPACE linkTitle: CREATE TABLESPACE description: Use the CREATE TABLESPACE statement to create a tablespace in the cluster. menu: preview: identifier: ddlcreatetablespace parent: statements type: docs Use the `CREATE TABLESPACE` statement to create a tablespace in the cluster. It defines the tablespace name and tablespace properties. {{%ebnf%}} create_tablespace {{%/ebnf%}} Create a tablespace with tablespace_name. If `qualified_name` already exists in the cluster, an error will be raised. YSQL tablespaces allow administrators to specify the number of replicas for a table or index, and how they can be distributed across a set of clouds, regions, and zones in a geo-distributed deployment. Can be one of [`replica_placement`]. Use `replica_placement` to specify the number of replicas stored in specific zones, regions, or clouds. See and for full guides.
Project: KICS (Provisioning / Security & Compliance)
File: 376c9390-7e9e-4cb8-a067-fd31c05451fd.md

title: Header JSON Reference Does Not Exists hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 376c9390-7e9e-4cb8-a067-fd31c05451fd Query name: Header JSON Reference Does Not Exists Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Structure and Semantics URL: Header reference should exists on components field<br> ```json title="Positive test num. 1 - json file" hl_lines="25" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "success", "content": { "application/json": { "schema": { "type": "array", "items": { "$ref": "#/components/schemas/MyObject" } }, "headers": { "X-Pages": { "$ref": "#/components/headers/wPages" } } } } } } } } }, "components": { "schemas": { "MyObject": { "type": "object", "properties": { "id": { "type": "string" }, "name": { "type": "string" } } } }, "headers": { "xPages": { "schema": { "type": "integer", "description": "number of pages" } } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="21" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': description: success content: application/json: schema: type: array items: "$ref": "#/components/schemas/MyObject" headers: X-Pages: "$ref": "#/components/headers/wPages" components: schemas: MyObject: type: object properties: id: type: string name: type: string headers: xPages: schema: type: integer description: number of pages ``` ```json title="Negative test num. 1 - json file" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "success", "content": { "application/json": { "schema": { "type": "array", "items": { "$ref": "#/components/schemas/MyObject" } }, "headers": { "X-Pages": { "$ref": "#/components/headers/xPages" } } } } } } } } }, "components": { "schemas": { "MyObject": { "type": "object", "properties": { "id": { "type": "string" }, "name": { "type": "string" } } } }, "headers": { "xPages": { "schema": { "type": "integer", "description": "number of pages" } } } } } ``` ```yaml title="Negative test num. 2 - yaml file" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': description: success content: application/json: schema: type: array items: "$ref": "#/components/schemas/MyObject" headers: X-Pages: "$ref": "#/components/headers/xPages" components: schemas: MyObject: type: object properties: id: type: string name: type: string headers: xPages: schema: type: integer description: number of pages ```
Project: Druid (App Definition and Development / Database)
File: test-stats.md

id: test-stats title: "Test Stats Aggregators" <!-- ~ 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 Apache Druid extension incorporates test statistics related aggregators, including z-score and p-value. Please refer to for math background and details. Make sure to include `druid-stats` extension in order to use these aggregators. Please refer to and for more details. z = (p1- p2) / S.E. (assuming null hypothesis is true) Please see below for p1 and p2. Please note S.E. stands for standard error where S.E. = sqrt{ p1 ( 1 - p1 )/n1 + p2 (1 - p2)/n2) } (p1 p2) is the observed difference between two sample proportions. `zscore2sample`: calculate the z-score using two-sample z-test while converting binary variables (e.g. success or not) to continuous variables (e.g.* conversion rate). ```json { "type": "zscore2sample", "name": "<output_name>", "successCount1": <post_aggregator> success count of sample 1, "sample1Size": <post_aggregaror> sample 1 size, "successCount2": <post_aggregator> success count of sample 2, "sample2Size" : <post_aggregator> sample 2 size } ``` Please note the post aggregator will be converting binary variables to continuous variables for two population proportions. Specifically p1 = (successCount1) / (sample size 1) p2 = (successCount2) / (sample size 2) `pvalue2tailedZtest`*: calculate p-value of two-sided z-test from zscore *pvalue2tailedZtest(zscore)* - the input is a z-score which can be calculated using the zscore2sample post aggregator ```json { "type": "pvalue2tailedZtest", "name": "<output_name>", "zScore": <zscore post_aggregator> } ``` In this example, we use zscore2sample post aggregator to calculate z-score, and then feed the z-score to pvalue2tailedZtest post aggregator to calculate p-value. A JSON query example can be as follows: ```json { ... "postAggregations" : { "type" : "pvalue2tailedZtest", "name" : "pvalue", "zScore" : { "type" : "zscore2sample", "name" : "zscore", "successCount1" : { "type" : "constant", "name" : "successCountFromPopulation1Sample", "value" : 300 }, "sample1Size" : { "type" : "constant", "name" : "sampleSizeOfPopulation1", "value" : 500 }, "successCount2": { "type" : "constant", "name" : "successCountFromPopulation2Sample", "value" : 450 }, "sample2Size" : { "type" : "constant", "name" : "sampleSizeOfPopulation2", "value" : 600 } } } } ```
Project: Glasskube (App Definition and Development / Application Definition & Image Build)
File: 01_helm.md

slug: helm sidebar_label: With Helm title: Glasskube vs Helm Comparison description: Discover Glasskube, a fresh Kubernetes package manager challenging Helm's shortcomings. Explore automatic updates, dependency management and much more. In late 2023, we published a about, what we thought, were the biggest shortcomings of undoubtedly the most popular package manager for Kubernetes. After receiving TONS of feedback from the community we realized that we were not alone in being unsatisfied with the status quo. That is why we started thinking about and prototyping Glasskubea new vision of what a package manager for Kubernetes could look like. We take a new approach on multiple features, but want to highlight the 5 most important differences that got either just released, are in development right now or are on our roadmap and will be started soon: Package updates<br/>Glasskube provides the possibility to install packages in `@latest` version which leads to automatic updates or install a package in specific version and explore new versions via the `outdated` command and upgrade them with the `upgrade` command. Dependency management<br/>Glasskube offersas you would expectdependency management out of the box. Multiple packages can require a specific package (e.g. `cert-manager`) being installed and updated in the Kubernetes cluster and its preferred namespace. Custom Resources Definition (CRD) changes<br/>Upgrading CRDs will be taken care of by Glasskube to ensure CRs and its operators don't get out-of-sync. Cloud-Native architecture<br/>As Helm's architecture is purely client side, it renders the templates and applies them via the Kubernetes API. Although releases are stored in Kubernetes Secrets there is no first party server-side component for helm making it harder to install packages via the GitOps approach. Kubernetes version upgrade compatibility<br/>Glasskube tries to make Kubernetes version upgrades as smooth as possible by automatically testing all package (combinations) across multiple Kubernetes versions. We acknowledge that Helm, with its flexibility and extensibility, has its place in a seasoned DevOps engineer's tool belt, and it's status as one of the most popular methods to deploy applications in Kubernetes is not without merit. However, Helm's extensive flexibility comes, at least in part, at the cost of the user, which is especially true for junior and novice Kubernetes administrators. That is why Glasskube is laser focused on delivering a tool for administrators who need to only manage a couple of applications, but who also need to make sure that a multitude of infrastructure components are kept up-to-date and secure throughout multiple Kubernetes version upgrades while also adapting to inevitable breaking changes. With that being said, Glasskube is not a full replacement of Helm, neither do we aspire for it to become one in the future. Rather, Glasskube is designed to integrate with established workflows and work in synergy with existing tools, such as Helm, Flux, ArgoCD and many more.
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: changelog.md

title: Changelog weight: 25 The Operator SDK project tracks changes across releases by maintaining a live changelog. This changelog is compiled via fragments located in `changelog/fragments` Contributors are asked to add these changelog fragments when creating pull requests by following this . The changlog fragments document the following information: Description of Changes Types of Changes One of: addition, change, deprecation, removal, bugfix Migration Guide for Changes These are required for breaking changes, and essential (but not required) for scaffolding-related changes.
Project: YugabyteDB (App Definition and Development / Database)
File: managed-cli-role.md

title: ybm CLI role resource headerTitle: ybm role linkTitle: role description: YugabyteDB Managed CLI reference Role resource. headcontent: Manage roles menu: preview_yugabyte-cloud: identifier: managed-cli-role parent: managed-cli-reference weight: 20 type: docs Use the `role` resource to create and manage YugabyteDB Managed account . ```text Usage: ybm role [command] [flags] ``` List roles in YugabyteDB Managed: ```sh ybm role list ``` Describe the Admin role: ```sh ybm role describe --role-name admin ``` You can use this command to view all the available permissions. Create a role: ```sh ybm role create --role-name backuprole \ --permissions resource-type=BACKUP,operation-group=CREATE \ --permissions resource-type=BACKUP,operation-group=DELETE ``` Create a custom role. | Flag | Description | | : | : | | --role-name | Required. Name for the role. | | &#8209;&#8209;permissions | Required. Permissions for the role, provided as key value pairs. Permissions are made up of a resource type and an operation group.<br>Arguments:<ul><li>resource-type - the resource to which the permission applies</li><li>operation-group - the operation that the permission allows on the resource</li></ul>Both resource-type and operation-group are mandatory. Specify multiple permissions by using multiple --permissions arguments. Use `ybm permission list` to view a list of all permissions. | | --description | Description for the role. | Delete a specified custom role. | Flag | Description | | : | : | | --role-name | Required. Name of the role. | Fetch detailed information about a specified role, including its permissions (name, description, resource type, and operation group), and users and API keys that are assigned to the role. | Flag | Description | | : | : | | --role-name | Required. Name of the role. | List the roles in your YugabyteDB Managed account. | Flag | Description | | : | : | | --role-name | Name of a role. | | --type | Type of role. BUILT-IN or CUSTOM. | Update the specified custom role. | Flag | Description | | : | : | | --role-name | Required. Name of the role. | | &#8209;&#8209;permissions | Required. Permissions for the role, provided as key value pairs. Permissions are made up of a resource type and an operation group.<br>Arguments:<ul><li>resource-type - the resource to which the permission applies</li><li>operation-group - the operation that the permission allows on the resource</li></ul>Both resource-type and operation-group are mandatory. Specify multiple permissions by using multiple --permissions arguments. Use `ybm permission list` to view a list of all permissions. | | --description | Description for the role. | | --new-name | New name for the updated role. |
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: compose_pause.md

<!MARKERGENSTART--> Pause services | Name | Type | Default | Description | |:|:--|:--|:--| | `--dry-run` | | | Execute command in dry run mode | <!MARKERGENEND--> Pauses running containers of a service. They can be unpaused with `docker compose unpause`.
Project: YugabyteDB (App Definition and Development / Database)
File: do-populate-results.md

title: dopopulateresults.sql linkTitle: dopopulateresults.sql headerTitle: dopopulateresults.sql description: dopopulateresults.sql - Part of the code kit for the "Analyzing a normal distribution" section within the YSQL window functions documentation. menu: v2.18: identifier: do-populate-results parent: analyzing-a-normal-distribution weight: 140 type: docs Save this script as `dopopulateresults.sql`. ```plpgsql do $body$ declare nof_buckets constant int not null := 20; begin delete from results; call dontile (nofbuckets); call dopercentrank (nof_buckets); call documedist (nof_buckets); end; $body$; ```
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: compose_kill.md

<!MARKERGENSTART--> Force stop service containers | Name | Type | Default | Description | |:-|:|:-|:| | `--dry-run` | | | Execute command in dry run mode | | `--remove-orphans` | | | Remove containers for services not defined in the Compose file | | `-s`, `--signal` | `string` | `SIGKILL` | SIGNAL to send to the container | <!MARKERGENEND--> Forces running containers to stop by sending a `SIGKILL` signal. Optionally the signal can be passed, for example: ```console $ docker-compose kill -s SIGINT ```
Project: KICS (Provisioning / Security & Compliance)
File: e36d8880-3f78-4546-b9a1-12f0745ca0d5.md

title: NPM Install Command Without Pinned Version hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e36d8880-3f78-4546-b9a1-12f0745ca0d5 Query name: NPM Install Command Without Pinned Version Platform: Dockerfile Severity: <span style="color:#ff7213">Medium</span> Category: Supply-Chain URL: Check if packages installed by npm are pinning a specific version.<br> ```dockerfile title="Positive test num. 1 - dockerfile file" hl_lines="2 3 4 5 6 7 8" FROM node:12 RUN npm install sax RUN npm install sax --no-cache RUN npm install sax | grep fail && npm install sax@latest RUN npm install sax@latest | grep fail && npm install sax RUN npm install sax | grep fail && npm install sax RUN npm i -g @angular/cli RUN ["npm","add","sax"] ``` ```dockerfile title="Negative test num. 1 - dockerfile file" FROM node:12 RUN npm install RUN npm install sax@latest RUN npm install sax@0.1.1 RUN npm install sax@0.1.1 | grep fail && npm install sax@latest RUN npm install git://github.com/npm/cli.git RUN npm install git+ssh://git@github.com:npm/cli#semver:^5.0 RUN npm install --production --no-cache RUN npm config set registry <internalnpmregistry> && \ npm install && \ npx vite build --mode $VITE_MODE ```
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.7.1.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Safemode default threshold should be 0.999 | Major | . | Konstantin Shvachko | Konstantin Shvachko | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | NullPointerException in JobTracker's ExireTaskTracker thread | Critical | . | Owen O'Malley | Owen O'Malley | | | NullPointerException in toString for RPC connection objects | Minor | . | Owen O'Malley | Owen O'Malley | | | rpc timeout in Task.done kills task | Major | . | Owen O'Malley | Owen O'Malley | | | transmission errors to the reduce will cause map output to be considered lost | Major | . | Owen O'Malley | Owen O'Malley |
Project: ArangoDB (App Definition and Development / Database)
File: outcome_throw_as_system_error_with_payload_boost_error_code.md

+++ title = "`void outcomethrowassystemerrorwithpayload(const boost::system::error_code &)`" description = "Specialisation of `outcomethrowassystemerrorwithpayload()` for `boost::system::error_code`." +++ A specialisation of `outcomethrowassystemerrorwithpayload()` for `boost::system::errorcode`. This executes {{% api "BOOSTOUTCOMETHROWEXCEPTION(expr)" %}} with a `boost::system::system_error` constructed from the input. Overridable: Argument dependent lookup. Requires: Nothing. Namespace: `boost::system` Header: `<boost/outcome/boost_result.hpp>`
Project: StarRocks (App Definition and Development / Database)
File: DROP_TASK.md

displayed_sidebar: "English" Drops an asynchronous ETL task submitted using . This feature has been supported since StarRocks v2.5.7. NOTE Dropping a task with DROP TASK simultaneously cancels the corresponding TaskRun. ```SQL DROP TASK `<task_name>` ``` | Parameter | Description | | - | -- | | task_name | The name of the task to drop. Please wrap the task name with backticks (`) to prevent any parse failure. | You can check the information of asynchronous tasks by querying the metadata views `tasks` and `task_runs` in Information Schema. ```SQL SELECT * FROM INFORMATION_SCHEMA.tasks; SELECT * FROM informationschema.tasks WHERE taskname = '<task_name>'; SELECT * FROM informationschema.taskruns; SELECT * FROM informationschema.taskruns WHERE taskname = '<taskname>'; ``` ```Plain MySQL > SUBMIT /+set_var(query_timeout=100000)/ TASK `ctas` AS -> CREATE TABLE insertwikiedit_new -> AS SELECT * FROM sourcewikiedit; +-+--+ | TaskName | Status | +-+--+ | ctas | SUBMITTED | +-+--+ 1 row in set (1.19 sec) MySQL > DROP TASK `ctas`; Query OK, 0 rows affected (0.35 sec) ```