cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-channel.md

layout: default title: mesheryctl-system-channel permalink: reference/mesheryctl/system/channel redirect_from: reference/mesheryctl/system/channel/ type: reference display-title: "false" language: en command: system subcommand: channel Switch between release channels Subscribe to a release channel. Choose between either 'stable' or 'edge' channels. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system channel [flags] </div> </pre> Subscribe to release channel or version <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system channel </div> </pre> To set the channel <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system channel set [stable|stable-version|edge|edge-version] </div> </pre> To pin/set the channel to a specific version <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system channel set stable-v0.6.0 </div> </pre> To view release channel and version <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system channel view </div> </pre> To switch release channel and version <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system channel switch [stable|stable-version|edge|edge-version] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for channel </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -c, --context string (optional) temporarily change the current context. -v, --verbose verbose output -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: KICS (Provisioning / Security & Compliance)
File: 29b8224a-60e9-4011-8ac2-7916a659841f.md

title: Google Compute Network Using Default Firewall Rule hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 29b8224a-60e9-4011-8ac2-7916a659841f Query name: Google Compute Network Using Default Firewall Rule Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: Google Compute Network should not use default firewall rule<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" name: create a firewall2 google.cloud.gcpcomputefirewall: name: default allowed: ip_protocol: tcp ports: '22' state: present network: "{{ my_network2 }}" name: create a network2 google.cloud.gcpcomputenetwork: name: test_object2 autocreatesubnetworks: 'true' project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present register: my_network2 ``` ```yaml title="Negative test num. 1 - yaml file" name: create a firewall google.cloud.gcpcomputefirewall: name: test_object allowed: ip_protocol: tcp ports: '22' target_tags: test-ssh-server staging-ssh-server source_tags: test-ssh-clients project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present network: "{{ my_network }}" name: create a network google.cloud.gcpcomputenetwork: name: test_object autocreatesubnetworks: 'true' project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present register: my_network ```
Project: CyberArk Conjur (Provisioning / Key Management)
File: feature_flags.md

Feature flags enable partially completed or experimental features to be available in the official Conjur releases. has an excellent article outlining various approaches to leveraging feature flags. For our initial Feature Flag implementation only supports setting flags via environment variables. In the future, we should support feature flags through file-based as well. To create a new feature flag, add the feature name to the `feature_flags` hash in `config/initializers/feature_flags.rb`. Set the hash entry value to the default state for the feature flag. For example, to create a feature flag for a feature called `Telemetry Endpoint`, add the following: ```ruby feature_flags = { telemetry_endpoint: false } ``` and restart Conjur. After a new flag has been added to the `feature_flags` hash, the Telemetry Endpoint is now a valid feature flag. Functionality can be gated with the following: ```ruby if Rails.configuration.featureflags.enabled?(:telemetryendpoint) ... # Gated code here end ``` To enable the Telemetry Endpoint feature, set the feature environment variable flag: ```sh CONJURFEATURETELEMETRYENDPOINTENABLED=true ``` and restart Conjur to pick up the new flag setting.
Project: ClickHouse (App Definition and Development / Database)
File: settings_profile_elements.md

slug: /en/operations/system-tables/settingsprofileelements Describes the content of the settings profile: onstraints. Roles and users that the setting applies to. Parent settings profiles. Columns: `profile_name` (()) Setting profile name. `user_name` (()) User name. `role_name` (()) Role name. `index` () Sequential number of the settings profile element. `setting_name` (()) Setting name. `value` (()) Setting value. `min` (()) The minimum value of the setting. `NULL` if not set. `max` (()) The maximum value of the setting. NULL if not set. `writability` ((('WRITABLE' = 0, 'CONST' = 1, 'CHANGEABLEINREADONLY' = 2))) Sets the settings constraint writability kind. `inherit_profile` (()) A parent profile for this setting profile. `NULL` if not set. Setting profile will inherit all the settings' values and constraints (`min`, `max`, `readonly`) from its parent profiles.
Project: Scylla (App Definition and Development / Database)
File: logging.md

Scylla implements logging using Seastar's logging facilities. Each log message comes with a severity level increasing from "trace", to "debug", "info", "warn" and "error", and with a subsystem name. The developer can filter messages based on these levels and system name - for example ask to show a large number of "trace" messages for a subsystem he or she is currently debugging, while other subsystems will only display serious warnings or error messages. Log messages are sent to Scylla's standard output and/or to the system log, as specified by the `--log-to-stdout` and `--log-to-syslog` options. The default is to send log messages to stdout only, but Scylla is installed we override this default so that log messages are sent to the system log. When the output is to stdout, the `--logger-stdout-timestamps <type>` option can be used to control the addition of time stamps to log messages: The default type of "real" prints the current time in human-readable date form. The type "boot" prints the time as the (floating-point) number of seconds since the epoch of std::chrono::steady_clock. The type "none" does not add a timestamp to log messages. As in any Seastar application, one can control Scylla's log filtering on startup with various command-line options. By default, log messages with severity info or above (info, warn or error) are displayed and the rest are filtered out. This default filtering level can be adjusted with the "`--default-log-level <level>`" option. But more commonly, a developer wants to enable more detailed logging just for selected subsystems. This can be done with a "`--logger-log-level <subsystem>=<level>' option. For example, `--logger-log-level repair=debug` to enable log messages from the "repair" subsystem if their severity level is `debug` or higher. The command line option "--help-loggers" can be used to get a list of all known subsystems. While for short-running tests it is easy enough to set the log filtering at the beginning of the run, in longer-running scenarios it is often useful to change the log filtering during the run. In Scylla, we can do this through the REST API: To obtain the status of a particular logger: ``` $ curl -X GET http://127.0.0.1:10000/system/logger/<subsystem_name> ``` For example: ``` $ curl -X GET http://127.0.0.1:10000/system/logger/sstable ``` To change the status of a particular logger: ``` $ curl -X POST http://127.0.0.1:10000/system/logger/sstable?level=trace ``` As mentioned above, valid levels are: trace, debug, info, warn, error. If your setup properly supports `nodetool` (i.e., `scylla-jmx` is running) you can also use a `nodetool` command instead of the aforementioned direct REST API requests. E.g.: `nodetool setlogginglevel sstable trace`.
Project: StarRocks (App Definition and Development / Database)
File: CREATE_FILE.md

displayed_sidebar: "English" You can execute the CREATE FILE statement to create a file. After a file is created, the file is uploaded and persisted in StarRocks. In a database, only an admin user can create and delete files, and all users who have permission to access the database can use the files that belong to the database. :::tip This operation requires the SYSTEM-level FILE privilege. You can follow the instructions in to grant this privilege. ::: File: refers to the file that is created and saved in StarRocks. After a file is created and stored in StarRocks, StarRocks assigns a unique ID to the file. You can find a file based on the database name, catalog, and file name. ```SQL CREATE FILE "file_name" [IN database] [properties] ``` | Parameter | Required | Description | | - | | | | file_name | Yes | The name of the file. | | database | No | The database to which the file belongs. If you do not specify this parameter, this parameter defaults to the name of the database that you access in the current session. | | properties | Yes | The properties of the file. The following table describes the configuration items of properties. | Configuration items of `properties` | Configuration item | Required | Description | | - | | | | url | Yes | The URL from which you can download the file. Only an unauthenticated HTTP URL is supported. After the file is stored in StarRocks, the URL is no longer needed. | | catalog | Yes | The category to which the file belongs. You can specify a catalog based on your business requirements. However, in some situations, you must set this parameter to a specific catalog. For example, if you load data from Kafka, StarRocks searches for files in the catalog from the Kafka data source. | | MD5 | No | The message-digest algorithm that is used to check a file. If you specify this parameter, StarRocks checks the file after the file is downloaded. | Create a file named test.pem under the category named kafka. ```SQL CREATE FILE "test.pem" PROPERTIES ( "url" = "https://starrocks-public.oss-cn-xxxx.aliyuncs.com/key/test.pem", "catalog" = "kafka" ); ``` Create a file named client.key under the category named my_catalog. ```SQL CREATE FILE "client.key" IN my_database PROPERTIES ( "url" = "http://test.bj.bcebos.com/kafka-key/client.key", "catalog" = "my_catalog", "md5" = "b5bb901bf10f99205b39a46ac3557dd9" ); ```
Project: YugabyteDB (App Definition and Development / Database)
File: yba_universe_node_list.md

List YugabyteDB Anywhere universe nodes List YugabyteDB Anywhere universe nodes ``` yba universe node list [flags] ``` ``` -h, --help help for list ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Required] The name of the universe for the corresponding node operations. --node-name string [Optional] The name of the universe node for the corresponding node operations. Required for add, reboot, release, remove, reprovision, start, stop. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage YugabyteDB Anywhere universe nodes
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: memory-reservation.md

Memory soft limit. A unit can be b (bytes), k (kibibytes), m (mebibytes), or g (gibibytes). After setting memory reservation, when the system detects memory contention or low memory, containers are forced to restrict their consumption to their reservation. So always set the value below --memory, otherwise the hard limit takes precedence. By default, memory reservation is the same as memory limit. This option is not supported on cgroups V1 rootless systems.
Project: ShardingSphere (App Definition and Development / Database)
File: base-transaction-seata.en.md

+++ title = "Seata BASE transaction" weight = 2 +++ When integrating Seata AT transaction, we need to integrate TM, RM and TC component into ShardingSphere transaction manager. Seata have proxied `DataSource` interface in order to RPC with TC. Similarly, Apache ShardingSphere faced to `DataSource` interface to aggregate data sources too. After Seata `DataSource` encapsulation, it is easy to put Seata AT transaction into Apache ShardingSphere sharding ecosystem. When an application containing `ShardingSphereTransactionBaseSeataAT` startup, the user-configured DataSource will be wrapped into seata `DataSourceProxy` through `seata.conf`, then registered into RM. TM controls the boundaries of global transactions. TM obtains the global transaction ID by sending Begin instructions to TC. All branch transactions participate in the global transaction through this global transaction ID. The context of the global transaction ID will be stored in the thread local variable. Actual SQL in Seata global transaction will be intercepted to generate undo snapshots by RM and sends participate instructions to TC to join global transaction. Since actual sharding SQLs executed in multi-threads, global transaction context should transfer from main thread to child thread, which is exactly the same as context transfer between services. When submitting a seata transaction, TM sends TC the commit and rollback instructions of the global transaction. TC coordinates all branch transactions for commit and rollback according to the global transaction ID.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.20.md

RabbitMQ `3.9.20` is a maintenance release in the `3.9.x` release series. Please refer to the Upgrading to 3.9 section from if upgrading from a version prior to 3.9.0. This release requires at least Erlang 23.2, and supports Erlang 24. has more details on Erlang version requirements for RabbitMQ. Release notes can be found on GitHub at . RabbitMQ Debian package now lists Erlang 25.0 as supported. None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.20.tar.xz` instead of the source tarball produced by GitHub.
Project: CloudEvents (App Definition and Development / Streaming & Messaging)
File: languages.md

<!-- no verify-links --> CloudEvents is a specification for describing event data in common formats. As a textual specification, language barriers MAY slow down the progress of understanding CloudEvents for some people. Thus, we welcome anyone to the CloudEvents specification into different languages. This document acknowledges those who contribute whether by reviewing translation works or translating English documents. Thanks for everything you did to spread CloudEvents. Reviewers Jie Ding - Translators Jie Ding -
Project: KubeLinter (Provisioning / Security & Compliance)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: "[BUG]" labels: '' assignees: '' System info: OS: [e.g. Linux? MaxOS? Windows?] Describe the bug A clear and concise description of the bug. To Reproduce Steps to reproduce the behavior: Sample YAML input If applicable, sample YAML input which reproduces the issue. Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here.
Project: Stolon (App Definition and Development / Database)
File: pitr.md

Stolon can do a point a time recovery starting from an existing backup. example shows how to do point in time recovery with stolon using example shows how to do point in time recovery with stolon using stolon doesn't trigger base backups, you can run them at your preferred times and with your preferred scheduler. With stolon you should instead enable `archivemode` and set the `archivecommand`, there's nothing different than a typical . ``` stolonctl update --patch '{ "pgParameters" : { "archivemode": "on", "archivecommand": "/path/to/your/archive/command %p" } }' ``` `archivemode` and the related `archivecommand` will be enabled for all the instances (master and standbys). This is done to avoid losing some wals to backup when the current master keeper is down and a new master is elected. We suggest to define your archive command script to avoid backing up the same wal from all the instances (for example doing this only when the instance is the stolon master and just removing the wal when the instance is a stolon standby). To trigger a point in time recovery the cluster has to be (re)initialized using the `pitr` initMode in the cluster specification and setting in the `pitrConfig` the `dataRestoreCommand` and the archive `restoreCommand`. The `dataRestoreCommand` should containt the local shell command to execute to restore the full backup. Any `%d` in the string is replaced by the full path to the data directory. The command should return a 0 exit status if (and only if) it succeeds. The archive `restoreCommand` will be used as is in the generated `recovery.conf` file. For its value see the related ``` stolonctl init '{ "initMode": "pitr", "pitrConfig": { "dataRestoreCommand": "/path/to/your/backup/restore/command \"%d\"" , "archiveRecoverySettings": { "restoreCommand": "/path/to/your/archive/restore/command \"%f\" \"%p\"" } } }' ``` Note: the `\"` is needed by json to put double quotes inside strings. We aren't using single quotes since they are just used to pass to the shell the full json as a single argument. When initializing a cluster in pitr init mode a random registered keeper will be choosed and it'll start restoring the database with these steps: Remove the current data directory Call the `dataRestoreCommand` expanding every %d to the data directory full path. If it exits with a non zero exit code then stop here since something went wrong. Create a `recovery.conf` with the right parameters and with `restore_command` set to `restoreCommand`. Start the postgres instance and wait for the archive recovery. If something goes wrong you can see the errors in the keeper's logs or in postgresql log (if these are related to the archive restore step) and you can retrigger a new pitr reinitializing the cluster.
Project: ArangoDB (App Definition and Development / Database)
File: co_tryv2_failure_likely.md

+++ title = "`BOOSTOUTCOMECOTRYV2FAILURE_LIKELY(spec, expr)`" description = "Evaluate an expression which results in an understood type, continuing execution if successful, immediately returning `tryoperationreturn_as(X)` from the calling function if unsuccessful." +++ Evaluate an expression which results in a type matching the following customisation points, continuing execution if successful, immediately returning {{% api "tryoperationreturn_as(X)" %}} from the calling function if unsuccessful: `BOOSTOUTCOMEV2NAMESPACE::`{{% api "tryoperationhasvalue(X)" %}} `BOOSTOUTCOMEV2NAMESPACE::`{{% api "tryoperationreturnas(X)" %}} `BOOSTOUTCOMEV2NAMESPACE::`{{% api "tryoperationextractvalue(X)" %}} Default overloads for these customisation points are provided. See . Hints are given to the compiler that the expression will be unsuccessful. If you expect success, you should use {{% api "BOOSTOUTCOMETRYV(expr)" %}} instead. Overridable: Not overridable. Definition: Firstly the expression's temporary is bound to a uniquely named, stack allocated, `spec`. If that reference's bound object's `tryoperationhasvalue()` is false, immediately execute `return tryoperationreturnas(propagated unique reference);`, propagating the rvalue/lvalue/etc-ness of the original expression. Header: `<boost/outcome/try.hpp>`
Project: Distribution (Provisioning / Container Registry)
File: CHANGES.md

v2:* add GoVersion package variable () () v2:* handle space in non-devel go version () () update dependencies () () v2:* drop cloud lro test dep () (), refs apierror:* add method to return HTTP status code conditionally () (), refs add ref to usage with clients () (), refs v2:* add WithTimeout option () () v2/apierror:* return Unknown GRPCStatus when err source is HTTP () (), refs update google.golang.org/api to latest () () v2/apierror:* add apierror.FromWrappingError () () v2:* copy DetermineContentType functionality () () v2:* resolve bad genproto pseudoversion in go.mod () () add ExtractProtoMessage to apierror () () v2:* add OnHTTPCodes CallOption () () v2/apierror:* use errors.As in FromError () () v2:* bump release-please processing () ()
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: v1.7.1.md

title: v1.7.1 weight: 998992999 The scaffolded `--config` flag was not added to either ansible-/helm-operator binary when support was originally added, so does not currently work. The `--config` flag supports configuration of both binaries by file; this method of configuration only applies to the underlying , not the operator as a whole. To optionally configure the operator's Deployment with a config file, make the following update to config/default/kustomization.yaml: ```diff \- managerauthproxy_patch.yaml +# Mount the controller config file for loading manager configurations +# through a ComponentConfig type +- managerconfigpatch.yaml ``` This feature is opt-in: flags can be used as-is or to override config file values. See for more details. The operator-framework is removing support for the packagemanifests format in the near future. Hence, `operator-sdk generate packagemanifests` and `operator-sdk run packagemanifests` commands are deprecated. In order to migrate packagemanifests to bundles, `operator-sdk pkgman-to-bundle` command can be used. Run `operator-sdk pkgman-to-bundle --help` for more details. See for more details. Make the following changes to config/rbac/leaderelectionrole.yaml: ```diff rules: \- apiGroups: "" - coordination.k8s.io resources: configmaps verbs: +- get +- list +- watch +- create +- update +- patch +- delete +- apiGroups: +- coordination.k8s.io resources: leases verbs: get ``` See for more details. Importing `setup-envtest.sh` needs bash, so your Makefile's `SHELL` variable should be set to `bash` with error options: ```diff else GOBIN=$(shell go env GOBIN) endif +# Setting SHELL to bash allows bash commands to be executed by recipes. +# This is a requirement for 'setup-envtest.sh' in the test target. +# Options are set to exit when a recipe line exits non-zero or a piped command fails. +SHELL = /usr/bin/env bash -o pipefail +.SHELLFLAGS = -ec all: build ``` See for more details. For Ansible-based operators, on cluster-scoped dependent resources and dependent resources in other namespaces were not applied correctly. A workaround was to add these annotations manually, which is no longer required as this bug has been fixed. See for more details. In your go.mod, change controller-runtime's version to v0.8.3 and kubernetes dependencies to v0.20.2, then rebuild your project. See for more details.