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

+++ title = "`explicit basicresult(basicresult<R, S, P> &&)`" description = "Explicit converting move constructor from compatible `basicresult`. Available if `predicate::enablecompatible_conversion<R, S, P>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "explicit-constructors", "converting-constructors"] weight = 320 +++ Explicit converting move constructor from compatible `basicresult`. Calls {{% api "void onresultmoveconstruction(T *, U &&) noexcept" %}} with `this` and the input. Requires: `predicate::enablecompatibleconversion<R, S, P>` is true. Complexity: Same as for the move constructors of the underlying types. Constexpr, triviality and noexcept of underlying operations is propagated. Guarantees: If an exception is thrown during the operation, the object is left in a partially completed state, as per the normal rules for the same operation on a `struct`.
Project: KICS (Provisioning / Security & Compliance)
File: 1c1325ff-831d-43a1-973e-839ae57dfcc0.md

title: Volume Has Sensitive Host Directory hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 1c1325ff-831d-43a1-973e-839ae57dfcc0 Query name: Volume Has Sensitive Host Directory Platform: DockerCompose Severity: <span style="color:#bb2124">High</span> Category: Build Process URL: Container has sensitive host directory mounted as a volume<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" version: "3.9" services: db: image: db volumes: data-volume:/var/lib/db backup: image: backup-service volumes: /var/lib/backup/data volumes: data-volume: ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="18" version: "3.9" services: web: image: nginx:alpine volumes: type: volume source: vol target: /data volume: nocopy: true type: bind source: ./static target: /opt/app/static volumes: vol: driver: local driver_opts: device: /var/lib/backup/data o: bind ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="12" version: '3' volumes: wordpress-db-data: driver: local-persist driver_opts: mountpoint: ${CONTAINERVOLUME}/dockerData/mysql wordpress: wp-content: driver: local-persist driver_opts: mountpoint: /var/data ``` <details><summary>Positive test num. 4 - yaml file</summary> ```yaml hl_lines="11" version: "3.8" services: yesno: image: docker.encEx.com/yesno/yesno:v1.1 container_name: "yesno-${MODE}" entrypoint: "/bin/sh" restart: unless-stopped volumes: type: bind source: /etc/exercise target: /etc/exercise type: volume source: yesno-1 target: /var/www/yesno type: volume source: yesno-2 target: /var/lib/exercise volumes: yesno-1: name: yesno-1 yesno-2: name: yesno-2 ``` </details> ```yaml title="Negative test num. 1 - yaml file" version: "3" services: proxy: build: ./pyproxy deploy: mode: replicated placement: constraints: [node.role == manager] replicas: 8 depends_on: storage-node-1 storage-node-2 storage-node-3 storage-node-4 storage-node-5 storage-node-6 storage-node-7 storage-node-8 storage-node-9 storage-node-10 storage-node-11 storage-node-12 storage-node-13 storage-node-14 storage-node-15 storage-node-16 zoo1: image: zookeeper restart: always ports: 2181:2181 environment: ZOOMYID=1 deploy: mode: replicated placement: constraints: [node.role == manager] metadata: image: redis:3.2.8 command: redis-server --appendonly yes deploy: mode: replicated placement: constraints: [node.role == manager] volumes: ./volumes/metadata/:/data/ ``` ```yaml title="Negative test num. 2 - yaml file" version: '3' volumes: wordpress-db-data: driver: local-persist driver_opts: mountpoint: ${CONTAINERVOLUME}/dockerData/mysql wordpress: wp-content: driver: local-persist driver_opts: mountpoint: ${CONTAINERVOLUME}/wp-content ``` ```yaml title="Negative test num. 3 - yaml file" version: "3.9" services: web: image: nginx:alpine ports: "80:80" volumes: type: volume source: mydata target: /data volume: nocopy: true type: bind source: ./static target: /opt/app/static networks: webnet: volumes: mydata: ```
Project: StarRocks (App Definition and Development / Database)
File: SHOW_BACKUP.md

displayed_sidebar: "English" Views the last BACKUP task in a specified database. NOTE Only the information of the last BACKUP task is saved in StarRocks. ```SQL SHOW BACKUP [FROM <db_name>] ``` | Parameter | Description | | - | -- | | db_name | Name of the database that the BACKUP task belongs to. | | Return | Description | | -- | | | JobId | Unique job ID. | | SnapshotName | Name of the data snapshot. | | DbName | Name of the database that the BACKUP task belongs to. | | State | Current state of the BACKUP task:<ul><li>PENDING: Initial state after submitting a job.</li><li>SNAPSHOTING: Creating snapshot.</li><li>UPLOADSNAPSHOT: Snapshot complete, ready for upload.</li><li>UPLOADING: Uploading snapshot.</li><li>SAVEMETA: Creating local metadata files.</li><li>UPLOAD_INFO: Uploading metadata files and information of the BACKUP task.</li><li>FINISHED: BACKUP task finished.</li><li>CANCELLED: BACKUP task failed or cancelled.</li></ul> | | BackupObjs | Backed up objects. | | CreateTime | Task submission time. | | SnapshotFinishedTime | Snapshot completion time. | | UploadFinishedTime | Snapshot upload completion time. | | FinishedTime | Task completion Time. | | UnfinishedTasks | Unfinished subtask IDs in the SNAPSHOTING and UPLOADING phases. | | Progress | The progress of snapshot uploading tasks. | | TaskErrMsg | Error messages. | | Status | Status information. | | Timeout | Task timeout. Unit: second. | Example 1: Views the last BACKUP task in the database `example_db`. ```SQL SHOW BACKUP FROM example_db; ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: overview-of-database-connection.md

title: Connect database from anywhere description: How to connect to a database keywords: [connect to a database] sidebar_position: 1 sidebar_label: Overview After the deployment of KubeBlocks and creating clusters, the database runs on Kubernetes as a Pod. You can connect to the database via a client interface or `kbcli`. As the figure below indicates, you must be clear with the purpose of connecting the database. To take a trial of KubeBlocks, and test the database function, or benchmarking with low-flow testing, see . To connect a database in a production environment, or for a high-flow pressure test, see .
Project: KICS (Provisioning / Security & Compliance)
File: e5071f76-cbe7-468d-bb2b-d10f02d2b713.md

title: Nifcloud RDB Has Backup Retention Less Than 2 Day hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e5071f76-cbe7-468d-bb2b-d10f02d2b713 Query name: Nifcloud RDB Has Backup Retention Less Than 2 Day Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Backup URL: The rdb has backup retention less than 2 day<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "nifclouddbinstance" "positive" { identifier = "example" instance_class = "db.large8" } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "nifclouddbinstance" "positive" { identifier = "example" instance_class = "db.large8" backupretentionperiod = 1 } ``` ```tf title="Negative test num. 1 - tf file" resource "nifclouddbinstance" "negative" { identifier = "example" instance_class = "db.large8" backupretentionperiod = 5 } ```
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.2.8.3.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | ConfServlet should respect Accept request header* Conf HTTP service should set response's content type according to the Accept header in the request. | Major | Configuration.dumpConfiguration should redact sensitive information* <!-- markdown --> Configuration.dumpConfiguration no longer prints out the clear text values for the sensitive keys listed in `hadoop.security.sensitive-config-keys`. Callers can override the default list of sensitive keys either to redact more keys or print the clear text values for a few extra keys for debugging purpose. | Major | Introduce a config to allow setting up write pipeline with fewer nodes than replication factor* Added new configuration "dfs.client.block.write.replace-datanode-on-failure.min-replication". The minimum number of replications that are needed to not to fail the write pipeline if new datanodes can not be found to replace failed datanodes (could be due to network failure) in the write pipeline. If the number of the remaining datanodes in the write pipeline is greater than or equal to this property value, continue writing to the remaining nodes. Otherwise throw exception. If this is set to 0, an exception will be thrown, when a replacement can not be found.
Project: ClickHouse (App Definition and Development / Database)
File: asynchronous_metric_log.md

slug: /en/operations/system-tables/asynchronousmetriclog Contains the historical values for `system.asynchronous_metrics`, which are saved once per time interval (one second by default). Enabled by default. Columns: `hostname` () Hostname of the server executing the query. `event_date` () Event date. `event_time` () Event time. `metric` () Metric name. `value` () Metric value. Example ``` sql SELECT * FROM system.asynchronousmetriclog LIMIT 3 \G ``` ``` text Row 1: hostname: clickhouse.eu-central1.internal event_date: 2023-11-14 event_time: 2023-11-14 14:39:07 metric: AsynchronousHeavyMetricsCalculationTimeSpent value: 0.001 Row 2: hostname: clickhouse.eu-central1.internal event_date: 2023-11-14 event_time: 2023-11-14 14:39:08 metric: AsynchronousHeavyMetricsCalculationTimeSpent value: 0 Row 3: hostname: clickhouse.eu-central1.internal event_date: 2023-11-14 event_time: 2023-11-14 14:39:09 metric: AsynchronousHeavyMetricsCalculationTimeSpent value: 0 ``` See Also Contains metrics, calculated periodically in the background. Contains history of metrics values from tables `system.metrics` and `system.events`, periodically flushed to disk.
Project: ClickHouse (App Definition and Development / Database)
File: statistic.md

slug: /en/sql-reference/statements/alter/statistic sidebar_position: 45 sidebar_label: STATISTIC The following operations are available: `ALTER TABLE [db].table ADD STATISTIC (columns list) TYPE type` - Adds statistic description to tables metadata. `ALTER TABLE [db].table DROP STATISTIC (columns list) TYPE type` - Removes statistic description from tables metadata and deletes statistic files from disk. `ALTER TABLE [db].table CLEAR STATISTIC (columns list) TYPE type` - Deletes statistic files from disk. `ALTER TABLE . The first two commands are lightweight in a sense that they only change metadata or remove files. Also, they are replicated, syncing statistics metadata via ZooKeeper. :::note Statistic manipulation is supported only for tables with engine (including variants). :::
Project: Harbor (Provisioning / Container Registry)
File: 4-04-DB-admin-role-view-logs.md

Test 4-04 - User with Admin Role Views Logs (DB Mode) ======= To verify that a user with system admin role can views logs when users are managed locally by Harbor (DB mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database. ( auth_mode is set to db_auth* .) The user data is stored in a local database. A linux host with Docker CLI installed (Docker client). NOTE: The below non-admin user A should NOT be the same as the non-admin user in Test 4-03. Assign an non-admin user A with system admin role. Repeat all steps in Test 4-03. A user with admin role can perform all operations the same as the admin user. Outcome should be the same as Test 4-03. None
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: v1.3.0.md

id: v1.3.0 title: v1.3.0 description: Backstage Release v1.3.0 These are the release notes for the v1.3.0 release of . A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for the hard work in getting this release developed and done. The scaffolder plugin now has a new template editor in addition to the form editor, which is accessible via the context menu on the top right hand corner of the Create page. It allows you to load a template from a local directory, edit it with a preview, execute it in dry-run mode, and view the results. Note that the must be supported by your browser for this to be available. The recommended TypeScript version has been bumped to `~4.7.0`, and thats what the main Backstage repository uses right now for its builds. Each Backstage project manages their version separately however, so there is no rush or immediate effect on users - you can update the `typescript` dependency in your root `package.json` once you feel ready to do so. In 1.2 we introduced expiry times for server-to-server authentication tokens issued from the standard `TokenManager`. At that point in time, the expiry was only added to tokens and not yet enforced. In this release however, it is now also enforced, meaning that expired tokens are considered invalid and will be rejected. Several new have been contributed as replacements for their corresponding discovery processors. Entity providers allow for more control and are over their processing counterparts. `AzureDevOpsEntityProvider` as replacement for `AzureDevOpsDiscoveryProcessor`. PR contributed by `GitlabDiscoveryEntityProvider` as replacement for `GitLabDiscoveryProcessor`. PR contributed by `BitbucketCloudEntityProvider` as a replacement for `BitbucketDiscoveryProcessor` (for Bitbucket Cloud only). PR contributed by View secrets from alongside your components. PR contributed by GitHub Pull Requests Board Plugin is a board that helps you visualize all open pull requests from all repositories owned by a team, with the main goal of reducing the time from opening a PR to merging it. PR contributed by Displays tracing data from alongside your components. PR contributed by `@backstage/plugin-scaffolder-backend`, please upgrade to the latest version if you are using this module. `@backstage/plugin-techdocs-node`, please upgrade to the latest version if you are using this module. We recommend that you keep your Backstage project up to date with this latest release. For more guidance on how to upgrade, check out the documentation for . Below you can find a list of links and references to help you learn about and start using this new release. , , and Backstage's for discussions and support Backstage , , , and Sign up for our if you want to be informed about what is happening in the world of Backstage.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.29.md

layout: release date: 2022-11-24 tag: v0.6.29 language: en server - fixes misspells and other linting warnings @paularah (#6544) Upgrade Meshkit and add meshmodel APIs @Revolyssup (#6565) Uncomment static k8s oam registeration @Revolyssup (#6562) [Extensions-cypress test fix] meshery-extensions redirections issue fix @Abhishek-kumar09 (#6558) Upgrade meshkit and meshmodel register API changes @Revolyssup (#6559) Send notifications on Content saving @Revolyssup (#6530) Move GetOAMWorkloads to ProviderAuth @Revolyssup (#6545) Fix issue #6273 - updated api endpoints and improved error messages for 'mesheryctl exp filter' commands @SufyaanKhateeb (#6434) [mesheryctl] improve the error messages shown to users for "mesheryctl" @XDRAGON2002 (#6356) removed warnings by adding key attributes @sam1code (#6426) Undeploy icon issue fixed on page: /configuration/patterns. @Krishna2323 (#6563) [Workflow] Build script Failing @Abhishek-kumar09 (#6557) [Node Configuration] Bugs fixes @harkiratsm (#6547) [Events] Fix: Event Source is not getting created @Abhishek-kumar09 (#6546) [Workflow] Build script Failing @Abhishek-kumar09 (#6557) Typo error corrected @AgniveshChaubey (#6555) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @AgniveshChaubey, @Chadha93, @Krishna2323, @Revolyssup, @SufyaanKhateeb, @XDRAGON2002, @harkiratsm, @l5io, @leecalcote, @paularah, @sam1code and l5io
Project: Microcks (App Definition and Development / Application Definition & Image Build)
File: mongodb-indexes.md

From a certain size of MongoDB, it can be interesting to add some indexes to your database. Here are below the indexes of interest with the commands on how to create them in your database: ```shell db.dailyStatistic.createIndex( {day: -1, serviceName: 1, serviceVersion: -1}, {name: "day-1serviceName1serviceVersion-1"} ); db.eventMessage.createIndex( {operationId: -1}, {name: "operationId-1"} ); db.eventMessage.createIndex( {testCaseId: -1}, {name: "testCaseId-1"} ); db.request.createIndex( {operationId: -1}, {name: "operationId-1"} ); db.request.createIndex( {testCaseId: -1}, {name: "testCaseId-1"} ); db.response.createIndex( {operationId: -1}, {name: "operationId-1"} ); db.response.createIndex( {testCaseId: -1}, {name: "testCaseId-1"} ); db.testResult.createIndex( {serviceId: -1}, {name: "serviceId-1"} ); db.testConformanceMetric.createIndex( {serviceId: -1}, {name: "serviceId-1"} ); ``` And how to drop them if you find they are not efficient enough: ```shell db.dailyStatistic.dropIndex("day-1serviceName1serviceVersion-1"); db.eventMessage.dropIndex("operationId-1"); db.eventMessage.dropIndex("testCaseId-1"); db.request.dropIndex("operationId-1"); db.request.dropIndex("testCaseId-1"); db.response.dropIndex("operationId-1"); db.response.dropIndex("testCaseId-1"); db.testResult.dropIndex("serviceId-1"); db.testConformanceMetric.dropIndex("serviceId-1"); ```
Project: Druid (App Definition and Development / Database)
File: http-compression.md

id: http-compression title: "HTTP compression" <!-- ~ 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 supports http request decompression and response compression, to use this, http request header `Content-Encoding:gzip` and `Accept-Encoding:gzip` is needed to be set. |Property|Description|Default| |--|--|-| |`druid.server.http.compressionLevel`|The compression level. Value should be between [-1,9], -1 for default level, 0 for no compression.|-1 (default compression level)| |`druid.server.http.inflateBufferSize`|The buffer size used by gzip decoder. Set to 0 to disable request decompression.|4096|
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: 2.2.md

Here's what we've been working on: AI-Assisted YAML Resource Creation Simplify YAML manifest creation Validate created resources Helm Chart Explorer Discover and install Helm charts Flexible installation options Other Enhancements Sample Project for exploration Enhanced Pod log readability and search Quick cluster management actions Graph view in Cluster Insights Bug fixes and contributions For more info about these new features and additional updates
Project: Apache Heron (App Definition and Development / Streaming & Messaging)
File: uploaders-http.md

id: version-0.20.3-incubating-uploaders-http title: HTTP sidebar_label: HTTP original_id: uploaders-http <!-- 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. --> When a topology is submitted to Heron, the topology jars will be uploaded to a stable location. The submitter will provide this location to the scheduler and it will pass it to the each container. Heron can use a Http uploader to upload topology jar distribution to a stable Http location. You can make Heron aware of the Http uploader by modifying the `uploader.yaml` config file specific for the Heron cluster. Youll need to specify the following for each cluster: `heron.class.uploader` Indicate the uploader class to be loaded. You should set this to `org.apache.heron.uploader.http.HttpUploader` `heron.uploader.http.uri` Provides the name of the URI where the topology jar should be uploaded. Below is an example configuration (in `uploader.yaml`) for a Http uploader: ```yaml heron.class.uploader: org.apache.heron.uploader.http.HttpUploader heron.uploader.http.uri: http://localhost:9000/api/v1/file/upload ``` Also Heron's API server can be used as a file server for the HttpUploader to upload topology package/jars as follows: ``` ${HOME}/.heron/bin/heron-apiserver --cluster nomad --base-template nomad -D heron.statemgr.connection.string=<zookeeperhost:zookeeperport> -D heron.nomad.scheduler.uri=<scheduler_uri> -D heron.class.uploader=org.apache.heron.uploader.http.HttpUploader --verbose ``` Also Http Server that topology package/jars are uploaded needs to return an URI upon upload so that Heron will know the location to download in the future.
Project: Neo4j (App Definition and Development / Database)
File: cypher-shell.1.md

% CYPHER-SHELL(1) % Neo4j Developers % 6 April 2017 cypher-shell - A command line shell for Neo4j cypher-shell [option...] [cypher] Please see cypher-shell --help for an up to date list of supported options. https://neo4j.com/docs/
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-config-gke.md

layout: default title: mesheryctl-system-config-gke permalink: reference/mesheryctl/system/config/gke redirect_from: reference/mesheryctl/system/config/gke/ type: reference display-title: "false" language: en command: system subcommand: config Configure Meshery to use GKE cluster Configure Meshery to connect to GKE cluster <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system config gke [flags] </div> </pre> Configure Meshery to connect to GKE cluster using auth token <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system config gke --token auth.json </div> </pre> Configure Meshery to connect to GKE cluster (if session is logged in using login subcommand) <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system config gke </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for gke -t, --token string Path to token for authenticating to Meshery API </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.