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

title: kbcli cluster describe-backup-policy Describe backup policy ``` kbcli cluster describe-backup-policy [flags] ``` ``` kbcli cluster describe-backup-policy cluster-name kbcli cluster describe-backup-policy cluster-name --name backup-policy-name ``` ``` -h, --help help for describe-backup-policy --name strings Backup policy name ``` ``` --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 ``` - Cluster command.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.47.md

layout: release date: 2024-04-16 tag: v0.7.47 Ripul handoo/mesheryctl/args error @RipulHandoo (#10726) [Chore] Update copyright holder in project license @leecalcote (#10729) [CI] fix: Mesheryctl lint checks failing test @singh1203 (#10643) Revert "Fix mesheryctl publish to remote provider command" @Yashsharma1911 (#10715) Fix mesheryctl publish to remote provider command @Yashsharma1911 (#10714) feat: enhance deployment flow @aabidsofi19 (#10733) expose remote provider capabilities @Aseem22 (#10575) ui bugs and enchanment @captain-Akshay (#10641) chore(Popup): change primary button color @dragon-slayer875 (#10727) Bump tar from 6.1.15 to 6.2.1 in /ui @dependabot (#10718) [Chore] Update copyright holder in project license @leecalcote (#10729) change integration output path to _models collection @vishalvivekm (#10717) Bump tar from 6.1.15 to 6.2.1 in /ui @dependabot (#10718) [CI] fix: Mesheryctl lint checks failing test @singh1203 (#10643) Missing "s" in hyperlink @leecalcote (#10737) Fix the docs to import designs in meshery @11happy (#10676) [Chore] Update copyright holder in project license @leecalcote (#10729) Reduced font size to 0.9rem in <code> @abhishekmmgn (#10722) move from pages/integrations to models collection @vishalvivekm (#10719) Update to providers doc clarifying URLs @sangramrath (#10646) [Docs] Fix broken link: Update toc.yml for managing-connections @jameshorton2337 (#10716) Suggested reading @vishalvivekm (#10699) Thank you to our contributors for making this release possible: @11happy, @Aseem22, @MUzairS15, @RipulHandoo, @Yashsharma1911, @aabidsofi19, @abhishekmmgn, @captain-Akshay, @codeKraken19, @dependabot, @dependabot[bot], @dragon-slayer875, @hamza-mohd, @jameshorton2337, @leecalcote, @sangramrath, @singh1203, @vishalvivekm and l5io
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: proxy-vars.md

title: Proxy Friendly Operators linkTitle: Proxy Vars weight: 20 Proxy-friendly Operators should inspect their environment for the standard proxy variables (`HTTPSPROXY`, `HTTPPROXY`, and `NO_PROXY`) and pass the values to Operands. This can be accomplished by modifying the `watches.yaml` to include the overrides based on an environment variable: ```yaml group: demo.example.com version: v1alpha1 kind: Nginx chart: helm-charts/nginx overrideValues: proxy.http: $HTTP_PROXY ``` Note: This example assumes that `proxy.http` is included in your chart's `Values.yaml`. The nginx tutorial does not have this value, but you can add to the `helmcharts/nginx/Values.yaml`: ```yaml proxy: http: "" https: "" no_proxy: "" ``` You will also need to make sure the chart template supports the usage of these values. Using the nginx tutorial, edit `helm-charts/nginx/templates/deployment.yaml` ```yaml containers: name: {{ .Chart.Name }} securityContext: {{- toYaml .Values.securityContext | nindent 12 }} image: "{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}" imagePullPolicy: {{ .Values.image.pullPolicy }} env: name: http_proxy value: "{{ .Values.proxy.http }}" ``` You can set the environment variable on the Operator deployment. Using the nginx tutorial, edit `config/manager/manager.yaml`: ```yaml containers: args: --leader-elect --leader-election-id=helm-proxy-demo image: controller:latest name: manager env: name: "HTTP_PROXY" value: "httpproxytest" ```
Project: BigchainDB (App Definition and Development / Database)
File: node-requirements.md

<! Copyright 2020 Interplanetary Database Association e.V., BigchainDB and IPDB software contributors. SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0) Code is Apache-2.0 and docs are CC-BY-4.0 > This page is about the requirements of BigchainDB Server. You can find the requirements of MongoDB, Tendermint and other in the documentation for that software. BigchainDB Server requires Python 3.5+ and Python 3.5+ , but we recommend using an LTS version of or a similarly server-grade Linux distribution. Don't use macOS (formerly OS X, formerly Mac OS X), because it's not a server-grade operating system. Also, BigchainDB Server uses the Python multiprocessing package and . BigchainDB Server runs many concurrent processes, so more RAM and more CPU cores is better. As mentioned on the page about , every machine running BigchainDB Server should be running an NTP daemon.
Project: ClickHouse (App Definition and Development / Database)
File: v23.3.15.29-lts.md

sidebar_position: 1 sidebar_label: 2023 Backported in : If the database is already initialized, it doesn't need to be initialized again upon subsequent launches. This can potentially fix the issue of infinite container restarts when the database fails to load within 1000 attempts (relevant for very large databases and multi-node setups). (). Backported in : Fix integration check python script to use gh api url - Add Readme for CI tests. (). Backported in : Check sha512 for tgz; use a proper repository for keeper; write only filenames to TGZ.sha512 files for tarball packages. Prerequisite for . (). Fix bug with inability to drop detached partition in replicated merge tree on top of S3 without zero copy (). Fix crash in QueryNormalizer with cyclic aliases (). Fix window functions in case of sparse columns. (). NO CL ENTRY: 'Pin rust version to fix GLIBC compatibility check'. (). Fix incorrect createColumn call on join clause (). Use `--filter` to reduce checkout time (). Improve enrich image (). One final leftover in diff_urls of PRInfo ().
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 19_io_pubsub.md

Prompt: Is Pub/Sub supported in Apache Beam? Response: is a service that provides a simple, reliable, scalable, and secure real-time messaging service for sending and receiving messages between independent applications. Apache Beam provides a PubSubIO connector that allows you to read and write messages from and to Pub/Sub. Pub/Sub is currently supported only in streaming pipelines. Pub/Sub is supported in the following Beam SDKs: (through X Language) To get started with Pub/Sub and Apache Beam, refer to the . The repository provides Python code examples that and data from and to Pub/Sub. Here is an example of the Apache Beam pipeline code for reading data from a Pub/Sub topic and writing it to another topic: ```python from apache_beam.io import ReadFromPubSub from apache_beam.io import WriteToPubSub with beam.Pipeline(options=options) as p: (p | "Read from Pub/Sub" >> ReadFromPubSub(topic="input_topic") | "Write to Pub/Sub" >> WriteToPubSub(topic="output_topic")) ```
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: sup_launcher.md

+++ title = "Launcher" description = "Launcher" gh_repo = "habitat" [menu] [menu.habitat] title = "Launcher" identifier = "habitat/supervisors/sup-launcher Supervisor Launcher Sidecar Process" parent = "habitat/supervisors" weight = 110 +++ Chef Habitat's Launcher is a sidecar process for the Supervisor which provides a mechanism for launching processes on behalf of the Supervisor. It is the entry point for running the Supervisor and is the Supervisor for the Supervisor. Whereas the Supervisor is able to automatically update itself, the Launcher is currently released a bit differently, by design; it should be rare that the Launcher ever needs to change. To update your Launchers, run: ```bash hab pkg install core/hab-launcher ``` Then restart the Supervisor. This will, by necessity, require a restart of supervised services, so factor that into your planning. The Launcher is designed to run as process 1; it is minimal by design. Its responsibilities are simply to be the parent process for the Supervisor. The Launcher enables the Supervisor to update itself without shutting down or re-parenting the services that the Supervisor is supervising. The Launcher is versioned separately from the Supervisor and should be updated very infrequently since an update of the Launcher could require a system restart if it is running as process 1.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 22_io_spanner.md

Prompt: Is Cloud Spanner supported in Apache Beam? Response: is a service that provides a fully managed, mission-critical, relational database service that offers transactional consistency at global scale, schemas, SQL (ANSI 2011 with extensions), and automatic, synchronous replication for high availability. Apache Beam has a built-in SpannerIO connector for Cloud Spanner that enables Apache Beam pipelines to read data from and write data to Cloud Spanner. Cloud Spanner is supported in both batch pipelines and streaming pipelines and can serve both as a source and a sink. For more information, see the SpannerIO connector documentation: To get started with Cloud Spanner and Apache Beam, refer to the . Here is an example of Apache Beam pipeline code for reading data from a Cloud Spanner table using an SQL query: ```python class ExampleRow(NamedTuple): id: int name: str with beam.Pipeline(options=options) as p: output = (p | "Read from table" >> ReadFromSpanner( projectid=options.projectid, instanceid=options.instanceid, databaseid=options.databaseid, row_type=ExampleRow, sql="SELECT * FROM example_row" ) | "Map Data" >> Map(lambda row: f"Id = {row.id}, Name = {row.name}") | "Log Data" >> Map(logging.info)) ```
Project: ClickHouse (App Definition and Development / Database)
File: constraint.md

slug: /en/sql-reference/statements/alter/constraint sidebar_position: 43 sidebar_label: CONSTRAINT Constraints could be added or deleted using following syntax: ``` sql ALTER TABLE [db].name [ON CLUSTER cluster] ADD CONSTRAINT constraint_name CHECK expression; ALTER TABLE [db].name [ON CLUSTER cluster] DROP CONSTRAINT constraint_name; ``` See more on . Queries will add or remove metadata about constraints from table, so they are processed immediately. :::tip Constraint check will not be executed on existing data if it was added. ::: All changes on replicated tables are broadcasted to ZooKeeper and will be applied on other replicas as well.
Project: Timescale (App Definition and Development / Database)
File: pull_request_template.md

updates updates Fixes #<issue number>. Cut everything below the above line. Checklist for a pull request: Try to follow [the seven rules of a great Git commit message](https://chris.beams.io/posts/git-commit/). Ideally, the PR should be merged as a single commit. Rebase on latest main code. Reference the issue(s) resolved with Fixes #<issue number>, or Closes #<issue number>. Make sure the PR has appropriate CHANGELOG updates, including thanks to people that reported issues. Include appropriate documentation changes. Two approvals are necessary to merge. Separate subject from body with a blank line Limit the subject line to 50 characters Capitalize the subject line Do not end the subject line with a period Use the imperative mood in the subject line Wrap the body at 72 characters Use the body to explain what and why vs. how The simplify reviewing and to protect against accidental merges of work-in-progress commits, the CI system enforces that a PR is merged as a single commit. However, sometimes a multi-commit PR is warranted if each commit is a distinct change that makes sense to submit in the same PR. The single-commit enforcement can be disabled by adding the following trailer to the PR description (note that the trailer should not be in the commit message): Disable-check: commit-count Generally, though, small single-commit PRs are preferred over large multi-commit PRs so that PRs are easier to review. It is also good to avoid multiple commits that have unrelated changes or a lot of work-in-progress changes that are not appropriate for a well-formatted commit log. If the code change adds a new feature, limitation, or change in behavior, the PR might need to include documentation or a separate follow-up PR to the .
Project: KubeEdge (Provisioning / Automation & Configuration)
File: LICENSE.md

The MIT License (MIT) Copyright (c) 2014 Mitchell Hashimoto Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Project: YDB (App Definition and Development / Database)
File: coalesce.md

Iterates through the arguments from left to right and returns the first non-empty argument found. To be sure that the result is non-empty (not of an ), the rightmost argument must be of this type (often a literal is used for this). With a single argument, returns this argument unchanged. Lets you pass potentially empty values to functions that can't handle them by themselves. A short format using the low-priority `??` operator is available (lower than the Boolean operations). You can use the `NVL` alias. Examples ```yql SELECT COALESCE( maybeemptycolumn, "it's empty!" ) FROM my_table; ``` ```yql SELECT maybeemptycolumn ?? "it's empty!" FROM my_table; ``` ```yql SELECT NVL( maybeemptycolumn, "it's empty!" ) FROM my_table; ``` <span style="color: gray;">(all three examples above are equivalent)</span>
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: notifications.md

Notifications are how Lagoon informs users about what's going on with their projects. There are several types of notifications: Slack RocketChat Email Webhook Microsoft Teams A project can have one or more notifications. Organizations have a notification quota for all of their projects. Notifications are created independently of projects, and can then be assigned to one or more projects. . .
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_alter_sequence.md

title: ALTER SEQUENCE statement [YSQL] headerTitle: ALTER SEQUENCE linkTitle: ALTER SEQUENCE description: Use the ALTER SEQUENCE statement to change the definition of a sequence in the current schema. menu: v2.18: identifier: ddlaltersequence parent: statements type: docs Use the `ALTER SEQUENCE` statement to change the definition of a sequence in the current schema. {{%ebnf%}} alter_sequence, altersequenceoptions {{%/ebnf%}} Specify the name of the sequence (sequence_name). An error is raised if a sequence with that name does not exists in the current schema and `IF EXISTS` is not specified. Changes the data type of a sequence. This automatically changes the minimum and maximum values of the sequence if the previous values were beyond what the new type allows. Valid types are `smallint`, `integer`, and `bigint`. Specify the difference between consecutive values in the sequence. Default is `1`. Specify the minimum value allowed in the sequence. If this value is reached (in a sequence with a negative increment), `nextval()` will return an error. If `NO MINVALUE` is specified, the default value will be used. Default is 1. Specify the maximum value allowed in the sequence. If this value is reached, `nextval()` will return an error. If `NO MAXVALUE` is specified, the default will be used. Default is `2-1`. Specify the first value in the sequence. `start` cannot be less than `minvalue`. Default is `1`. Change the current value of the sequence. If no value is specified, the current value will be set to the last value specified with `START [ WITH ]` when the sequence was created or altered. Specify how many numbers from the sequence to cache in the client. Default is `1`. When YB-TServer configuration flag is not explicitly turned off (set to `0`), the maximum value of the flag and the cache clause will be used. It gives ownership of the sequence to the specified column (if any). This means that if the column (or the table to which it belongs to) is dropped, the sequence will be automatically dropped. If `NONE` is specified, any previous ownership will be deleted. Create a simple sequence. ```plpgsql yugabyte=# CREATE SEQUENCE s; ``` ``` CEATE SEQUENCE ``` Modify the increment value. ```plpgsql yugabyte=# ALTER SEQUENCE s INCREMENT BY 5; ``` ``` ALTER SEQUENCE ``` ```plpgsql yugabyte=# SELECT nextval('s'); ``` ``` nextval 1 (1 row) ``` ```plpgsql yugabyte=# SELECT nextval('s'); ``` ``` nextval 6 (1 row) ``` Modify the starting value. ```plpgsql yugabyte=# ALTER SEQUENCE s RESTART WITH 2; ``` ``` ALTER SEQUENCE ``` ```plpgsql yugabyte=# SELECT nextval('s'); ``` ``` nextval 2 (1 row) ``` ```plpgsql yugabyte=# SELECT nextval('s'); ``` ``` nextval 7 (1 row) ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.133.md

layout: release date: 2023-09-01 tag: v0.6.133 [Server] Fix meshery server bottleneck issues @MUzairS15 (#8622) Bump gopkg.in/yaml.v3 from 3.0.0-20210107192922-496545a6307b to 3.0.0 in /install/docker-extension @dependabot (#8616) Bump @babel/eslint-parser from 7.19.1 to 7.22.11 in /ui @dependabot (#8626) Bump @mui/icons-material from 5.14.3 to 5.14.7 in /provider-ui @dependabot (#8632) Bump eslint from 8.47.0 to 8.48.0 in /provider-ui @dependabot (#8633) Bump @babel/eslint-parser from 7.22.7 to 7.22.11 in /provider-ui @dependabot (#8635) fix: Fixed the misspelling in connections page @tushh-codes (#8621) Changed `CustomTableFooter` from class-based to functional component @Rajdip019 (#8610) Fixed type error and removed publish schema from Meshery UI @Yashsharma1911 (#8608) Moved CustomToolbarSelect.js from class-based component to functional component @Rajdip019 (#8582) Bump github.com/layer5io/meshsync from 0.6.11 to 0.6.14 @dependabot (#8628) Bump @babel/eslint-parser from 7.19.1 to 7.22.11 in /ui @dependabot (#8626) Bump @mui/icons-material from 5.14.3 to 5.14.7 in /provider-ui @dependabot (#8632) Bump eslint from 8.47.0 to 8.48.0 in /provider-ui @dependabot (#8633) Bump @babel/eslint-parser from 7.22.7 to 7.22.11 in /provider-ui @dependabot (#8635) Bump gonum.org/v1/gonum from 0.12.0 to 0.14.0 @dependabot (#8583) Prevent MeshMap from running on forked repo @VaibhavMalik4187 (#8598) Updated email-on-failure job @VaibhavMalik4187 (#8578) Kuma dark mode logo resolve @lanzkrish (#8596) Thank you to our contributors for making this release possible: @MUzairS15, @Rajdip019, @VaibhavMalik4187, @Yashsharma1911, @aabidsofi19, @dependabot, @dependabot[bot], @lanzkrish, @leecalcote and @tushh-codes
Project: YugabyteDB (App Definition and Development / Database)
File: shutdown.md

title: Shut down YugabyteDB Anywhere headerTitle: Shut down YugabyteDB Anywhere linkTitle: Shut down description: Shut YugabyteDB Anywhere down gracefully to perform maintenance. menu: v2.18_yugabyte-platform: identifier: shutdown parent: administer-yugabyte-platform weight: 60 type: docs If you need to perform maintenance on the server hosting your YugabyteDB Anywhere installation requiring a shutdown or restart, you should shut YugabyteDB Anywhere down gracefully. If you installed YugabyteDB Anywhere using , shut down using the following command: ```sh $ sudo yba-ctl stop ``` To restart the service, use the following command: ```sh $ sudo yba-ctl start ``` The service should automatically start up after a reboot. If you installed YugabyteDB Anywhere using Replicated, stop the application via the Replicated console. You can also use the following command: ```sh replicatedctl app stop ``` For Kubernetes, node patching doesn't require YBA coordination.
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-exp-relationship.md

layout: default title: mesheryctl-exp-relationship permalink: reference/mesheryctl/exp/relationship redirect_from: reference/mesheryctl/exp/relationship/ type: reference display-title: "false" language: en command: exp subcommand: relationship View list of relationships and details of relationship Meshery uses relationships to define how interconnected components interact. View list of relationships and detailed information of a specific relationship <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp relationship [flags] </div> </pre> To view list of relationships <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp relationships list </div> </pre> To view a specific relationship <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp relationships view [model-name] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for relationship </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -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.