cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: linux-mac.md

layout: default title: Install Meshery CLI on Linux or Mac permalink: installation/linux-mac type: installation category: mesheryctl redirect_from: installation/platforms/linux-mac display-title: "false" language: en list: include image: /assets/img/platforms/linux_mac.png abstract: Install Meshery CLI on Linux or Mac To set up and run Meshery on Linux or macOS, you will need to install `mesheryctl`. `mesheryctl` is the command line interface (CLI) for Meshery. It is used to install, manage, and operate one or more Meshery deployments. `mesheryctl` can be installed via `bash` is also available or through or . {% include mesheryctl/installation-brew.md %} {% include mesheryctl/installation-bash.md %} Guides to using Meshery's various features and components. {% assign sorted_guides = site.pages | sort: "name" %} <ul> {% for item in sorted_guides %} {% if item.type=="guides" and item.category=="mesheryctl" and item.list!="exclude" and item.language=="en" -%} <li><a href="{{ site.baseurl }}{{ item.url }}">{{ item.title }}</a> </li> {% endif %} {% endfor %} <li><a href="{{ site.baseurl }}/guides/upgrade#upgrading-meshery-cli">Upgrading Meshery CLI</a></li> </ul> {% include related-discussions.html tag="mesheryctl" %} {:toc} <!-- You can either use Bash or Brew to install <a href="/guides/mesheryctl">mesheryctl</a> ( Meshery command line interface ). To run Meshery, execute the following command. <pre class="codeblock-pre"><div class="codeblock"> <div class="clipboardjs">mesheryctl system start</div></div> </pre> Meshery server supports customizing authentication flow callback URL, which can be configured in the following way <pre class="codeblock-pre"><div class="codeblock"> <div class="clipboardjs"> $ MESHERYSERVERCALLBACK_URL=https://custom-host mesheryctl system start </div></div> </pre> -->
Project: Meshery (Provisioning / Automation & Configuration)
File: fluentd-operator.md

layout: integration title: Fluentd Operator subtitle: Collaborative and visual infrastructure as code for Fluentd Operator image: /assets/img/integrations/fluentd-operator/icons/color/fluentd-operator-color.svg permalink: extensibility/integrations/fluentd-operator docURL: https://docs.meshery.io/extensibility/integrations/fluentd-operator description: integrations-category: Observability and Analysis integrations-subcategory: Logging registrant: Artifact Hub components: name: fluentd-config colorIcon: assets/img/integrations/fluentd-operator/components/fluentd-config/icons/color/fluentd-config-color.svg whiteIcon: assets/img/integrations/fluentd-operator/components/fluentd-config/icons/white/fluentd-config-white.svg description: featureList: [ "Fluent Operator provides great flexibility in building a logging layer based on Fluent Bit and Fluentd.", "Fluentd Management: Deploy and destroy Fluentd StatefulSet automatically.", "Custom Configuration: Select input/filter/output plugins via labels." ] howItWorks: "Fluent Bit will be deployed as a DaemonSet while Fluentd will be deployed as a StatefulSet. " howItWorksDetails: "Although both Fluent Bit and Fluentd can collect, process(parse and filter) and then forward log to the final destinations, still they have strengths in different aspects. Fluent Bit is a good choice as a logging agent because of its lightweight and efficiency, while Fluentd is more powerful to perform advanced processing on logs because of its rich plugins. Fluent Bit only mode: If you just need to collect logs and send logs to the final destinations, all you need is Fluent Bit. Fluent Bit + Fluentd mode: If you also need to perform some advanced processing on the logs collected or send to more sinks, then you also need Fluentd. Fluentd only mode: If you need to receive logs through networks like HTTP or Syslog and then process and send the log to the final sinks, you only need Fluentd. Fluent Operator includes CRDs and controllers for both Fluent Bit and Fluentd which allows you to config your log processing pipelines in the 3 modes mentioned above as you wish." language: en list: include type: extensibility category: integrations
Project: ShardingSphere (App Definition and Development / Database)
File: metadata-repository.en.md

+++ title = "Metadata Repository" weight = 1 +++ Apache ShardingSphere provides different metadata persistence methods for different running modes. Users can freely choose the most appropriate way to store metadata while configuring the running mode. Type: JDBC Mode: Standalone Attributes: | Name | Type | Description | Default Value | |-|--||-| | provider | String | Type for metadata persist, the optional value is H2, MySQL | H2 | | jdbcurl | String | JDBC URL | jdbc:h2:mem:config;DBCLOSEDELAY=-1;DATABASETO_UPPER=false;MODE=MYSQL | | username | String | username | sa | | password | String | password | | Type: ZooKeeper Mode: Cluster Attributes: | Name | Type | Description | Default Value | ||--|--|--| | retryIntervalMilliseconds | int | Milliseconds of retry interval | 500 | | maxRetries | int | Max retries of client connection | 3 | | timeToLiveSeconds | int | Seconds of ephemeral data live | 60 | | operationTimeoutMilliseconds | int | Milliseconds of operation timeout | 500 | | digest | String | Password of login | | Type: Etcd Mode: Cluster Attributes: | Name | Type | Description | Default Value | |-|--|--|--| | timeToLiveSeconds | long | Seconds of ephemeral data live | 30 | | connectionTimeout | long | Seconds of connection timeout | 30 | Configure running mode in global.yaml. Configure metadata persistence warehouse type. Standalone mode configuration method. ```yaml mode: type: Standalone repository: type: JDBC props: provider: H2 jdbcurl: jdbc:h2:mem:config;DBCLOSEDELAY=-1;DATABASETO_UPPER=false;MODE=MYSQL username: test password: Test@123 ``` Cluster mode. ```yaml mode: type: Cluster repository: type: zookeeper props: namespace: governance_ds server-lists: localhost:2181 retryIntervalMilliseconds: 500 timeToLiveSeconds: 60 maxRetries: 3 operationTimeoutMilliseconds: 500 ```
Project: Salt Project (Provisioning / Automation & Configuration)
File: 3006.7.md

(release-3006.7)= <! Do not edit this file. This is auto generated. Edit the templates in doc/topics/releases/templates/ for a given release. --> <!-- Add release specific details below --> <!-- Do not edit the changelog below. This is auto generated. --> Deprecate and stop using ``salt.features`` Change module search path priority, so Salt extensions can be overridden by syncable modules and moduledirs. You can switch back to the old logic by setting features.enabledeprecatedmodulesearchpathpriority to true, but it will be removed in Salt 3008. Fix an issue with mac_shadow that was causing a command execution error when retrieving values that were not yet set. For example, retrieving last login before the user had logged in. Fixed an issue when keys didn't match because of line endings Corrected encoding of credentials for use with Artifactory Use `send_multipart` instead of `send` when sending multipart message. Fix an issue where the minion would crash on Windows if some of the grains failed to resolve Fix issue with openscap when the error was outside the expected scope. It now returns failed with the error code and the error Upgrade relenv to 0.15.0 to fix namespaced packages installed by salt-pip Fix regression of fileclient re-use when rendering sls pillars and states Fixes the s3fs backend computing the local cache's files with the wrong hash type Fixed Salt-SSH pillar rendering and state rendering with nested SSH calls when called via saltutil.cmd or in an orchestration Fix boto execution module loading Removed PR 65185 changes since incomplete solution catch only ret/ events not all returning events. Fix nonsensical time in fileclient timeout error. Fixes an issue when reading/modifying ini files that contain unicode characters added https proxy to the list of proxies so that requests knows what to do with https based proxies Ensure minion channels are closed on any master connection error. Fixed issue where Salt can't find libcrypto when pip installed from a cloned repo Fix RPM package systemd scriptlets to make RPM packages more universal Fixed an issue where fileclient requests during Pillar rendering cause fileserver backends to be needlessly refreshed. Fix exceptions being set on futures that are already done in ZeroMQ transport Use hmac compare_digest method in hashutil module to mitigate potential timing attacks Fix request channel default timeout regression. In 3006.5 it was changed from 60 to 30 and is now set back to 60 by default. Upgrade relenv to 0.15.1 to fix debugpy support. Bump to ``cryptography==42.0.0`` due to https://github.com/advisories/GHSA-3ww4-gg4f-jr7f In the process, we were also required to update to ``pyOpenSSL==24.0.0`` Bump to `cryptography==42.0.3` due to https://github.com/advisories/GHSA-3ww4-gg4f-jr7f
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_backuprepo_list.md

title: kbcli backuprepo list List Backup Repositories. ``` kbcli backuprepo list [flags] ``` ``` kbcli backuprepo list ``` ``` -A, --all-namespaces If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace. -h, --help help for list -o, --output format prints the output in the specified format. Allowed values: table, json, yaml, wide (default table) -l, --selector string Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. --show-labels When printing, show all labels as the last column (default hide labels column) ``` ``` --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: Meshery (Provisioning / Automation & Configuration)
File: v0.6.28.md

layout: release date: 2022-11-16 tag: v0.6.28 language: en Bump loader-utils from 1.4.1 to 1.4.2 in /install/docker-extension/ui @dependabot (#6539) Add Mutation in pattern engine @Revolyssup (#6366) fix panic @Revolyssup (#6541) Publish feature in UI for Catalog @harkiratsm (#6478) [playground] Enable wss connection in remote playground server @Abhishek-kumar09 (#6538) [Docs] Consolidated Compatibility Matrix on Supported Platforms page @asubedy (#6509) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @MUzairS15, @Revolyssup, @asubedy, @dependabot, @dependabot[bot], @harkiratsm, @l5io, @leecalcote and l5io
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_plugin_kubectl.KubeContext.md

/ / KubeContext .KubeContext Kubernetes context `KubeContext` apiVersion: `"github.com/kui-shell/plugin-kubectl/v1alpha1"` KubeResource.apiVersion `Optional` content: `void` KubeResource.content packages/core/mdist/models/entity.d.ts:50 `Optional` contentType: `string` KubeResource.contentType packages/core/mdist/models/entity.d.ts:51 isKubeResource: `true` KubeResource.isKubeResource `Optional` isSimulacrum: `boolean` KubeResource.isSimulacrum kind: `"Context"` KubeResource.kind `Optional` kuiRawData: `string` KubeResource.kuiRawData `Optional` metadata: { `creationTimestamp?`: `string` ; `generation?`: `string` ; `labels?`: `Record`<`string`, `string`\> ; `name`: `string` ; `namespace?`: `string` } & `Partial`<`WithOwnerReferences`\> & `Partial`<`WithResourceVersion`\> & { `annotations?`: `object` ; `creationTimestamp?`: `string` ; `generateName?`: `string` ; `generation?`: `string` ; `labels?`: { [key: string]: `string`; } ; `name`: `string` ; `namespace?`: `string` ; `uid?`: `string` } KubeResource.metadata packages/core/mdist/models/entity.d.ts:23 `Optional` nameHash: `string` KubeResource.nameHash packages/core/mdist/models/entity.d.ts:42 `Optional` onclick: `Object` family of onclick handlers | Name | Type | | :-- | :- | | `kind?` | `string` | | `name?` | `string` | | `nameHash?` | `string` | | `namespace?` | `string` | KubeResource.onclick packages/core/mdist/models/entity.d.ts:44 originatingCommand: `EvaluatorArgs`<\> KubeResource.originatingCommand `Optional` presentation: `Presentation` KubeResource.presentation packages/core/mdist/models/entity.d.ts:53 `Optional` prettyName: `string` name hash, e.g. the hash part of auto-generated names, or an openwhisk activation id KubeResource.prettyName packages/core/mdist/models/entity.d.ts:41 spec: `Object` | Name | Type | | :- | :-- | | `cluster` | `string` | | `isCurrent` | `boolean` | | `user` | `string` | KubeResource.spec `Optional` status: KubeResource.status `Optional` toolbarText: `ToolbarText` KubeResource.toolbarText packages/core/mdist/models/entity.d.ts:52 `Optional` version: `string` optional designation of resource version KubeResource.version packages/core/mdist/models/entity.d.ts:39
Project: ArangoDB (App Definition and Development / Database)
File: try_failure_likely.md

+++ title = "`BOOSTOUTCOMETRYFAILURELIKELY(var, expr)`" description = "Evaluate an expression which results in an understood type, assigning `T` to a decl called `var` 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, assigning `T` to a decl called `var` 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 "BOOSTOUTCOMETRY(var, expr)" %}} instead. An internal temporary to hold the value of the expression is created, which generally invokes a copy/move. Overridable: Not overridable. Definition: See {{% api "BOOSTOUTCOMETRYV(expr)" %}} for most of the mechanics. If successful, `var` is initialised or assigned to the expression result's `.assume_value()` if available, else to its `.value()`. This binds a reference possibly to the `T` stored inside the bound result of the expression, but possibly also to a temporary emitted from the value observer function. Header: `<boost/outcome/try.hpp>` Legacy: Before Outcome v2.2, `var` was always declared as an automatic rvalue ref. You can use the backwards compatibility macro `OUTCOME21COTRY()` if wish to retain the old behaviour.
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.2.8.2.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Critical | Trash does not descent into child directories to check for permissions* Permissions are now checked when moving a file to Trash. | Major | Add ability to secure log servlet using proxy users* WARNING: No release note provided for this change. | Major | Decommissioning stuck because of failing recovery* Allow a block to complete if the number of replicas on live nodes, decommissioning nodes and nodes in maintenance mode satisfies minimum replication factor. The fix prevents block recovery failure if replica of last block is being decommissioned. Vice versa, the decommissioning will be stuck, waiting for the last block to be completed. In addition, file close() operation will not fail due to last block being decommissioned. | Minor | Rename ADLS credential properties* <!-- markdown --> Properties {{dfs.adls.}} are renamed {{fs.adl.*}} Property {{adl.dfs.enable.client.latency.tracker}} is renamed {{adl.enable.client.latency.tracker}} Old properties are still supported | Major | Set default ADLS access token provider type to ClientCredential* Switch the default ADLS access token provider type from Custom to ClientCredential. | Major | Display upgrade domain information in fsck* New fsck option "-upgradedomains" has been added to display upgrade domains of any block. | Blocker | GetContentSummary uses excessive amounts of memory* Reverted HDFS-10797 to fix a scalability regression brought by the commit. | Major | Disable setting tcp socket send/receive buffers for write pipelines* The size of the TCP socket buffers are no longer hardcoded by default. Instead the OS now will automatically tune the size for the buffer.
Project: Keycloak (Provisioning / Security & Compliance)
File: updating-server-config.md

If you need to make a change to the default keycloak-subsystem configuration that is packaged with our distributions, you will need to edit this file: https://github.com/keycloak/keycloak/blob/main/wildfly/server-subsystem/src/main/config/default-server-subsys-config.properties This file contains a single multi-line property containing the subsystem xml declaration. Maven filtering is used to read this property and inject it everywhere it needs to go. Editing this file will also take care of propagating it to the distributions like server-dist and demo-dist. Also, you need to create CLI commands for each change by editing this file: https://github.com/keycloak/keycloak/blob/main/wildfly/server-subsystem/src/main/resources/cli/default-keycloak-subsys-config.cli This CLI snippet is used in the scripts required by the overlay distribution. The changes you will likely make are when you need to add a new SPI, change an existing SPI, or add/change a provider within an SPI. All elements in an SPI declaration are optional, but a full SPI declaration looks like this: ````xml <spi name="example"> <default-provider>myprovider</default-provider> <provider name="myprovider" enabled="true"> <properties> <property name="key" value="value"/> </properties> </provider> <provider name="mypotherrovider" enabled="true"> <properties> <property name="key" value="value2"/> </properties> </provider> </spi> ```` Here we have two providers defined for the SPI `example`. The `default-provider` is listed as `myprovider`. However it is up to the SPI to decide how it will treat this setting. Some SPIs allow more than one provider and some do not. So `default-provider` can help the SPI to choose. Also notice that each provider defines its own set of configuration properties. The fact that both providers above have a property called `lockWaitTimeout` is just a coincidence. The type of each property value is interpreted by the provider. However, there is one exception. Consider the `jpa` provider for the `eventStore` API: ````xml <spi name="eventsStore"> <provider name="jpa" enabled="true"> <properties> <property name="exclude-events" value="[&quot;EVENT1&quot;,&quot;EVENT2&quot;]"/> </properties> </provider> </spi> ```` We see that the value begins and ends with square brackets. That means that the value will be passed to the provider as a list. In this example, the system will pass the provider a list with two element values `EVENT1` and `EVENT2`. To add more values to the list, just separate each list element with a comma. Unfortunately, you do need to escape the quotes surrounding each list element with `&quot;`.
Project: ClickHouse (App Definition and Development / Database)
File: v21.1.7.1-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : fix default_replica_path and default_replica_name values are useless on Replicated()MergeTree engine when the engine needs specify other parameters. (). Backported in : fix bug related to cast tuple to map. Closes . (). Backported in : Now mutations allowed only for table engines that support them (MergeTree family, Memory, MaterializedView). Other engines will report a more clear error. Fixes . (). Backported in : Fix crash in `EXPLAIN` for query with `UNION`. Fixes , . (). Backported in : Fix redundant reconnects to ZooKeeper and the possibility of two active sessions for a single clickhouse server. Both problems introduced in . (). Backported in : Now `ALTER MODIFY COLUMN` queries will correctly affect changes in partition key, skip indices, TTLs, and so on. Fixes . (). Backported in : Fix error `Bad cast from type ... to DB::ColumnLowCardinality` while inserting into table with `LowCardinality` column from `Values` format. Fixes . ().
Project: Beam (App Definition and Development / Streaming & Messaging)
File: dataflow-runner.md

title: "Flink Runner Roadmap" <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> This roadmap is in progress. In the meantime, here are available resources: - Issues: