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

displayed_sidebar: "English" StarRocks supports backing up data to alicloud OSS / AWS S3 (or object storage compatible with S3 protocol). Suppose there are two StarRocks clusters, namely DB1 cluster and DB2 cluster. We need to back up the data in DB1 to alicloud OSS and then restore it to DB2 when necessary. The general process of backup and recovery is as follows: Execute SQL in DB1 and DB2 respectively: ```sql CREATE REPOSITORY `repository name` WITH BROKER `broker_name` ON LOCATION "oss://bucket name/path" PROPERTIES ( "fs.oss.accessKeyId" = "xxx", "fs.oss.accessKeySecret" = "yyy", "fs.oss.endpoint" = "oss-cn-beijing.aliyuncs.com" ); ``` a. Both DB1 and DB2 need to be created, and the created REPOSITORY name should be the same. View the repository: ```sql SHOW REPOSITORIES; ``` b. broker_ name needs to fill in the broker name in a cluster. View BrokerName: ```sql SHOW BROKER; ``` c. The path after fs.oss.endpoint does not need to have a bucket name. BACKUP the tables to be backed up to the cloud repository in DB1. Execute SQL in DB1: ```sql BACKUP SNAPSHOT [dbname].{snapshotname} TO `repository_name` ON ( `table_name` [PARTITION (`p1`, ...)], ... ) PROPERTIES ("key"="value", ...); ``` ```plain text PROPERTIES currently supports the following properties: "type" = "full": indicates that this is a full update (default). "timeout" = "3600": task timeout. The default is one day. The unit is seconds. ``` StarRocks does not support full database backup at present. We need to specify the tables or partitions to be backed up ON (...), and these tables or partitions will be backed up in parallel. View the backup tasks in progress (note that only one backup task can be performed at the same time): ```sql SHOW BACKUP FROM db_name; ``` After the backup is completed, you can check whether the backup data in the OSS already exists (unnecessary backups need to be deleted in the OSS): ```sql SHOW SNAPSHOT ON OSS repository name; ``` For data restore in DB2, there is no need to create a table structure to be restored in DB2. It will be created automatically during the Restore operation. Perform restore SQL: ```sql RESTORE SNAPSHOT [dbname].{snapshotname} FROMrepository_name`` ON ( 'tablename' [PARTITION ('p1', ...)] [AS 'tblalias'], ... ) PROPERTIES ("key"="value", ...); ``` View the restore progress: ```sql SHOW RESTORE; ```
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.0.12-en.md

This version included a refactoring of MQTT bridge config. The older version config file created from v5.0.11 or earlier will be converted to according to the new schema. Please note, the request body of `/bridges` API to configure MQTT brdige is changed in a incompatible way. Disable global garbage collection by `node.globalgcinterval = disabled` Improve the CLI to avoid waste atom table when typing erros . Start building MacOS packages for Apple Silicon hadrdware . Remove support for setting shared subscriptions using the non-standard `$queue` feature . Shared subscriptions are now part of the MQTT spec. Use `$share` instead. Refactor authn API by replacing `POST /authentication/{id}/move` with `PUT /authentication/{id}/position/{position}`. . Same is done for `/listeners/{listener_id}/authentication/id/...`. Redesign `/rules` API to make `metrics` a dedicated resources rather than being included with every response . Add more PSK ciphers support . Improve `emqx_retainer` write performance: get rid of transactions on write . HTTP client library `ehttpc` upgraded from `0.4.0` to `0.4.2` . Add `handshake_timeout` option to MQTT SSL listener . Upgrade dashboard to . Users can define the `externalTrafficPolicy` of service in EMQX Helm Chart . Return `204` instead of `200` for `POST /gateway/lwm2m/clients/{clientid}/{read,write,observe}` . Make possible to create an authentication entirely from environment variable . As an example, one can now enable MySQL auth with: `env EMQXAUTHENTICATION1='{mechanism="passwordbased",backend="mysql",server="localhost:3306",database="emqx",username="emqx",password="",query="SELECT passwordhash,salt FROM mqttuser WHERE username=${username} LIMIT 1",enable=true}'`. Prior to this change, overrides only work on top of existing authentication, for example, if there is already MySQL auth configured in `emqx.conf` but we want to disable it, we can do it with `env EMQXAUTHENTICATION1_ENABLE=false`. Start building packages for Amazon Linux 2 . Fix that the obsolete SSL files aren't deleted after the ExHook config update . Fix doc and schema for `/trace` API . Return `404` for `/telemetry/data` in case it's disabled . Fix some potential MQTT packet parse errors . Fixed EMQX Helm Chart deployment error . Fixed the `Discovery error: no such service` error occurred during helm chart deployment, resulting in an abnormal discovery of cluster nodes. Fixed issue that caused EMQX Helm Chart to fail when modifying some of EMQX's configuration items via environment variables. Fix shadowing `'client.authenticate'` callbacks by `emqxauthenticator`. Now `emqxauthenticator` passes execution to the further callbacks if none of the authenticators matches . Return `400` if query param `node` is not a known node in `/trace/:id/download?node={node}` . `POST /traces` to return `409` in case of duplicate . Fix bridging function, when both ingress and egress bridges are configured, egress bridge does not work . Fix EMQX Helm Chart using incorrect secret values when custom credentials are provided .
Project: Sonobuoy (Provisioning / Security & Compliance)
File: sonobuoy_get_pod.md

Fetch sonobuoy pods ``` sonobuoy get pod [flags] ``` ``` -h, --help help for pod -n, --namespace string The namespace to run Sonobuoy in. Only one Sonobuoy run can exist per namespace simultaneously. (default "sonobuoy") -p, --plugin string Plugin to locate pods for ``` ``` --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) ``` - Fetches Sonobuoy resources of a specified type
Project: YugabyteDB (App Definition and Development / Database)
File: tsget.md

title: TSGET linkTitle: TSGET description: TSGET menu: preview: parent: api-yedis weight: 2420 aliases: /preview/api/redis/tsget /preview/api/yedis/tsget type: docs `TSGET key timestamp` This command fetches the value for the given `timestamp` in the time series that is specified by the given `key`. If the given `key` or `timestamp` does not exist, nil is returned. If the given `key` is associated with non-time series data, an error is raised. If the given `timestamp` is not a valid signed 64 bit integer, an error is raised. Returns the value for the given `timestamp`. The timestamp can be arbitrary integers used just for sorting values in a certain order. ```sh $ TSADD cpu_usage 10 "70" ``` ``` "OK" ``` ```sh $ TSADD cpu_usage 20 "80" 30 "60" 40 "90" ``` ``` "OK" ``` We could also encode the timestamp as yyyymmddhhmm, since this would still produce integers that are sortable by the actual timestamp. ```sh $ TSADD cpu_usage 201710311100 "50" ``` ``` "OK" ``` A more common option would be to specify the timestamp as the unix timestamp. ```sh $ TSADD cpu_usage 1509474505 "75" ``` ``` "OK" ``` ```sh $ TSGET cpu_usage 10 ``` ``` "70" ``` ```sh $ TSGET cpu_usage 100 ``` ``` (nil) ``` ```sh $ TSGET cpu_usage 201710311100 ``` ``` "50" ``` ```sh $ TSGET cpu_usage 1509474505 ``` ``` "75" ``` An error is returned when the timestamp is not an int64. ```sh $ TSGET cpu_usage xyz ``` ``` (error) Request was unable to be processed from server. ``` , , , , ,
Project: Sonobuoy (Provisioning / Security & Compliance)
File: 2019-10-01-new-github-org.md

title: Announcing a new GitHub home for Sonobuoy image: /img/vmware-tanzu.svg excerpt: Big news! We're moving, but the project stays the same. author_name: John Schnake author_url: https://github.com/johnschnake author_avatar: /img/contributors/john-schnake.png categories: [kubernetes, sonobuoy, conformance] tags: ['Sonobuoy Team', 'John Schnake'] date: 2019-10-01 slug: new-github-org We are now part of a brand new GitHub organization: VMware Tanzu. VMware Tanzu is a new family of projects, products and services for the cloud native world. The Sonobuoy project is a critical part to conformance tests on Kubernetes, so it makes sense that it would be moved to sit alongside all the other VMware-supported cloud native repositories. You can read more about this change in this [VMware blog post]. As always, we welcome feedback and participation in the development of Sonobuoy. All information on how to contact us or become involved can be found on our [community page].
Project: ShardingSphere (App Definition and Development / Database)
File: show-migration-rule.en.md

+++ title = "SHOW MIGRATION RULE" weight = 1 +++ The `SHOW MIGRATION RULE` syntax is used to query migration rule. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowMigrationRule ::= 'SHOW' 'MIGRATION' 'RULE' ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} | Column | Description | |-|-| | read | Data reading configuration | | write | Data writing configuration | | stream_channel | Data channel | Query migration rule ```sql SHOW MIGRATION RULE; ``` ```sql mysql> SHOW MIGRATION RULE; +--+--+-+ | read | write | stream_channel | +--+--+-+ | {"workerThread":20,"batchSize":1000,"shardingSize":10000000} | {"workerThread":20,"batchSize":1000} | {"type":"MEMORY","props":{"block-queue-size":"2000"}} | +--+--+-+ 1 row in set (0.01 sec) ``` `SHOW`, `MIGRATION`, `RULE`
Project: Harbor (Provisioning / Container Registry)
File: 5-02-OVA-reboot.md

Test 5-02 - OVA Reboot ======= To verify that an OVA version of Harbor can be rebooted. Its configuration remains unchanged and should work the same way as before a reboot. User guide, installation guide of Harbor OVA version. This test requires an OVA binary of Harbor. A vCenter, at least an ESX host, and a network that supports DHCP. A linux host with Docker CLI installed (Docker client). From vSphere Web Client, import Harbor's OVA onto an ESX host. In the deployment wizard, enter different passwords of Linux root user, Harbor admin user and MySQL root user. Leave the networking settings blank. Configure email settings. (can be mail server that does not exist ) Power on the imported OVA. Wait a few minutes for the VM's booting and its IP address comes up in vCenter. (may need to refresh in Web Client) Open a browser and enter http://VMIPaddress. Log in as admin user of Harbor. Create a new project. On a Docker client host, use `docker login <harbor_host>` command to log in as the admin user. Run some `docker push` and `docker pull` commands to push images to the project and pull from the project. On vSphere, open the console of Harbor's VM, log in as root user using the password entered during deployment. On vCenter Web Client, reboot the VM. (soft reboot) After the VM starts up, repeat Step 7-12, should work the same. Power off the VM, and the power it on. (hard reboot) After the VM starts up, repeat Step 7-12, should work the same. On vSphere, open the console of Harbor's VM, log in as root user, type `ovfenv` command to verify environment variables are the same as those entered during deployment. In Step 1-12, everything should work without errors. The passwords entered during deployment should work in Step 7, 9 and 11. In Step 14, 16, the VM should work the same before the reboot or power-off. Step 17, environment variables should remain unchanged as those entered during deployment. None
Project: Cloud Custodian (Provisioning / Automation & Configuration)
File: metrics.md

Collect application metrics Permanent s3 archive of high resolution metrics Gather Historical metrics (non current extant resources) S3 Archival account/region/datestring/resource-type/resource-id/uuid.json.gz fine grained would be a stream of params for collection get metrics tasks for distributed collection Todo [ ] incremental metrics [ ] dynamic period adjustment based on window [ ] metrics in config / supplement defaults
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.WatchPusher.md

/ / WatchPusher .WatchPusher callbacks to indicate state changes allOffline(): `void` The entire underlying model has disappared `void` batchUpdateDone(): `void` A batch of calls to `update` is complete `void` done(): `void` No more updates will be performed `void` footer(`streams`): `void` | Name | Type | | :-- | : | | `streams` | `string`[] | `void` header(`response`): `void` The header model has changed | Name | Type | | : | :- | | `response` | | `void` offline(`rowKey`): `void` The given keyed row is gone | Name | Type | | :- | :- | | `rowKey` | `string` | `void` progress(`progress`): `void` Update progress bar for a given row | Name | Type | | :- | :- | | `progress` | `Object` | | `progress.fileName?` | `string` | | `progress.message?` | `string` | | `progress.percentComplete` | `number` | | `progress.rowIdx` | `number` | | `progress.totalSize?` | `number` | `void` setBody(`response`): `void` set table body | Name | Type | | : | : | | `response` | [] | `void` update(`response`, `batch?`, `changed?`, `idxToUpdate?`): `void` | Name | Type | Description | | :- | :- | :- | | `response` | | Updated row model | | `batch?` | `boolean` | - | | `changed?` | `boolean` | - | | `idxToUpdate?` | `number` | - | `void`
Project: YDB (App Definition and Development / Database)
File: tools-copy.md

Using the `tools copy` subcommand, you can create a copy of one or more DB tables. The copy operation leaves the source table unchanged while the copy contains all the source table data. General format of the command: ```bash {{ ydb-cli }} [global options...] tools copy [options...] ``` `global options`: . `options`: . View a description of the command to copy a table: ```bash {{ ydb-cli }} tools copy --help ``` | Parameter name | Parameter description | | | `--timeout` | The time within which the operation should be completed on the server. | | `--item <property>=<value>,...` | Operation properties. You can specify the parameter more than once to copy several tables in a single transaction.<br/>Required properties:<ul><li>`destination`, `dst`, `d`: Path to target table. If the destination path contains folders, they must be created in advance. No table with the destination name should exist.</li><li>`source`, `src`, `s`: Path to source table.</li></ul> | {% include %} Create the `backup` folder in the DB: ```bash {{ ydb-cli }} -p quickstart scheme mkdir backup ``` Copy the `series` table to a table called `series-v1`, the `seasons` table to a table called `seasons-v1`, and `episodes` to `episodes-v1` in the `backup` folder: ```bash {{ ydb-cli }} -p quickstart tools copy --item destination=backup/series-v1,source=series --item destination=backup/seasons-v1,source=seasons --item destination=backup/episodes-v1,source=episodes ``` View the listing of objects in the `backup` folder: ```bash {{ ydb-cli }} -p quickstart scheme ls backup ``` Result: ```text episodes-v1 seasons-v1 series-v1 ```
Project: ClickHouse (App Definition and Development / Database)
File: v22.3.12.19-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix TGZ packages. (). Backported in : fix HashMethodOneNumber get wrong key value when column is const. (). Backported in : Fix bug in collectFilesToSkip() by adding correct file extension(.idx or idx2) for indexes to be recalculated, avoid wrong hard links. Fixed . (). Backported in : Fix insufficient argument check for encryption functions (found by query fuzzer). This closes . (). Backported in : Fix possible segfault in CapnProto input format. This bug was found and send through ClickHouse bug-bounty by kiojj*. (). fix heap buffer overflow by limiting http chunk size (). Reduce changelog verbosity in CI (). Backport the upstream clickhouse_helper.py ().
Project: Meshery (Provisioning / Automation & Configuration)
File: dapr.md

layout: integration title: Dapr subtitle: Collaborative and visual infrastructure as code for Dapr image: /assets/img/integrations/dapr/icons/color/dapr-color.svg permalink: extensibility/integrations/dapr docURL: https://docs.meshery.io/extensibility/integrations/dapr description: integrations-category: Serverless integrations-subcategory: Framework registrant: Artifact Hub components: name: component colorIcon: assets/img/integrations/dapr/components/component/icons/color/component-color.svg whiteIcon: assets/img/integrations/dapr/components/component/icons/white/component-white.svg description: name: resiliency colorIcon: assets/img/integrations/dapr/components/resiliency/icons/color/resiliency-color.svg whiteIcon: assets/img/integrations/dapr/components/resiliency/icons/white/resiliency-white.svg description: name: configuration colorIcon: assets/img/integrations/dapr/components/configuration/icons/color/configuration-color.svg whiteIcon: assets/img/integrations/dapr/components/configuration/icons/white/configuration-white.svg description: name: http-endpoint colorIcon: assets/img/integrations/dapr/components/http-endpoint/icons/color/http-endpoint-color.svg whiteIcon: assets/img/integrations/dapr/components/http-endpoint/icons/white/http-endpoint-white.svg description: name: subscription colorIcon: assets/img/integrations/dapr/components/subscription/icons/color/subscription-color.svg whiteIcon: assets/img/integrations/dapr/components/subscription/icons/white/subscription-white.svg description: featureList: [ "Helps you write resilient and secured microservices.", "Provides you with APIs that abstract away the complexity of common challenges developers encounter regularly when building distributed applications.", "Leverages proven practices for distributed application development that enable you to build resilient, secured systems." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.5.1.en.md

Fixed an issue that data integration configurations failed to load correctly during upgrades from EMQX version 5.0.2 to newer releases. Fixed an issue that users were unable to subscribe to or unsubscribe from shared topic filters via HTTP API. The affected APIs include: `/clients/:clientid/subscribe` `/clients/:clientid/subscribe/bulk` `/clients/:clientid/unsubscribe` `/clients/:clientid/unsubscribe/bulk` Fixed an issue where logs of the LDAP driver were not being captured. Now, all logs are recorded at the `info` level. The Prometheus API experienced crashes when the specified SSL certificate file did not exist in the given path. Now, when an SSL certificate file is missing, the `emqxcertexpiry_at` metric will report a value of 0, indicating the non-existence of the certificate. Redacted sensitive information in HTTP headers to exclude authentication and authorization credentials from `debug` level logs in the HTTP Server connector, mitigating potential security risks. Fixed an issue where the rule engine's SQL built-in function `datetounix_ts` produced incorrect results for dates starting from March 1st on leap years.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: default.md

title: "{{ replace .Name "-" " " | title }}" <!-- 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: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: start-stop-a-cluster.md

title: Stop/Start a PostgreSQL cluster description: How to start/stop a PostgreSQL cluster keywords: [postgresql, stop a cluster, start a cluster] sidebar_position: 5 sidebar_label: Stop/Start You can stop/start a cluster to save computing resources. When a cluster is stopped, the computing resources of this cluster are released, which means the pods of Kubernetes are released, but the storage resources are reserved. Start this cluster again if you want to restore the cluster resources from the original storage by snapshots. Configure the name of your cluster and run the command below to stop this cluster. ```bash kbcli cluster stop <name> ``` *Example* ```bash kbcli cluster stop pg-cluster ``` Run the command below to stop a cluster. ```bash kubectl apply -f - <<EOF apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: name: pg-cluster generateName: stop- spec: clusterRef: pg-cluster type: Stop EOF ``` Configure replicas as 0 to delete pods. ```yaml apiVersion: apps.kubeblocks.io/v1alpha1 kind: Cluster metadata: name: pg-cluster spec: clusterDefinitionRef: postgresql clusterVersionRef: postgresql-14.7.0 terminationPolicy: WipeOut componentSpecs: name: pg-replication componentDefRef: postgresql monitor: false replicas: 0 volumeClaimTemplates: name: data spec: storageClassName: standard accessModes: ReadWriteOnce resources: requests: storage: 1Gi ``` Configure the name of your cluster and run the command below to start this cluster. ```bash kbcli cluster start <name> ``` *Example* ```bash kbcli cluster start pg-cluster ``` Run the command below to start a cluster. ```bash kubectl apply -f - <<EOF apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: name: pg-cluster generateName: start- spec: clusterRef: pg-cluster type: Start EOF ``` Change replicas back to the original amount to start this cluster again. ```yaml apiVersion: apps.kubeblocks.io/v1alpha1 kind: Cluster metadata: name: pg-cluster spec: clusterDefinitionRef: postgresql clusterVersionRef: postgresql-14.7.0 terminationPolicy: WipeOut componentSpecs: name: pg-replication componentDefRef: postgresql monitor: false replicas: 1 volumeClaimTemplates: name: data spec: storageClassName: standard accessModes: ReadWriteOnce resources: requests: storage: 1Gi ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_storage_bucket_iam_binding.md

+++ title = "googlestoragebucketiambinding resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlestoragebucketiambinding" identifier = "inspec/resources/gcp/googlestoragebucketiambinding.md googlestoragebucketiambinding resource" parent = "inspec/resources/gcp" +++ A `googlestoragebucketiambinding` is used to test a Google Bucket Iam Bindings ```ruby describe googlestoragebucketiambinding(bucket: "bucket", role: "roles/editor") do it { should exist } its('members') { should include 'user:testuser@example.com' } end ``` Properties that can be accessed from the `googlestoragebucketiambinding` resource: `role` : Role that is assigned to members. For example, roles/viewer, roles/editor, or roles/owner. `members` : Specifies the identities requesting access for a Cloud Platform resource. Ensure the is enabled for the current project.