cwielenb/CNCF-Dataset huggingface dataset:
Project: sigstore (Provisioning / Security & Compliance)
File: README.md

In order to use Azure KMS () with the sigstore project you need to have a few things setup in Azure first. The key creation will be handled in sigstore, however the Azure Key Vault and the required permission will have to be configured before. (not required, but used in below examples) Different commands require different Key Vault access policies. For more information check the official . An Azure KMS key must be provided in the following format: `azurekms://[Key Vault Name].vault.azure.net/[Key Name]` A specific key version can optionally be provided: `azurekms://[Key Vault Name].vault.azure.net/[Key Name]/[Key Version]` Required access policies (keys): `get`, `create` ```shell cosign generate-key-pair --kms azurekms://[Key Vault Name].vault.azure.net/[Key Name] ``` Required access policies (keys): `get`, `sign` ```shell az acr login --name [Container Registry Name] cosign sign --key azurekms://[Key Vault Name].vault.azure.net/[Key Name] [Container Registry Name].azurecr.io/[Image Name] ``` Required access policy (keys): `verify` ```shell az acr login --name [Container Registry Name] cosign verify --key azurekms://[Key Vault Name].vault.azure.net/[Key Name] [Container Registry Name].azurecr.io/[Image Name] ``` There are multiple authentication methods supported for Azure Key Vault and by default they will be evaluated in the following order: Client credentials (FromEnvironment) Client certificate (FromEnvironment) Username password (FromEnvironment) MSI (FromEnvironment) CLI (FromCLI) You can force either `FromEnvironment` or `FromCLI` by configuring the environment variable `AZUREAUTHMETHOD` to either `environment` or `cli`. For backward compatibility, if you configure `AZURETENANTID`, `AZURECLIENTID` and `AZURECLIENTSECRET`, `FromEnvironment` will be used. If you would like to use a cloud other than the Azure public cloud, configure `AZURE_ENVIRONMENT`. The following values are accepted: `AZUREUSGOVERNMENT`, `AZUREUSGOVERNMENTCLOUD` uses the Azure US Government Cloud `AZURECHINACLOUD` uses Azure China Cloud `AZURECLOUD`, `AZUREPUBLICCLOUD` uses the public cloud If `AZURE_ENVIRONMENT` is not configured, Azure public cloud is used. In addition to unit tests in this module, there is `integration_test.go`, which requires you to provide either environment or CLI credentials. Because the Sigstore project does not use Azure, the tests are not run as part of any CI/CD. These tests are for Azure client developers to test that changes work as expected against their own Azure subscription. Run the integration tests with `go test -tags=integration ./...` in the root of this module.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.173.md

layout: release date: 2023-11-07 tag: v0.6.173 Fix Dark mode @ptdatta (#9318) Enable status col in connection and add ping check @sudhanshutech (#9317) [bug] Fix broken UI @sudhanshutech (#9315) [bug] Fix broken UI @sudhanshutech (#9315) [docs] Fix Redirection /platforms/page -> /page @theBeginner86 (#9316) [bug/docs] Fix redirect from /platforms @theBeginner86 (#9314) Thank you to our contributors for making this release possible: @MUzairS15, @l5io, @leecalcote, @ptdatta, @sudhanshutech and @theBeginner86
Project: ShardingSphere (App Definition and Development / Database)
File: show-sql-parser-rule.en.md

+++ title = "SHOW SQL_PARSER RULE" weight = 4 +++ The `SHOW SQL_PARSER RULE` syntax is used to query sql parser rule configuration. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowSqlParserRule ::= 'SHOW' 'SQL_PARSER' 'RULE' ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} | Column | Description | ||--| | parsetreecache | parse tree cache configuration | | sqlstatementcache | SQL statement cache configuration | Query sql parser rule configuration ```sql SHOW SQL_PARSER RULE; ``` ```sql mysql> SHOW SQL_PARSER RULE; +--+-+ | parsetreecache | sqlstatementcache | +--+-+ | initialCapacity: 128, maximumSize: 1024 | initialCapacity: 2000, maximumSize: 65535 | +--+-+ 1 row in set (0.05 sec) ``` `SHOW`, `SQL_PARSER`, `RULE`
Project: Apicurio Registry (App Definition and Development / Streaming & Messaging)
File: bug_report.md

name: Bug report about: Use this template to report a bug in this project title: "" labels: Bug <!-- In order for us to better investigate the bug, please fill in as much relevant information as is reasonable in the format below. Before proceeding, consider the following: This repository is for issues with Apicurio Registry. Make sure the bug report is not more appropriate or another repository. Make sure the bug is in Apicurio Registry and not in an external library or other non-Apicurio software. For example, we provide a compatibility REST API for Confluent Schema Registry clients. Make sure the bug is not in one of their libraries. Run the Registry with DEBUG logging enabled, by passing the LOG_LEVEL=DEBUG env. variable. --> Registry Version: <!-- Please add the Apicurio Registry version number here. You can use "latest" for the latest released version, or "snapshot" if you are using a build from main. --> Persistence type: <!-- Please add the persistence type here. One of "in-memory", "sql", or "kafkasql". --> <!-- Please provide as much detail about the bug as possible. --> <!-- What is the environment in which you are running Apicurio Registry? e.g. Kubernetes v1.25. How are you interacting with Apicurio Registry? Are you using a specific serdes client? Please include its version. --> <!-- Add the steps required to reproduce this error. Go to `XX >> YY >> SS` Create a new item `N` with the info `X` See error If the error cannot be easily reproduced, make sure to fill in the Environment and Logs sections. You can also try to reproduce the bug with a fresh Apicurio Registry instance. --> <!-- A clear and concise description of what you expected to happen and what actually happened. --> <!-- Paste or link the logs from Registry, browser console, your command line or other relevant places. Redact if needed.-->
Project: Beam (App Definition and Development / Streaming & Messaging)
File: custom-io.md

title: "Custom I/O patterns" <!-- 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 page describes common patterns in pipelines with . Custom I/O connectors connect pipelines to databases that aren't supported by Beam's . {{< language-switcher java py >}} are tested and hardened, so use them whenever possible. Only use custom I/O connectors when: No built-in options exist Your pipeline pulls in a small subset of source data For instance, use a custom I/O connector to enrich pipeline elements with a small subset of source data. If youre processing a sales order and adding information to each purchase, you can use a custom I/O connector to pull the small subset of data into your pipeline (instead of processing the entire source). Beam distributes work across many threads, so custom I/O connectors can increase your data sources load average. You can reduce the load with the <span class="language-java"></span><span class="language-py"></span> and <span class="language-java"></span><span class="language-py"></span> bundle annotations.
Project: YugabyteDB (App Definition and Development / Database)
File: extension-pgcrypto.md

title: pgcrypto extension headerTitle: pgcrypto extension linkTitle: pgcrypto description: Using the pgcrypto extension in YugabyteDB menu: v2.18: identifier: extension-pgcrypto parent: pg-extensions weight: 20 type: docs The module provides cryptographic functions for PostgreSQL. ```sql CREATE EXTENSION pgcrypto; CREATE TABLE pgcryptoexample(id uuid PRIMARY KEY DEFAULT genrandom_uuid(), content text, digest text); INSERT INTO pgcrypto_example (content, digest) values ('abc', digest('abc', 'sha1')); SELECT * FROM pgcrypto_example; ``` ```output id | content | digest --++-- b8f2e2f7-0b8d-4d26-8902-fa4f5277869d | abc | \xa9993e364706816aba3e25717850c26c9cd0d89d (1 row) ```
Project: YugabyteDB (App Definition and Development / Database)
File: hmset.md

title: HMSET linkTitle: HMSET description: HMSET menu: preview: parent: api-yedis weight: 2170 aliases: /preview/api/redis/hmset /preview/api/yedis/hmset type: docs `HMSET key field value [field value ...]` This command sets the data for the given `field` with the given `value` in the hash that is specified by `key`. If the given `field` already exists in the specified hash, this command overwrites the existing value with the given `value`. If the given `key` does not exist, a new hash is created for the `key`, and the given values are inserted to the associated given fields. If the given `key` is associated with a non-hash data, an error is raised. Returns status string. ```sh $ HMSET yugahash area1 "America" area2 "Africa" ``` ``` "OK" ``` ```sh $ HGET yugahash area1 ``` ``` "America" ``` , , , , , , , , , ,
Project: YugabyteDB (App Definition and Development / Database)
File: date-and-time-ycql.md

title: Date and time in YCQL headerTitle: Date and time linkTitle: 7. Date and time description: Learn how to work with date and time in YCQL. menu: v2.18: parent: learn name: 7. Date and time identifier: date-and-time-2-ycql weight: 569 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="{{< relref "./date-and-time-ysql.md" >}}" class="nav-link"> <i class="icon-postgres" aria-hidden="true"></i> YSQL </a> </li> <li > <a href="{{< relref "./date-and-time-ysql.md" >}}" class="nav-link active"> <i class="icon-cassandra" aria-hidden="true"></i> YCQL </a> </li> </ul> YCQL content coming soon.
Project: ClickHouse (App Definition and Development / Database)
File: quota.md

slug: /en/sql-reference/statements/create/quota sidebar_position: 42 sidebar_label: QUOTA title: "CREATE QUOTA" Creates a that can be assigned to a user or a role. Syntax: ``` sql CREATE QUOTA [IF NOT EXISTS | OR REPLACE] name [ON CLUSTER cluster_name] [IN accessstoragetype] [KEYED BY {username | ipaddress | clientkey | clientkey,username | clientkey,ip_address} | NOT KEYED] [FOR [RANDOMIZED] INTERVAL number {second | minute | hour | day | week | month | quarter | year} {MAX { {queries | queryselects | queryinserts | errors | resultrows | resultbytes | readrows | readbytes | execution_time} = number } [,...] | NO LIMITS | TRACKING ONLY} [,...]] [TO {role [,...] | ALL | ALL EXCEPT role [,...]}] ``` Keys `username`, `ipaddress`, `clientkey`, `clientkey, username` and `clientkey, ip_address` correspond to the fields in the table. Parameters `queries`, `queryselects`, `queryinserts`, `errors`, `resultrows`, `resultbytes`, `readrows`, `readbytes`, `executiontime`, `failedsequential_authentications` correspond to the fields in the table. `ON CLUSTER` clause allows creating quotas on a cluster, see . Examples Limit the maximum number of queries for the current user with 123 queries in 15 months constraint: ``` sql CREATE QUOTA qA FOR INTERVAL 15 month MAX queries = 123 TO CURRENT_USER; ``` For the default user limit the maximum execution time with half a second in 30 minutes, and limit the maximum number of queries with 321 and the maximum number of errors with 10 in 5 quarters: ``` sql CREATE QUOTA qB FOR INTERVAL 30 minute MAX execution_time = 0.5, FOR INTERVAL 5 quarter MAX queries = 321, errors = 10 TO default; ```
Project: ko (App Definition and Development / Application Definition & Image Build)
File: community.md

We have a bi-weekly community meeting on . The main goal of these meetings is that we want to hear from you! We want to know what you're using `ko` for, what you'd like to see in `ko`, how we can make `ko` better for you. With any remaining time we can go through open issues and PRs. We have a you can use to propose topics for discussion/ideas. You can also just show up and we'll figure out what to talk about. Come discuss `ko` with us in the `#ko-build` channel on the ! See you there!
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-token-set.md

layout: default title: mesheryctl-system-token-set permalink: reference/mesheryctl/system/token/set redirect_from: reference/mesheryctl/system/token/set/ type: reference display-title: "false" language: en command: system subcommand: token Set token for context Set token for current context or context specified with --context flag. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system token set [flags] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system token set [token-name] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --context string Pass the context -h, --help help for set </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 -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: Beam (App Definition and Development / Streaming & Messaging)
File: Strivr.md

title: "Strivr" icon: /images/logos/powered-by/Strivr.png hasLink: "https://www.strivr.com/" <!-- 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. -->
Project: KICS (Provisioning / Security & Compliance)
File: 69f72007-502e-457b-bd2d-5012e31ac049.md

title: Firewall Rule Allows Too Many Hosts To Access Redis Cache hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 69f72007-502e-457b-bd2d-5012e31ac049 Query name: Firewall Rule Allows Too Many Hosts To Access Redis Cache Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: Check if any firewall rule allows too many hosts to access Redis Cache.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="6" name: toomanyhosts azurermrediscachefirewallrule: resource_group: myResourceGroup cache_name: myRedisCache name: myRule startipaddress: 192.168.1.1 endipaddress: 192.169.1.4 ``` ```yaml title="Negative test num. 1 - yaml file" name: reduced_hosts azurermrediscachefirewallrule: resource_group: myResourceGroup cache_name: myRedisCache name: myRule startipaddress: 192.168.1.1 endipaddress: 192.168.1.4 ```
Project: Apache Hadoop (App Definition and Development / Database)
File: YarnUI2.md

<!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> Hadoop: YARN-UI V2 ================= Prerequisites Please make sure Hadoop is built by passing -Pyarn-ui to Maven (reference to BUILDING.txt for more details) Configurations In `yarn-site.xml` | Configuration Property | Description | |:- |:- | | `yarn.webapp.ui2.enable` | (Required) In the server side it indicates whether the new YARN-UI v2 is enabled or not. Defaults to `false`. | | `yarn.webapp.ui2.war-file-path` | (Optional) WAR file path for launching yarn UI2 web application. By default this is empty and YARN will lookup required war file from classpath | Please note that, If you run YARN daemons locally in your machine for test purpose, you need the following configurations added to `yarn-site.xml` to enable cross origin (CORS) support. | Configuration Property | Value | Description | |:- |:- |:--| | `yarn.timeline-service.http-cross-origin.enabled` | true | Enable CORS support for Timeline Server | | `yarn.resourcemanager.webapp.cross-origin.enabled` | true | Enable CORS support for Resource Manager | | `yarn.nodemanager.webapp.cross-origin.enabled` | true | Enable CORS support for Node Manager | | `yarn.router.webapp.cross-origin.enabled` | true | Enable CORS support for Yarn Router | | `yarn.federation.gpg.webapp.cross-origin.enabled` | true | Enable CORS support for Yarn GPG | Also please ensure that CORS related configurations are enabled in `core-site.xml`. Kindly refer Use it Open your browser, go to `rm-address:8088/ui2` and try it! Notes This UI framework is verified under security environment as well.
Project: ShardingSphere (App Definition and Development / Database)
File: limitations.en.md

+++ title = "Limitations" weight = 2 +++ Although Apache ShardingSphere aims at being compatible with all distributed scenario and providing the best performance, under the CAP theorem guidance, there is no sliver bullet with distributed transaction solution. The Apache ShardingSphere community chose instead to give the users the ability to choose their preferred distributed transaction type and use the most suitable solution according to their scenarios. Does not support the cross-database transactions caused by network or hardware crash. For example, when updating two databases in transaction, if one database crashes before commit, then only the data of the other database can commit. Recover committing and rolling back in other machines after the service is down. MySQL, in the transaction block, the SQL execution is abnormal, and run `Commit`, and data remains consistent. After XA transactions are configured, the maximum length of the storage unit name cannot exceed 45 characters. Does not support isolation level.
Project: YugabyteDB (App Definition and Development / Database)
File: topology-aware-drivers.md

title: Topology aware client drivers headerTitle: Topology-aware client drivers linkTitle: Topology-aware drivers headcontent: menu: preview: identifier: topology-aware-drivers parent: going-beyond-sql weight: 500 rightNav: hideH3: true type: docs Topology-aware connections in YugabyteDB refer to a feature of the that enables them to dynamically adapt to the topology (structure and arrangement) of the database cluster. This capability allows the client drivers to make intelligent decisions about which nodes to connect to based on the current state of the cluster, such as node availability. In this section, we will explore the features and benefits of YugabyteDB's topology-aware , highlighting their significance in distributed application development. To create a topology-aware connection, you specify topology keys in the connection string of the application. Topology keys are a comma-separated list of cluster locations, in the form `cloud.region.zone`, that allow you to limit connections to specific regions and zones. For example, to connect only to nodes in the `us-east-1a` zone located in the `us-east-1` region, you can set your connection string as follows: ```sql "postgres://host:5433/dbname?topology_keys=aws.us-east-1.us-east-1a" ``` To connect to any node in region `us-east-1`, you can use an asterisk (`*`) for globbing as follows: ```sql "postgres://host:5433/dbname?topology_keys=aws.us-east-1.*" ``` Using topology keys, you can tell your application to only connect to nodes that are nearby. For example, for applications running in `us-central-1`, you can set `topologykeys` to `aws.us-central-1.*`; for applications running in `us-east`, you can set `topologykeys` to `aws.us-east-1.*`. When you create a YugabyteDB cluster, you can specify , which defines the priority of placement of leaders. You can opt to specify the same order of priority in the `topologykeys` parameter to ensure that the driver connects to the next preferred region when the first preferred region fails. For example, if you have set up your first preferred region to `us-east` and your second preferred region to `us-central`, then you can specify the `topologykeys` as follows: ```sql "postgres://host:5433/dbname?topology_keys=aws.us-east-1.:1,aws.us-central-1.:2" ``` This way, if the region `us-east` fails, your application will automatically connect to `us-central`.
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: md_docs.md

Generating Markdown pages from a cobra command is incredibly easy. An example is as follows: ```go package main import ( "log" "github.com/spf13/cobra" "github.com/spf13/cobra/doc" ) func main() { cmd := &cobra.Command{ Use: "test", Short: "my test program", } err := doc.GenMarkdownTree(cmd, "/tmp") if err != nil { log.Fatal(err) } } ``` That will get you a Markdown document `/tmp/test.md` This program can actually generate docs for the kubectl command in the kubernetes project ```go package main import ( "log" "io/ioutil" "os" "k8s.io/kubernetes/pkg/kubectl/cmd" cmdutil "k8s.io/kubernetes/pkg/kubectl/cmd/util" "github.com/spf13/cobra/doc" ) func main() { kubectl := cmd.NewKubectlCommand(cmdutil.NewFactory(nil), os.Stdin, ioutil.Discard, ioutil.Discard) err := doc.GenMarkdownTree(kubectl, "./") if err != nil { log.Fatal(err) } } ``` This will generate a whole series of files, one for each command in the tree, in the directory specified (in this case "./") You may wish to have more control over the output, or only generate for a single command, instead of the entire command tree. If this is the case you may prefer to `GenMarkdown` instead of `GenMarkdownTree` ```go out := new(bytes.Buffer) err := doc.GenMarkdown(cmd, out) if err != nil { log.Fatal(err) } ``` This will write the markdown doc for ONLY "cmd" into the out, buffer. Both `GenMarkdown` and `GenMarkdownTree` have alternate versions with callbacks to get some control of the output: ```go func GenMarkdownTreeCustom(cmd *Command, dir string, filePrepender, linkHandler func(string) string) error { //... } ``` ```go func GenMarkdownCustom(cmd Command, out bytes.Buffer, linkHandler func(string) string) error { //... } ``` The `filePrepender` will prepend the return value given the full filepath to the rendered Markdown file. A common use case is to add front matter to use the generated documentation with : ```go const fmTemplate = ` date: %s title: "%s" slug: %s url: %s ` filePrepender := func(filename string) string { now := time.Now().Format(time.RFC3339) name := filepath.Base(filename) base := strings.TrimSuffix(name, path.Ext(name)) url := "/commands/" + strings.ToLower(base) + "/" return fmt.Sprintf(fmTemplate, now, strings.Replace(base, "_", " ", -1), base, url) } ``` The `linkHandler` can be used to customize the rendered internal links to the commands, given a filename: ```go linkHandler := func(name string) string { base := strings.TrimSuffix(name, path.Ext(name)) return "/commands/" + strings.ToLower(base) + "/" } ```