cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: etcd-cluster-operator.md

layout: integration title: Etcd Cluster Operator subtitle: Collaborative and visual infrastructure as code for Etcd Cluster Operator image: /assets/img/integrations/etcd-cluster-operator/icons/color/etcd-cluster-operator-color.svg permalink: extensibility/integrations/etcd-cluster-operator docURL: https://docs.meshery.io/extensibility/integrations/etcd-cluster-operator description: integrations-category: Orchestration & Management integrations-subcategory: Coordination & Service Discovery registrant: Artifact Hub components: name: etcd-backup colorIcon: assets/img/integrations/etcd-cluster-operator/components/etcd-backup/icons/color/etcd-backup-color.svg whiteIcon: assets/img/integrations/etcd-cluster-operator/components/etcd-backup/icons/white/etcd-backup-white.svg description: name: etcd-backup-schedule colorIcon: assets/img/integrations/etcd-cluster-operator/components/etcd-backup-schedule/icons/color/etcd-backup-schedule-color.svg whiteIcon: assets/img/integrations/etcd-cluster-operator/components/etcd-backup-schedule/icons/white/etcd-backup-schedule-white.svg description: name: etcd-cluster colorIcon: assets/img/integrations/etcd-cluster-operator/components/etcd-cluster/icons/color/etcd-cluster-color.svg whiteIcon: assets/img/integrations/etcd-cluster-operator/components/etcd-cluster/icons/white/etcd-cluster-white.svg description: name: etcd-peer colorIcon: assets/img/integrations/etcd-cluster-operator/components/etcd-peer/icons/color/etcd-peer-color.svg whiteIcon: assets/img/integrations/etcd-cluster-operator/components/etcd-peer/icons/white/etcd-peer-white.svg description: name: etcd-restore colorIcon: assets/img/integrations/etcd-cluster-operator/components/etcd-restore/icons/color/etcd-restore-color.svg whiteIcon: assets/img/integrations/etcd-cluster-operator/components/etcd-restore/icons/white/etcd-restore-white.svg description: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-qry-select-limit.md

layout: global title: LIMIT Clause displayTitle: LIMIT Clause license: | 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. The `LIMIT` clause is used to constrain the number of rows returned by the statement. In general, this clause is used in conjunction with to ensure that the results are deterministic. ```sql LIMIT { ALL | integer_expression } ``` ALL* If specified, the query returns all the rows. In other words, no limit is applied if this option is specified. integer_expression* Specifies a foldable expression that returns an integer. ```sql CREATE TABLE person (name STRING, age INT); INSERT INTO person VALUES ('Zen Hui', 25), ('Anil B', 18), ('Shone S', 16), ('Mike A', 25), ('John A', 18), ('Jack N', 16); -- Select the first two rows. SELECT name, age FROM person ORDER BY name LIMIT 2; +++ | name|age| +++ |Anil B| 18| |Jack N| 16| +++ -- Specifying ALL option on LIMIT returns all the rows. SELECT name, age FROM person ORDER BY name LIMIT ALL; +-++ | name|age| +-++ | Anil B| 18| | Jack N| 16| | John A| 18| | Mike A| 25| |Shone S| 16| |Zen Hui| 25| +-++ -- A function expression as an input to LIMIT. SELECT name, age FROM person ORDER BY name LIMIT length('SPARK'); +-++ | name|age| +-++ | Anil B| 18| | Jack N| 16| | John A| 18| | Mike A| 25| |Shone S| 16| +-++ -- A non-foldable expression as an input to LIMIT is not allowed. SELECT name, age FROM person ORDER BY name LIMIT length(name); org.apache.spark.sql.AnalysisException: The limit expression must evaluate to a constant value ... ```
Project: ShardingSphere (App Definition and Development / Database)
File: alter-mask-rule.en.md

+++ title = "ALTER MASK RULE" weight = 2 +++ The `ALTER MASK RULE` syntax is used to create a mask rule. {{< tabs >}} {{% tab name="Grammar" %}} ```sql AlterEncryptRule ::= 'ALTER' 'MASK' 'RULE' maskRuleDefinition (',' maskRuleDefinition)* maskRuleDefinition ::= ruleName '(' 'COLUMNS' '(' columnDefinition (',' columnDefinition)* ')' ')' columnDefinition ::= '(' 'NAME' '=' columnName ',' maskAlgorithmDefinition ')' maskAlgorithmDefinition ::= 'TYPE' '(' 'NAME' '=' algorithmType (',' propertiesDefinition)? ')' propertiesDefinition ::= 'PROPERTIES' '(' key '=' value (',' key '=' value)* ')' ruleName ::= identifier columnName ::= identifier algorithmType ::= literal key ::= string value ::= literal ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} `algorithmType` specifies the data masking algorithm type, please refer to . ```sql ALTER MASK RULE t_mask ( COLUMNS( (NAME=phonenumber,TYPE(NAME='MASKFROMXTO_Y', PROPERTIES("from-x"=1, "to-y"=2, "replace-char"="*"))), (NAME=address,TYPE(NAME='MD5')) )); ``` `ALTER`, `MASK`, `RULE`, `COLUMNS`, `NAME`, `TYPE`
Project: Kraken (Provisioning / Container Registry)
File: ENDPOINTS.md

Table of Contents - - Kraken proxy implements all . Kraken agent only implements the GET and HEAD endpoints of docker registry. You can push images to proxy using normal docker push command: ``` docker push {proxyhost}:{proxyport}/{repo}:{tag} ``` Proxy will then upload the blobs and tag to origin and build-index. Yon can also pull from proxy directly without going through the p2p network: ``` docker pull {proxyhost}:{proxyport}/{repo}:{tag} ``` Note: if you didn't configure Kraken with TLS, you might need to update your docker daemon config to whitelist kraken-proxy as an first. To pull docker images from local kraken agent, run: ``` docker pull localhost:{agentregistryport}/{repo}:{tag} ``` Note: kraken agent use different ports for docker registry endpoints and generic content addressable blobs. Please make sure you are using the port configured via `agentregistryport`. Kraken's usecase is not limited to docker images. It exposes a separate set of endpoints for uploading and downloading generic blobs that's identified by SHA256 hash of the content. Kraken proxy and build-index are not used in this usecase. Uploads will be handled by Kraken origin, and downloads still go through Kraken agent. Blobs can be uploaded through the Kraken origin cluster and into your storage backend. All blobs must be uploaded in chunks, using the following API: ``` POST /namespace/<namespace>/blobs/<digest>/uploads ``` Starts the upload. Returns an upload id in the "Location" response header, which is used for uploading chunks of the blob. ``` PATCH /namespace/<namespace>/blobs/<digest>/uploads/<uid> ``` Uploads a chunk of the blob, using the previously returned upload id. Supply the chunk bytes in the request body. The "Content-Range" header in the request must specify the range of the chunk being uploaded, for example: ``` Content-Range: 128,256 ``` This would upload the request body to bytes ``[128, 256)`` of the blob. ``` PUT /namespace/<namespace>/blobs/<digest>/uploads/<uid>?through=<through> ``` Commits the upload. If ``through`` is set to ``true``, the blob will be uploaded through the origin cluster and into the storage backend configured for ``namespace``. ``` GET /namespace/<namespace>/blobs/<digest> ``` Once Kraken has been configured with your storage information and namespace, you can download your blobs from any host with a Kraken agent running on it. The download endpoint takes your namespace and the content digest of the blob you want to download, and blocks until agent has downloaded the blob to its on-disk cache. Once the blob is downloaded locally, status 200 is returned and the blob content is streamed over the response body. Error codes: 404: Blob was not found in your storage backend. 5xx: Something went wrong. Check the response body for an error message, or reach out to the Kraken team.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_http_health_check.md

+++ title = "googlecomputehttphealthcheck resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputehttphealthcheck" identifier = "inspec/resources/gcp/googlecomputehttphealthcheck.md googlecomputehttphealthcheck resource" parent = "inspec/resources/gcp" +++ A `googlecomputehttphealthcheck` is used to test a Google HttpHealthCheck resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputehttphealthcheck(project: 'chef-gcp-inspec', name: 'inspec-gcp-http-health-check') do it { should exist } its('timeout_sec') { should eq '20' } its('requestpath') { should eq '/healthcheck' } its('checkintervalsec') { should eq '20' } end describe googlecomputehttphealthcheck(project: 'chef-gcp-inspec', name: 'nonexistent') do it { should_not exist } end ``` Properties that can be accessed from the `googlecomputehttphealthcheck` resource: `checkintervalsec` : How often (in seconds) to send a health check. The default value is 5 seconds. `creation_timestamp` : Creation timestamp in RFC3339 text format. `description` : An optional description of this resource. Provide this property when you create the resource. `healthy_threshold` : A so-far unhealthy instance will be marked healthy after this many consecutive successes. The default value is 2. `host` : The value of the host header in the HTTP health check request. If left empty (default value), the public IP on behalf of which this health check is performed will be used. `id` : The unique identifier for the resource. This identifier is defined by the server. `name` : Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression `?` which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash. `port` : The TCP port number for the HTTP health check request. The default value is 80. `request_path` : The request path of the HTTP health check request. The default value is /. `timeout_sec` : How long (in seconds) to wait before claiming failure. The default value is 5 seconds. It is invalid for timeoutSec to have greater value than checkIntervalSec. `unhealthy_threshold` : A so-far healthy instance will be marked unhealthy after this many consecutive failures. The default value is 2. Ensure the is enabled for the current project.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: PKG_LINUX.md

Debian Jesse using this `Vagrantfile`: ``` $script = <<SCRIPT export LANG='C.UTF-8' export DEBIAN_FRONTEND=noninteractive echo 'deb http://cdn-fastly.deb.debian.org/debian jessie-backports main' >> /etc/apt/sources.list.d/backports.list wget https://packages.erlang-solutions.com/erlang-solutions1.0all.deb dpkg -i erlang-solutions1.0all.deb apt-get clean apt-get update apt-get install -y --fix-missing --no-install-recommends \ build-essential \ ca-certificates \ debhelper \ dh-systemd \ elinks \ esl-erlang \ elixir \ fakeroot \ git \ libfile-fcntllock-perl \ mandoc \ nsis \ python-lxml \ python-markdown \ python-simplejson \ rpm \ rsync \ tofrodos \ unzip \ xmlto \ xsltproc \ zip \ curl date > /etc/vagrantprovisionedat SCRIPT Vagrant.configure('2') do |config| config.vm.box = "debian/jessie64" config.vm.hostname = 'DEBIAN-JESSIE64' config.vm.provision 'shell', inline: $script end ``` Bring up a Debian Jesse instance using Vagrant, or, use the provisioning script on a Debian Jesse server of your own. When it is done running, all necessary package build requirements for either `apt`-based or `rpm`-based distros will be present. See the document for instructions on building packages.
Project: Sonobuoy (Provisioning / Security & Compliance)
File: sonobuoy_status.md

Gets a summarized status of a sonobuoy run ``` sonobuoy status [flags] ``` ``` --context string Context in the kubeconfig to use. -h, --help help for status --json Print the status object as json --kubeconfig Kubeconfig Path to explicit kubeconfig file. -n, --namespace string The namespace to run Sonobuoy in. Only one Sonobuoy run can exist per namespace simultaneously. (default "sonobuoy") --show-all Don't summarize plugin statuses, show results for each node ``` ``` --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) ``` - Generate reports on your Kubernetes cluster by running plugins
Project: KICS (Provisioning / Security & Compliance)
File: 2e44e632-d617-43cb-b294-6bfe72a08938.md

title: Operation Using Password Flow hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2e44e632-d617-43cb-b294-6bfe72a08938 Query name: Operation Using Password Flow Platform: OpenAPI Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Operation Object should not use 'password' Flow in OAuth2 authentication<br> ```json title="Positive test num. 1 - json file" hl_lines="22" { "swagger": "2.0", "info": { "title": "Simple API overview", "version": "1.0.0" }, "schemes": [ "https" ], "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "security": [ { "oAuth2AuthCodeNeg2": [ "write", "read" ] } ] } } }, "securityDefinitions": { "oAuth2AuthCodeNeg2": { "type": "oauth2", "description": "For more information, see https://api.my.company.com/docs/oauth", "flow": "password", "tokenUrl": "https://api.my.company.com/oauth/token" } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="16" swagger: "2.0" info: title: Simple API overview version: 1.0.0 schemes: https paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response security: oAuth2AuthCodeNeg2: write read securityDefinitions: oAuth2AuthCodeNeg2: type: oauth2 description: For more information, see https://api.my.company.com/docs/oauth flow: password tokenUrl: https://api.my.company.com/oauth/token ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API overview", "version": "1.0.0" }, "schemes": [ "https" ], "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "security": [ { "oAuth2AuthCodeNeg2": [ "write", "read" ] } ] } } }, "securityDefinitions": { "oAuth2AuthCodeNeg2": { "type": "oauth2", "description": "For more information, see https://api.my.company.com/docs/oauth", "flow": "accessCode", "authorizationUrl": "https://api.my.company.com/oauth/authorize", "tokenUrl": "https://api.my.company.com/oauth/token", "scopes": { "write:api": "modify apis in your account", "read:api": "read your apis" } } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: "2.0" info: title: Simple API overview version: 1.0.0 schemes: https paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response security: oAuth2AuthCodeNeg2: write read securityDefinitions: oAuth2AuthCodeNeg2: type: oauth2 description: For more information, see https://api.my.company.com/docs/oauth flow: accessCode authorizationUrl: https://api.my.company.com/oauth/authorize tokenUrl: https://api.my.company.com/oauth/token scopes: write:api: modify apis in your account read:api: read your apis ```
Project: external-secrets (Provisioning / Security & Compliance)
File: acr.md

The Azure Container Registry (ACR) generator creates a short-lived refresh or access token for accessing ACR. The token is generated for a particular ACR registry defined in `spec.registry`. | Key | Description | | -- | -- | | username | username for the `docker login` command | | password | password for the `docker login` command | You must choose one out of three authentication mechanisms: service principal managed identity workload identity The generated token will inherit the permissions from the assigned policy. I.e. when you assign a read-only policy all generated tokens will be read-only. You must , such as `AcrPush` or `AcrPull` to the service principal in order to be able to authenticate with the Azure container registry API. You can scope tokens to a particular repository using `spec.scope`. First, an Azure Active Directory access token is obtained with the desired authentication method. This AAD access token will be used to authenticate against ACR to issue a refresh token or access token. If `spec.scope` if it is defined it obtains an ACR access token. If `spec.scope` is missing it obtains an ACR refresh token: access tokens are scoped to a specific repository or action (pull,push) refresh tokens can are scoped to whatever policy is attached to the identity that creates the acr refresh token The Scope grammar is defined in the . Note: You can not use a wildcards in the scope parameter, you can match exactly one repository and defined multiple actions like `pull` or `push`. Example scopes: ``` repository:my-repository:pull,push repository:my-repository:pull ``` ```yaml {% include 'generator-acr.yaml' %} ``` Example `ExternalSecret` that references the ACR generator: ```yaml {% include 'generator-acr-example.yaml' %} ```
Project: ClickHouse (App Definition and Development / Database)
File: v21.7.4.18-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fixed incorrect `sequence_id` in MySQL protocol packets that ClickHouse sends on exception during query execution. It might cause MySQL client to reset connection to ClickHouse server. Fixes . (). Backported in : Fix logical error on join with totals, close . (). Backported in : Fixed rare bug in lost replica recovery that may cause replicas to diverge. (). Backported in : Fix possible crash when login as dropped user. This PR fixes . (). Backported in : Fix infinite non joined block stream in `partialmergejoin` close . (). Backported in : Fix some fuzzed msan crash. Fixes . ().
Project: Seata (App Definition and Development / Database)
File: 1.5.2.md

| <details> <summary><mark>Release notes</mark></summary> Seata 1.5.2 Released. Seata is an easy-to-use, high-performance, open source distributed transaction solution. The version is updated as follows: ] support xid consistency load balance ] support server to expose Nacos services by mounting SLB ] support batch message parallel processing ] support where method condition(findinset) ] fix the error of SeataTCCFenceAutoConfiguration when database unused ] fix sql exception with PostgreSQL in module console ] fix the exception in RedisTransactionStoreManager for update map During iteration ] fix the error of key transport.enableRmClientBatchSendRequest cache penetration if not configure ] fix missing command line args ] fix bug on skipping lock check ] fix oracle database insert value ] fix batch message send may return NullPointException ] fix set AspectTransactional.rollbackForClassName with wrong value ] fix the sql exception when pk is non-numeric in INSERTONDUPLICATE SQL ] fix some security vulnerabilities ] optimize the thread pool size of branchResultMessageExecutor ] optimize rollback transaction metrics ] optimize the console navigation bar ] fix maven-compiler-plugin and maven-resources-plugin execute failed ] separate lib dependencies for deployments ] optimize pom description ] upgrade logback dependency to 1.2.9 ] support mysql8 in release package ] Replace `flatten-maven-plugin` with `easyj-maven-plugin` to fix the conflict between `shade` and `flatten` ] check relation of before status and after status when updating global session ] make EnhancedServiceLoader more readable ] optimize transaction timeout judgment ] do not execute triggerAfterCommit() in case of timeout ] optimize jackson dependencies in TransactionContextFilterTest ] fix UT failed in AsyncWorkerTest and LockManagerTest Thanks to these contributors for their code commits. Please report an unintended omission. <!-- Please make sure your Github ID is in the list below --> Also, we receive many valuable issues, questions and advices from our community. Thanks for you all. Seata: https://github.com/seata/seata Seata-Samples: https://github.com/seata/seata-samples Release: https://github.com/seata/seata/releases WebSite: https://seata.io </details>
Project: YDB (App Definition and Development / Database)
File: source_code.md

| Version | Release date | Link | Changelog | : | : | : | : v23.4 v.23.4.11 | 14/05/2024 | v23.3 v.23.3.17 | 14/12/2023 | v.23.3.13 | 12/10/2023 | | v23.2 v.23.2.12 | 14/08/2023 | | v23.1 v.23.1.26 | 05/05/2023 | | v22.5 v.22.5.10 | 09/02/2023 | | v22.4 v.22.4.44 | 28/11/2022 | | v.22.4.31 | 23/10/2022 | v.22.4.30 | 09/10/2022 | v.22.4.21 | 03/10/2022 | v22.2 v.22.2.47 | 07/07/2022 | v.22.2.40 | 16/06/2022 | v.22.2.39 | 15/06/2022 | v.22.2.31 | 07/06/2022 | v.22.2.22 | 18/04/2022 | v.22.2.5 | 14/02/2022 |
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_logging_folder_exclusions.md

+++ title = "googleloggingfolder_exclusions resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleloggingfolder_exclusions" identifier = "inspec/resources/gcp/googleloggingfolderexclusions.md googleloggingfolderexclusions resource" parent = "inspec/resources/gcp" +++ A `googleloggingfolder_exclusions` is used to test a Google FolderExclusion resource ```ruby describe.one do googleresourcemanagerfolders(parent: 'organizations/12345').names.each do |name| describe googleloggingfolder_exclusions(folder: name.split('/')[1]) do its('names'){ should include 'inspec-folder-exclusion' } its('descriptions'){ should include 'My folder exclusion description' } its('filters'){ should include 'resource.type = gce_instance AND severity <= DEBUG' } end end end ``` Properties that can be accessed from the `googleloggingfolder_exclusions` resource: See the resource for more information. `folders` : an array of `googleloggingfolder_exclusion` folder `names` : an array of `googleloggingfolder_exclusion` name `descriptions` : an array of `googleloggingfolder_exclusion` description `filters` : an array of `googleloggingfolder_exclusion` filter `disableds` : an array of `googleloggingfolder_exclusion` disabled This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.