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

title: kbcli backuprepo create Create a backup repo ``` kbcli backuprepo create [NAME] [flags] ``` ``` kbcli backuprepo create \ --provider s3 \ --region us-west-1 \ --bucket test-kb-backup \ --access-key-id <ACCESS KEY> \ --secret-access-key <SECRET KEY> \ --default kbcli backuprepo create my-backup-repo \ --provider s3 \ --region us-west-1 \ --bucket test-kb-backup \ --access-key-id <ACCESS KEY> \ --secret-access-key <SECRET KEY> ``` ``` --access-method string Specify the access method for the backup repository, "Tool" is preferred if not specified. options: ["Mount" "Tool"] --default Specify whether to set the created backup repo as default -h, --help help for create --provider string Specify storage provider --pv-reclaim-policy string Specify the reclaim policy for PVs created by this backup repo, the value can be "Retain" or "Delete" (default "Retain") --volume-capacity string Specify the capacity of the new created PVC" (default "100Gi") ``` ``` --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 ``` - BackupRepo command.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.26.md

RabbitMQ `3.11.26` is a maintenance release in the `3.11.x` . This release series . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25 and supports Erlang versions up to `25.3.x`. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . When a topic permission was deleted, an of type `permission.deleted` was emitted in some cases, instead of `topic.permission.deleted`. Investigated by @bedia. GitHub issue: Correctly block publishing AMQP 1.0 connections when a is in effect. GitHub issue: are now available in the dashboard. Contributed by @johanrhodin (CloudAMQP) GitHub issue: `rabbitmq-diagnostics listpoliciesthat_match [queue name]` is a new command that simplifies troubleshooting of policy conflicts. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.26.tar.xz` instead of the source tarball produced by GitHub.
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-filter-delete.md

layout: default title: mesheryctl-filter-delete permalink: reference/mesheryctl/filter/delete redirect_from: reference/mesheryctl/filter/delete/ type: reference display-title: "false" language: en command: filter subcommand: delete Delete a filter file Delete a filter file using the name or ID of a filter <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl filter delete [filter-name | ID] [flags] </div> </pre> Delete the specified WASM filter file using name or ID A unique prefix of the name or ID can also be provided. If the prefix is not unique, the first match will be deleted. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl filter delete [filter-name | ID] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for delete </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -t, --token string Path to token file default from current context -v, --verbose verbose output </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Akri (Provisioning / Automation & Configuration)
File: SECURITY.md

The Akri team and community take security vulnerabilities very seriously. If you find a security-related issue with Akri, we kindly ask you send a report privately to cncf-akri-security@lists.cncf.io and to give us an appropriate time to address and mitigate the vulnerability. All reports will be thoroughly investigated by the Akri maintainers. We will disclose any security vulnerabilities in our . All vulnerabilities and associated information will be treated with full confidentiality. We are thankful for your efforts in keeping Akri secure and we will publicly acknowledge your contributions if you wish.
Project: YugabyteDB (App Definition and Development / Database)
File: pexpire.md

title: PEXPIRE linkTitle: PEXPIRE description: PEXPIRE menu: preview: parent: api-yedis weight: 2233 aliases: /preview/api/redis/pexpire /preview/api/yedis/pexpire type: docs `PEXPIRE key timeout` This command works exactly like EXPIRE but the time to live of the key is specified in milliseconds instead of seconds. Returns integer reply, specifically 1 if the timeout was set and 0 if key does not exist. ```sh $ SET yugakey "Yugabyte" ``` ``` "OK" ``` ```sh $ PEXPIRE yugakey 10000 ``` ``` (integer) 1 ``` ```sh $ PTTL yugakey ``` ``` (integer) 9995 ``` , , ,
Project: Vault (Provisioning / Key Management)
File: serializers-adapters.md

<!-- START doctoc generated TOC please keep comment here to allow auto update --> <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE --> <!-- END doctoc generated TOC please keep comment here to allow auto update --> Prepend internal functions with an underscore to differentiate from Ember methods `_getUrl` Consider using the adapter if the model name is part of the request path Utilize the serializer to remove sending model attributes that do not correspond to an API parameter. Example in ```js export default class SomeSerializer extends ApplicationSerializer { attrs = { attrName: { serialize: false }, }; } ``` Note: this will remove the attribute when calling `snapshot.serialize()` even if the method is called within the serialize method where custom logic may be written The JSON serializer removes attributes with empty arrays
Project: Meshery (Provisioning / Automation & Configuration)
File: credentials.md

layout: default title: Credentials permalink: concepts/logical/credentials type: concepts abstract: Meshery uses one or more Credentials when authenticating to a managed or unmanaged Connection. language: en list: include redirect_from: concepts/credentials Meshery uses one or more Credentials when authenticating to a managed or unmanaged Connection. Credentials are based on the Meshery's with defined attributes. [States for Unmanaged Connections]({{ site.baseurl }}/assets/img/meshsync/states-for-unmanaged-connections.svg)
Project: KICS (Provisioning / Security & Compliance)
File: feature_request.md

name: Feature request about: Suggest an idea/feature for this project title: 'feat(<scope>): <title starting with lowercase letter>' labels: community, feature request assignees: '' Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when \[...\]) Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here.
Project: Tremor (App Definition and Development / Streaming & Messaging)
File: record.md

The `Record` rule defines a set of name-value pairs delimited by `,` a comma. Records are enclosed in `{` and `}` curly braces. The record structure in tremor is backwards compatible with JSON. All JSON records can be read by tremor. Not all tremor records can be read by a JSON reader as tremor supports computations, comments and trailiing `,` commas in its record and array structures.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.139.md

layout: release date: 2023-09-13 tag: v0.6.139 [MeshModel] New shapes @leecalcote (#8762) Remove Firewall Policy @leecalcote (#8759) [server]Fix Index Out of Range Error Handling in Meshery Component Handler @Shiva953 (#8709) Update events_persister.go @MUzairS15 (#8719) [Events] Add API to return available event category and action. @MUzairS15 (#8715) Improve search functionality using debounce @sudhanshutech (#8720) FIXED: adapter deployment permission denied error on docker platform @zakisk (#8694) Show duplicates meshmodels on toggle @sudhanshutech (#8704) Improve search functionality using debounce @sudhanshutech (#8720) created a folder @ritiksaxena124 (#8726) change sort order from asc to desc as default @MUzairS15 (#8725) [UI] Converted UserPreferences and preferences form class-based to fun @mukeshkuiry (#8707) Thank you to our contributors for making this release possible: @MUzairS15, @Shiva953, @Yashsharma1911, @leecalcote, @mukeshkuiry, @nebula-aac, @ritiksaxena124, @sudhanshutech, @zakisk and l5io
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: Datahub.md

DataHub sink connector A sink plugin which use send message to DataHub | name | type | required | default value | |-|--|-|| | endpoint | string | yes | - | | accessId | string | yes | - | | accessKey | string | yes | - | | project | string | yes | - | | topic | string | yes | - | | timeout | int | yes | - | | retryTimes | int | yes | - | | common-options | | no | - | your DataHub endpoint start with http string your DataHub accessId which cloud be access from Alibaba Cloud (string) your DataHub accessKey which cloud be access from Alibaba Cloud (string) your DataHub project which is created in Alibaba Cloud (string) your DataHub topic (string) the max connection timeout (int) the max retry times when your client put record failed (int) Sink plugin common parameters, please refer to for details ```hocon sink { DataHub { endpoint="yourendpoint" accessId="xxx" accessKey="xxx" project="projectname" topic="topicname" timeout=3000 retryTimes=3 } } ``` Add DataHub Sink Connector
Project: KICS (Provisioning / Security & Compliance)
File: 3878dc92-8e5d-47cf-9cdd-7590f71d21b9.md

title: Incorrect Volume Claim Access Mode ReadWriteOnce hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3878dc92-8e5d-47cf-9cdd-7590f71d21b9 Query name: Incorrect Volume Claim Access Mode ReadWriteOnce Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Build Process URL: Kubernetes Stateful Sets must have one Volume Claim template with the access mode 'ReadWriteOnce'<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="72 27" apiVersion: apps/v1 kind: StatefulSet metadata: name: web spec: selector: matchLabels: app: nginx # has to match .spec.template.metadata.labels serviceName: "nginx" replicas: 3 # by default is 1 template: metadata: labels: app: nginx # has to match .spec.selector.matchLabels spec: terminationGracePeriodSeconds: 10 containers: name: nginx image: k8s.gcr.io/nginx-slim:0.8 ports: containerPort: 80 name: web volumeMounts: name: www mountPath: /usr/share/nginx/html volumeClaimTemplates: metadata: name: www spec: accessModes: [ "ReadWriteOnce" ] storageClassName: "my-storage-class" resources: requests: storage: 1Gi metadata: name: aaa spec: accessModes: [ "ReadWriteOnce" ] storageClassName: "my-storage-class" resources: requests: storage: 1Gi apiVersion: apps/v1 kind: StatefulSet metadata: name: web2 spec: selector: matchLabels: app: nginx # has to match .spec.template.metadata.labels serviceName: "nginx" replicas: 3 # by default is 1 template: metadata: labels: app: nginx # has to match .spec.selector.matchLabels spec: terminationGracePeriodSeconds: 10 containers: name: nginx image: k8s.gcr.io/nginx-slim:0.8 ports: containerPort: 80 name: web volumeMounts: name: www mountPath: /usr/share/nginx/html volumeClaimTemplates: metadata: name: www spec: accessModes: [ "ReadWrite" ] storageClassName: "my-storage-class" resources: requests: storage: 1Gi metadata: name: aaa spec: accessModes: [ "ReadWrite" ] storageClassName: "my-storage-class" resources: requests: storage: 1Gi ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: apps/v1 kind: StatefulSet metadata: name: web spec: selector: matchLabels: app: nginx # has to match .spec.template.metadata.labels serviceName: "nginx" replicas: 3 # by default is 1 template: metadata: labels: app: nginx # has to match .spec.selector.matchLabels spec: terminationGracePeriodSeconds: 10 containers: name: nginx image: k8s.gcr.io/nginx-slim:0.8 ports: containerPort: 80 name: web volumeMounts: name: www mountPath: /usr/share/nginx/html volumeClaimTemplates: metadata: name: www spec: accessModes: [ "ReadWriteOnce" ] storageClassName: "my-storage-class" resources: requests: storage: 1Gi ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: timestamp.md

Set the create timestamp to seconds since epoch to allow for deterministic builds (defaults to current time). By default, the created timestamp is changed and written into the image manifest with every commit, causing the image's sha256 hash to be different even if the sources are exactly the same otherwise. When --timestamp is set, the created timestamp is always set to the time specified and therefore not changed, allowing the image's sha256 hash to remain the same. All files committed to the layers of the image is created with the timestamp. If the only instruction in a Containerfile is `FROM`, this flag has no effect.
Project: ClickHouse (App Definition and Development / Database)
File: dashboards.md

slug: /en/operations/system-tables/dashboards Contains queries used by `/dashboard` page accessible though . This table can be useful for monitoring and troubleshooting. The table contains a row for every chart in a dashboard. :::note `/dashboard` page can render queries not only from `system.dashboards`, but from any table with the same schema. This can be useful to create custom dashboards. ::: Example: ``` sql SELECT * FROM system.dashboards WHERE title ILIKE '%CPU%' ``` ``` text Row 1: dashboard: overview title: CPU Usage (cores) query: SELECT toStartOfInterval(eventtime, INTERVAL {rounding:UInt32} SECOND)::INT AS t, avg(ProfileEventOSCPUVirtualTimeMicroseconds) / 1000000 FROM system.metric_log WHERE eventdate >= toDate(now() - {seconds:UInt32}) AND eventtime >= now() - {seconds:UInt32} GROUP BY t ORDER BY t WITH FILL STEP {rounding:UInt32} Row 2: dashboard: overview title: CPU Wait query: SELECT toStartOfInterval(eventtime, INTERVAL {rounding:UInt32} SECOND)::INT AS t, avg(ProfileEventOSCPUWaitMicroseconds) / 1000000 FROM system.metric_log WHERE eventdate >= toDate(now() - {seconds:UInt32}) AND eventtime >= now() - {seconds:UInt32} GROUP BY t ORDER BY t WITH FILL STEP {rounding:UInt32} Row 3: dashboard: overview title: OS CPU Usage (Userspace) query: SELECT toStartOfInterval(event_time, INTERVAL {rounding:UInt32} SECOND)::INT AS t, avg(value) FROM system.asynchronousmetriclog WHERE eventdate >= toDate(now() - {seconds:UInt32}) AND eventtime >= now() - {seconds:UInt32} AND metric = 'OSUserTimeNormalized' GROUP BY t ORDER BY t WITH FILL STEP {rounding:UInt32} Row 4: dashboard: overview title: OS CPU Usage (Kernel) query: SELECT toStartOfInterval(event_time, INTERVAL {rounding:UInt32} SECOND)::INT AS t, avg(value) FROM system.asynchronousmetriclog WHERE eventdate >= toDate(now() - {seconds:UInt32}) AND eventtime >= now() - {seconds:UInt32} AND metric = 'OSSystemTimeNormalized' GROUP BY t ORDER BY t WITH FILL STEP {rounding:UInt32} ``` Columns: `dashboard` (`String`) - The dashboard name. `title` (`String`) - The title of a chart. `query` (`String`) - The query to obtain data to be displayed.
Project: ArangoDB (App Definition and Development / Database)
File: hook_outcome_construction2.md

+++ title = "`void hookoutcomeconstruction(T *, U &&, V &&) noexcept`" description = "(Until v2.2.0) ADL discovered free function hook invoked by the implicit constructors of `basic_outcome`." +++ Removed in Outcome v2.2.0, unless {{% api "BOOSTOUTCOMEENABLELEGACYSUPPORT_FOR" %}} is set to less than `220` to enable emulation. Use {{% api "onoutcomeconstruction(T *, U &&, V &&) noexcept" %}} instead in new code. One of the constructor hooks for {{% api "basicoutcome<T, EC, EP, NoValuePolicy>" %}}, generally invoked by the implicit constructors of `basicoutcome` which consume two arguments. See each constructor's documentation to see which specific hook it invokes. Overridable: By Argument Dependent Lookup. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::hooks` Header: `<boost/outcome/basic_outcome.hpp>`
Project: ShardingSphere (App Definition and Development / Database)
File: readwrite-splitting.en.md

+++ title = "Readwrite-splitting" weight = 3 +++ Read/write splitting YAML configuration is highly readable. The YAML format enables you to quickly understand the dependencies between read/write sharding rules. ShardingSphere automatically creates the ShardingSphereDataSource object according to the YAML configuration, which reduces unnecessary coding for users. ```yaml rules: !READWRITE_SPLITTING dataSourceGroups: <datasourcegroup_name> (+): # Logic data source group name of readwrite-splitting, which uses Groovy's Row Value Expressions SPI implementation to parse by default writedatasource_name: # Write data source name, which uses Groovy's Row Value Expressions SPI implementation to parse by default readdatasource_names: # Read data source names, multiple data source names separated with comma, which uses Groovy's Row Value Expressions SPI implementation to parse by default transactionalReadQueryStrategy (?): # Routing strategy for read query within a transaction, values include: PRIMARY (to primary), FIXED (to fixed data source), DYNAMIC (to any data source), default value: DYNAMIC loadBalancerName: # Load balance algorithm name loadBalancers: <loadbalancername> (+): # Load balance algorithm name type: # Load balance algorithm type props: # Load balance algorithm properties ``` Please refer to for more details about type of algorithm. Add read/write splitting data source. Set the load balancer algorithm. Use read/write data source. ```yaml rules: !READWRITE_SPLITTING dataSourceGroups: readwrite_ds: writeDataSourceName: write_ds readDataSourceNames: readds0 readds1 transactionalReadQueryStrategy: PRIMARY loadBalancerName: random loadBalancers: random: type: RANDOM ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: ISSUE_TEMPLATE.md

Choose one: is this a bug report or feature request? Briefly describe the issue and the expected behavior. Also, please be aware of our . Tell us which version of InSpec (`inspec version` or SHA of a commit) and Operating System distribution you are using Tell us what steps to take to replicate your problem. See for information on how to create a good replication case. If you have already ideas how to solve the issue, add them here. Please include the stacktrace output or link to a gist of it, if there is one.
Project: YugabyteDB (App Definition and Development / Database)
File: onprem.md

title: Configure YugabyteDB Anywhere on premises headerTitle: Overview linkTitle: Overview description: Configure YugabyteDB Anywhere on-premises headcontent: Configure YugabyteDB Anywhere for on-premises menu: v2.18_yugabyte-platform: identifier: configure-5-onprem parent: configure-yugabyte-platform weight: 5 type: docs For overview of how to configure database nodes, select one of the following cloud providers: <ul class="nav nav-tabs-alt nav-tabs-yb"> <li> <a href="../aws/" class="nav-link"> <i class="fa-brands fa-aws"></i> AWS </a> </li> <li> <a href="../gcp/" class="nav-link"> <i class="fa-brands fa-google" aria-hidden="true"></i> GCP </a> </li> <li> <a href="../azure/" class="nav-link"> <i class="fa-brands fa-windows" aria-hidden="true"></i> Azure </a> </li> <li> <a href="../kubernetes/" class="nav-link"> <i class="fa-regular fa-dharmachakra" aria-hidden="true"></i> Kubernetes </a> </li> <li> <a href="../onprem/" class="nav-link active"> <i class="fa-solid fa-building"></i> On-premises </a> </li> </ul> The following diagram depicts the configuration process for on-premises deployments. <div class="image-with-map"> <img src="/images/ee/flowchart/yb-configure-onprem.png" usemap="#image-map"> <map name="image-map"> <area alt="Create admin user" title="Create admin user" href="../../create-admin-user/" coords="296,260,607,320" shape="rect" style="top: 15.9%;height: 3.7%;left: 31%;width: 38%;"> <area alt="On prem cloud provider" title="On prem cloud provider" href="../../set-up-cloud-provider/on-premises/" coords="247,369,653,424" shape="rect" style="top: 22.5%;height: 3.7%;left: 27%;width: 46%;"> <area alt="configure on prem provider-1" title="configure on prem provider-1" href="../../set-up-cloud-provider/on-premises/#step-1-configure-the-on-premises-provider" coords="204,1230,425,1331" shape="rect" style="top: 75.3%;height: 6.1%;left: 22%;width: 25%;"> <area alt="configure on prem provider-2" title="configure on prem provider-2" href="../../set-up-cloud-provider/on-premises/#step-1-configure-the-on-premises-provider" coords="474,1230,695,1328" shape="rect" style="top: 75.3%;height: 6.1%;left: 52.4%;width: 25%;"> </map> </div>