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

+++ title = "`basic_result(ErrorCondEnum &&)`" description = "Implicit `errortype` from `ErrorCondEnum` constructor. Available if `predicate::enableerrorconditionconverting_constructor<ErrorCondEnum>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "implicit-constructors", "converting-constructors"] weight = 200 +++ Implicit `errortype` from `ErrorCondEnum` constructor. Calls {{% api "void onresult_construction(T *, U &&) noexcept" %}} with `this` and `ErrorCondEnum`. Requires: `predicate::enableerrorconditionconvertingconstructor<R>` is true. Complexity: Same as for `errortype`'s copy or move constructor from the result of `makeerror_code(ErrorCondEnum)`. Constexpr, triviality and noexcept of underlying operations is propagated. Guarantees: If an exception is thrown during the operation, the state of the input is left indeterminate.
Project: YugabyteDB (App Definition and Development / Database)
File: AUTHORS.md

PostgreSQL Anonymizer Development Team =============================================================================== This is an open project. Feel free to join us and improve this tool. To find out how you can get involved, please read [CONTRIBUTING.md]. Maintainer This software is mainly developed and maintained by Damien Clochard with the help of many contributors. Contributors Mark Shay: Support in Google Cloud SQL Jitesh Srivastava: Documentation GPGIT2 : Feedback, Testing and Ideas Udo Leiteritz : fix for pgdumpanon Luis Gonzalez-Silen : Documentation Julien Rouhaud : Technical Discussions Olle Jonsson : Documentation Manuel Eveno : Feedback Michel Pelletier : Consistent backups Gerg Rubint : Documentation Mahesh Moturu : Documentation Greg pringle : Bug Report Radek Sala : Bug report Cristian Gomez Portes: Bug report Mike Tefft: Feature request Hrvoje Pavlinovic : Bug fix Be Hai Tran : How-To Florent Jardin : How-To Yann B. (@ybycode) : fix for pgdumpanon Christophe Courtois (@Krysztophe) : Documentation Vito Botta (@vitobotta) : Documentation Cristiano (@stresser) : Documentation Adrien S. (@adriens) : Documentation Justin Wei : Documentation Frdric Yhuel (@yhuelf) : code review and refactoring Jakob Serlier : documentation Alice Armand (@alice_) : Proofreading Carlos Medeiros (@cadubsb) : Bug Fix Devrim Gndz (@devrimgunduz) : RPM Packages Rushal Verma (@rusrushal13) : documentation Paul Bonaud (@paulrbr) : support for foreign tables Dmitry Fomin (@fomin.list) : Bug fix Sbastien Helbert (@sebastien-helbert) : Code refactoring Rodrigo Otsuka (@rodrigo.otsuka) : Bug reports Nicolas Peltier (@npeltier) : Bug reports Matthieu Larcher (@somatt) : Bug reports Nikolay Samokhvalov (@NikolayS) : Bug fix + Documentation Gunnar "Nick" Bluth (@nickbluth) : Some additional functions Yann ROBIN (@me.show) : version() function and DBAAS install Ilya Gorbunov (@dAverk) : Bug fixes Peter Neave (@peterneave) : Typos Yann Robin (@me.show) : version() function and DBAAS install Christophe Courtois (@Krysztophe) : Proofreading Pierre-Henri Dubois Amy (@theodor_lobster) : Proofreading, GIS Thomas Clark (@cthomaspdx) : Pseudonymization Joe Auty (@joeauty) : Issue #114 Bernie Caessens (@bcaessens) : Feedback on the black box method Sam Buckingham (@sam.buckingham) : Feedback on the black box method Sebastien Delobel (@sdelobel) : Typos Travis Miller (@travismiller) : MacOS support Jan Birk (@jabi27) : Install on Ubuntu Olleg Samoylov (@Splarv) : Issue #87, Bug fixes, Documentation Damien Cazeils (www.damiencazeils.com) : Logo Ioseph Kim (@i0seph) : Documentation Matiss Zarkevics (@leovingi) : Tests on Amazon RDS Peter Goodwin (@Postgressor) : Tests Tim (@roconda) : Documentation Micha Lipka (@michallipka) : Tests and typos Thibaut Madeleine (@madtibo) : original idea :-)
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.Events.md

/ / Events .Events SnapshotRequestEvent: `Object` | Name | Type | Description | | :- | :- | :- | | `execUUID?` | `string` | Capture just one block? | | `cb?` | (`snapshot`: `Buffer`) => `void` | - | StatusStripeChangeEvent: `Object` | Name | Type | | : | :-- | | `message?` | `string` | | `type` | `"default"` \| `"blue"` \| `"yellow"` \| `"red"` | TabLayoutChangeEvent: `Object` | Name | Type | | :-- | :-- | | `isSidecarNowHidden` | `boolean` | | `isWidthConstrained?` | `boolean` | eventBus: `EventBus` eventChannelUnsafe: `EventEmitter` unwireToStandardEvents(`listener`): `void` Unhook | Name | Type | | : | : | | `listener` | (`tab?`: `number` \| ) => `void` | `void` unwireToTabEvents(`listener`): `void` Unhook | Name | Type | | : | : | | `listener` | (`tab?`: `number` \| ) => `void` | `void` wireToStandardEvents(`listener`): `void` Hook an event listener up to the family of standard user interaction events. | Name | Type | | : | : | | `listener` | (`tab?`: `number` \| ) => `void` | `void` wireToTabEvents(`listener`): `void` Hook an event listener up to tab events. | Name | Type | | : | : | | `listener` | (`tab?`: `number` \| ) => `void` | `void`
Project: KICS (Provisioning / Security & Compliance)
File: 656880aa-1388-488f-a6d4-8f73c23149b2.md

title: RDS Database Cluster not Encrypted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 656880aa-1388-488f-a6d4-8f73c23149b2 Query name: RDS Database Cluster not Encrypted Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: RDS Database Cluster Encryption should be enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsdbcluster_snapshot" "positive1" { dbclusteridentifier = awsrdscluster.example2.id dbclustersnapshot_identifier = "resourcetestsnapshot1234" } resource "awsrdscluster" "example2" { cluster_identifier = "example" dbsubnetgroupname = awsdbsubnetgroup.example.name engine_mode = "multimaster" master_password = "barbarbarbar" master_username = "foo" skipfinalsnapshot = true } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "awsdbcluster_snapshot" "positive2" { dbclusteridentifier = awsrdscluster.example3.id dbclustersnapshot_identifier = "resourcetestsnapshot1234" } resource "awsrdscluster" "example3" { cluster_identifier = "example" dbsubnetgroupname = awsdbsubnetgroup.example.name engine_mode = "multimaster" master_password = "barbarbarbar" master_username = "foo" skipfinalsnapshot = true storage_encrypted = false } ``` ```tf title="Negative test num. 1 - tf file" resource "awsdbcluster_snapshot" "negative" { dbclusteridentifier = awsrdscluster.example.id dbclustersnapshot_identifier = "resourcetestsnapshot1234" } resource "awsrdscluster" "example" { cluster_identifier = "example" dbsubnetgroupname = awsdbsubnetgroup.example.name engine_mode = "multimaster" master_password = "barbarbarbar" master_username = "foo" skipfinalsnapshot = true storage_encrypted = true } ```
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: BUILDING.md

Windows: * make macOS: * make Linux: * make Once you have the prerequisites installed, you can build the CLI using: ```console make ``` This will output a `docker-compose` CLI plugin for your host machine in `./bin/build`. You can statically cross compile the CLI for Windows, macOS, and Linux using the `cross` target. To run all of the unit tests, run: ```console make test ``` If you need to update a golden file simply do `go test ./... -test.update-golden`. To run e2e tests, the Compose CLI binary needs to be built. All the commands to run e2e tests propose a version with the prefix `build-and-e2e` to first build the CLI before executing tests. Note that this requires a local Docker Engine to be running. To execute both CLI and standalone e2e tests, run : ```console make e2e ``` Or if you need to build the CLI, run: ```console make build-and-e2e ``` To execute CLI plugin e2e tests, run : ```console make e2e-compose ``` Or if you need to build the CLI, run: ```console make build-and-e2e-compose ``` To execute the standalone CLI e2e tests, run : ```console make e2e-compose-standalone ``` Or if you need to build the CLI, run: ```console make build-and-e2e-compose-standalone ``` To create a new release: Check that the CI is green on the main branch for the commit you want to release Run the release Github Actions workflow with a tag of form vx.y.z following existing tags. This will automatically create a new tag, release and make binaries for Windows, macOS, and Linux available for download on the .
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.18.md

layout: release date: 2022-10-22 tag: v0.6.18 language: en Updated protobuf build in Makefile @abdullah1308 (#6402) Fix skipped operator uninstall from mesheryctl on failed meshery unin @Revolyssup (#6425) Fix context search in modal @MUzairS15 (#6427) [bug] Fix UI crash due to K8s context search in modal @theBeginner86 (#6423) [RJSF] Migration v3-v5, Validation Error Fixes @Abhishek-kumar09 (#6379) Changed size and Removed Extra SVG @Harshit-Dandriyal (#6375) [UI] Removal of unused variables with comments @dipankardas011 (#6422) [bug] Fix UI crash due to K8s context search in modal @theBeginner86 (#6423) Specific Version Update @DantrazTrev (#6428) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @DantrazTrev, @Harshit-Dandriyal, @MUzairS15, @Revolyssup, @abdullah1308, @dipankardas011, @gr455, @harkiratsm, @l5io, @leecalcote, @theBeginner86 and l5io
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: pid.container.md

Set the PID namespace mode for the container. The default is to create a private PID namespace for the container. container:id: join another container's PID namespace; host: use the host's PID namespace for the container. Note the host mode gives the container full access to local PID and is therefore considered insecure; ns:path: join the specified PID namespace; private: create a new namespace for the container (default).
Project: YugabyteDB (App Definition and Development / Database)
File: managed-cli-read-replica.md

title: ybm CLI cluster read-replica resource headerTitle: ybm cluster read-replica linkTitle: cluster read-replica description: YugabyteDB Managed CLI reference Cluster Read Replica resource. headcontent: Manage cluster read replicas menu: preview_yugabyte-cloud: identifier: managed-cli-read-replica parent: managed-cli-reference weight: 20 type: docs Use the `cluster read-replica` resource to perform operations on a YugabyteDB Managed cluster , including the following: create, update, and delete read replicas get information about read replicas ```text Usage: ybm cluster read-replica [command] [flags] ``` Create a read-replica cluster: ```sh ybm cluster read-replica create \ --replica num-cores=2,\ memory-mb=4096,\ disk-size-gb=200,\ cloud-provider=AWS,\ region=us-west-3,\ num-nodes=3,\ vpc=my-vpc,\ num-replicas=2,\ multi-zone=true ``` Create a read replica for a specified cluster. | Flag | Description | | : | : | | --cluster-name | Required. Name of the cluster to which you want to add read replicas. | | --replica | Specifications for the read replica provided as key-value pairs.<br>Arguments:<br><ul><li>num-cores - number of vCPUs per node. Default is 2.</li><li>memory-mb - memory (MB) per node. Default is 4096.</li><li>disk-size-gb - disk size (GB) per node. Default is 10.</li><li>cloud-provider - cloud provider (`AWS` or `GCP`)</li><li>region - region in which to deploy the read replica</li><li>num-nodes - number of nodes for the read replica. Default is 1.</li><li>vpc-name - name of the VPC in which to deploy the read replica</li><li>num-replicas - the replication factor</li><li>multi-zone - whether the read replica is multi-zone (`true` or `false`). Default is false.</li></ul> Delete read replicas of a specified cluster. | Flag | Description | | : | : | | --cluster-name | Required. Name of the cluster whose read replicas you want to delete. | List the read replicas of a specified cluster. | Flag | Description | | : | : | | --cluster-name | Required. Name of the cluster whose read replicas you want to fetch. | Update a read replica for a specified cluster. | Flag | Description | | : | : | | --cluster-name | Required. Name of the cluster with read replicas you want to update. | | --replica | Specifications for the read replica provided as key-value pairs.<br>Arguments:<br><ul><li>num-cores - number of vCPUs per node. Default is 2.</li><li>memory-mb - memory (MB) per node. Default is 4096.</li><li>disk-size-gb - disk size (GB) per node. Default is 10.</li><li>cloud-provider - cloud provider (`AWS` or `GCP`)</li><li>region - region in which to deploy the read replica</li><li>num-nodes - number of nodes for the read replica. Default is 1.</li><li>vpc-name - name of the VPC in which to deploy the read replica</li><li>num-replicas - the replication factor</li><li>multi-zone - whether the read replica is multi-zone (`true` or `false`). Default is false.</li></ul>
Project: KICS (Provisioning / Security & Compliance)
File: 83103dff-d57f-42a8-bd81-40abab64c1a7.md

title: BigQuery Dataset Is Public hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 83103dff-d57f-42a8-bd81-40abab64c1a7 Query name: BigQuery Dataset Is Public Platform: GoogleDeploymentManager Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: BigQuery dataset is anonymously or publicly accessible. Attribute access.specialGroup should not contain 'allAuthenticatedUsers'<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" resources: name: bigquery type: bigquery.v2.dataset properties: access: role: owner specialGroup: allAuthenticatedUsers role: owner specialGroup: my-group ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: bigquery type: bigquery.v2.dataset properties: access: role: owner specialGroup: my-group ``` ```yaml title="Negative test num. 2 - yaml file" resources: name: bigquery type: bigquery.v2.dataset properties: description: my-bigquery ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-image-tree.1.md

% podman-image-tree 1 podman\-image\-tree - Print layer hierarchy of an image in a tree format podman image tree [options] image:tag|image-id Prints layer hierarchy of an image in a tree format. If no tag is provided, Podman defaults to `latest` for the image. Layers are indicated with image tags as `Top Layer of`, when the tag is known locally. Print usage statement Show all child images and layers of the specified image List image tree information on specified image: ``` $ podman image tree docker.io/library/wordpress Image ID: 6e880d17852f Tags: [docker.io/library/wordpress:latest] Size: 429.9MB Image Layers ID: 3c816b4ead84 Size: 58.47MB ID: e39dad2af72e Size: 3.584kB ID: b2d6a702383c Size: 213.6MB ID: 94609408badd Size: 3.584kB ID: f4dddbf86725 Size: 43.04MB ID: 8f695df43a4c Size: 11.78kB ID: c29d67bf8461 Size: 9.728kB ID: 23f4315918f8 Size: 7.68kB ID: d082f93a18b3 Size: 13.51MB ID: 7ea8bedcac69 Size: 4.096kB ID: dc3bbf7b3dc0 Size: 57.53MB ID: fdbbc6404531 Size: 11.78kB ID: 8d24785437c6 Size: 4.608kB ID: 80715f9e8880 Size: 4.608kB Top Layer of: [docker.io/library/php:7.2-apache] ID: c93cbcd6437e Size: 3.573MB ID: dece674f3cd1 Size: 4.608kB ID: 834f4497afda Size: 7.168kB ID: bfe2ce1263f8 Size: 40.06MB ID: 748e99b214cf Size: 11.78kB Top Layer of: [docker.io/library/wordpress:latest] ``` Show all child images and layers of the specified image: ``` $ podman image tree ae96a4ad4f3f --whatrequires Image ID: ae96a4ad4f3f Tags: [docker.io/library/ruby:latest] Size: 894.2MB Image Layers ID: 9c92106221c7 Size: 2.56kB Top Layer of: [docker.io/library/ruby:latest] ID: 1b90f2b80ba0 Size: 3.584kB ID: 42b7d43ae61c Size: 169.5MB ID: 26dc8ba99ec3 Size: 2.048kB ID: b4f822db8d95 Size: 3.957MB ID: 044e9616ef8a Size: 164.7MB ID: bf94b940200d Size: 11.75MB ID: 4938e71bfb3b Size: 8.532MB ID: f513034bf553 Size: 1.141MB ID: 1e55901c3ea9 Size: 3.584kB ID: b62835a63f51 Size: 169.5MB ID: 9f4e8857f3fd Size: 2.048kB ID: c3b392020e8f Size: 3.957MB ID: 880163026a0a Size: 164.8MB ID: 8c78b2b14643 Size: 11.75MB ID: 830370cfa182 Size: 8.532MB ID: 567fd7b7bd38 Size: 1.141MB Top Layer of: [docker.io/circleci/ruby:latest] ``` Feb 2019, Originally compiled by Kunal Kushwaha `<kushwahakunalv7@lab.ntt.co.jp>`
Project: Beam (App Definition and Development / Streaming & Messaging)
File: lumaapps.md

title: "Luma Apps" icon: /images/logos/powered-by/lumaapps.png hasLink: "https://www.lumapps.com/" <!-- Licensed 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. -->
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: root-config.md

id: root-config title: Root Config Service sidebar_label: Root Config description: Documentation for the Root Config service This service allows you to read configuration values out of your `app-config` YAML files. The following example shows how you can use the default config service to be able to get a config value, and then log it to the console. ```ts import { coreServices, createBackendPlugin, } from '@backstage/backend-plugin-api'; createBackendPlugin({ pluginId: 'example', register(env) { env.registerInit({ deps: { log: coreServices.logger, config: coreServices.rootConfig, }, async init({ log, config }) { const baseUrl = config.getString('backend.baseUrl'); log.warn(`The backend is running at ${baseUrl}`); }, }); }, }); ``` There's additional configuration that you can optionally pass to setup the `config` core service. `argv` - Override the arguments that are passed to the config loader, instead of using `process.argv` `remote` - Configure remote configuration loading You can configure these additional options by adding an override for the core service when calling `createBackend` like follows: ```ts import { rootConfigServiceFactory } from '@backstage/backend-app-api'; const backend = createBackend(); backend.add( rootConfigServiceFactory({ argv: [ '--config', '/backstage/app-config.development.yaml', '--config', '/backstage/app-config.yaml', ], remote: { reloadIntervalSeconds: 60 }, }), ); ```
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-logout.md

layout: default title: mesheryctl-system-logout permalink: reference/mesheryctl/system/logout redirect_from: reference/mesheryctl/system/logout/ type: reference display-title: "false" language: en command: system subcommand: logout Remove authentication for Meshery Server Remove authentication for Meshery Server This command removes the authentication token from the user's filesystem <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system logout [flags] </div> </pre> Logout current session with your Meshery Provider. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system logout </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for logout </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -c, --context string (optional) temporarily change the current context. -v, --verbose verbose output -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: StarRocks (App Definition and Development / Database)
File: SHOW_RUNNING_QUERIES.md

displayed_sidebar: "English" Shows the information of all queries that are running or pending in the query queue. This feature is supported from v3.1.4 onwards. :::tip This operation does not require privileges. ::: ```SQL SHOW RUNNING QUERIES ``` `QueryId`: The ID of the query. `ResourceGroupId`: The ID of the resource group that the query hit. When there is no hit on a user-defined resource group, it will be displayed as "-". `StartTime`: The start time of the query. `PendingTimeout`: The time when the PENDING query will time out in the queue. `QueryTimeout`: The time when the query times out. `State`: The queue state of the query, where "PENDING" indicates it is in the queue, and "RUNNING" indicates it is currently executing. `Slots`: The logical resource quantity requested by the query, currently fixed at `1`. `Frontend`: The FE node that initiated the query. `FeStartTime`: The start time of the FE node that initiated the query. ```Plain MySQL [(none)]> SHOW RUNNING QUERIES; +--+--++++--+-+++ | QueryId | ResourceGroupId | StartTime | PendingTimeout | QueryTimeout | State | Slots | Frontend | FeStartTime | +--+--++++--+-+++ | a46f68c6-3b49-11ee-8b43-00163e10863a | - | 2023-08-15 16:56:37 | 2023-08-15 17:01:37 | 2023-08-15 17:01:37 | RUNNING | 1 | 127.00.00.0190101692069711535 | 2023-08-15 16:37:03 | | a6935989-3b49-11ee-935a-00163e13bca3 | 12003 | 2023-08-15 16:56:40 | 2023-08-15 17:01:40 | 2023-08-15 17:01:40 | RUNNING | 1 | 127.00.00.0290101692069658426 | 2023-08-15 16:37:03 | | a7b5e137-3b49-11ee-8b43-00163e10863a | 12003 | 2023-08-15 16:56:42 | 2023-08-15 17:01:42 | 2023-08-15 17:01:42 | PENDING | 1 | 127.00.00.0390101692069711535 | 2023-08-15 16:37:03 | +--+--++++--+-+++ ```
Project: Druid (App Definition and Development / Database)
File: timeboundaryquery.md

id: timeboundaryquery title: "TimeBoundary queries" sidebar_label: "TimeBoundary" <!-- ~ 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. --> :::info Apache Druid supports two query languages: and . This document describes a query type that is only available in the native language. ::: Time boundary queries return the earliest and latest data points of a data set. The grammar is: ```json { "queryType" : "timeBoundary", "dataSource": "sample_datasource", "bound" : < "maxTime" | "minTime" > # optional, defaults to returning both timestamps if not set "filter" : { "type": "and", "fields": [<filter>, <filter>, ...] } # optional } ``` There are 3 main parts to a time boundary query: |property|description|required?| |--|--|| |queryType|This String should always be "timeBoundary"; this is the first thing Apache Druid looks at to figure out how to interpret the query|yes| |dataSource|A String or Object defining the data source to query, very similar to a table in a relational database. See for more information.|yes| |bound | Optional, set to `maxTime` or `minTime` to return only the latest or earliest timestamp. Default to returning both if not set| no | |filter|See |no| |context|See |no| The format of the result is: ```json [ { "timestamp" : "2013-05-09T18:24:00.000Z", "result" : { "minTime" : "2013-05-09T18:24:00.000Z", "maxTime" : "2013-05-09T18:37:00.000Z" } } ] ```