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

layout: release date: 2024-03-04 tag: v0.7.27 [mesheryctl] Update model generator. @MUzairS15 (#10487) [chore] fix UI lint issues. @MUzairS15 (#10492) [chore] Bump meshkit to v0.7.16 @MUzairS15 (#10489) Inject Sistent Into remote components @codeKraken19 (#10480) Bump eslint from 8.55.0 to 8.57.0 in /provider-ui @dependabot (#10463) Bump github.com/fatih/color from 1.15.0 to 1.16.0 @dependabot (#10473) Create Bill of Materials and Licenses @jameshorton2337 (#10477) Bump eslint from 8.55.0 to 8.57.0 in /provider-ui @dependabot (#10463) Thank you to our contributors for making this release possible: @MUzairS15, @aabidsofi19, @codeKraken19, @dependabot, @dependabot[bot], @jameshorton2337, @l5io and @leecalcote
Project: ShardingSphere (App Definition and Development / Database)
File: show-shadow-algorithm.en.md

+++ title = "SHOW SHADOW ALGORITHMS" weight = 3 +++ The `SHOW SHADOW ALGORITHMS` syntax is used to query shadow algorithms for specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowEncryptAlgorithm::= 'SHOW' 'SHADOW' 'ALGORITHMS' ('FROM' databaseName)? databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When `databaseName` is not specified, the default is the currently used `DATABASE`. If `DATABASE` is not used, `No database selected` will be prompted. | Column | Description | |--|--| | shadowalgorithmname | Shadow algorithm name | | type | Shadow algorithm type | | props | Shadow algorithm properties | | is_default | Default | Query shadow algorithms for specified database. ```sql SHOW SHADOW ALGORITHMS FROM shadow_db; ``` ```sql mysql> SHOW SHADOW ALGORITHMS FROM shadow_db; +-+-+--++ | shadowalgorithmname | type | props | is_default | +-+-+--++ | useridmatchalgorithm | VALUEMATCH | column=user_id,operation=insert,value=1 | false | +-+-+--++ 1 row in set (0.00 sec) ``` Query shadow algorithms for current database. ```sql SHOW SHADOW ALGORITHMS; ``` ```sql mysql> SHOW SHADOW ALGORITHMS; +-+-+--++ | shadowalgorithmname | type | props | is_default | +-+-+--++ | useridmatchalgorithm | VALUEMATCH | column=user_id,operation=insert,value=1 | false | +-+-+--++ 1 row in set (0.00 sec) ``` `SHOW`, `SHADOW`, `ALGORITHMS`, `FROM`
Project: ClickHouse (App Definition and Development / Database)
File: v20.8.15.11-lts.md

Backported in : Fix maxdistributedconnections (affects `preferlocalhostreplica=1` and `maxthreads!=maxdistributed_connections`). (). Backported in : Join tries to materialize const columns, but our code waits for them in other places. (). 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 : Fixed race on SSL object inside SecureSocket in Poco. (). Backported in : Fix a deadlock in `ALTER DELETE` mutations for non replicated MergeTree table engines when the predicate contains the table itself. Fixes . (). Backported in : Fix bug for ReplicatedMerge table engines when `ALTER MODIFY COLUMN` query doesn't change the type of decimal column if its size (32 bit or 64 bit) doesn't change. (). Backported in : Docker entrypoint: avoid chown of `.` in case when `LOG_PATH` is empty. Closes . (). Backported in : Fix waiting for `OPTIMIZE` and `ALTER` queries for `ReplicatedMergeTree` table engines. Now the query will not hang when the table was detached or restarted. (). Backported in : Now clickhouse will not throw `LOGICAL_ERROR` exception when we try to mutate the already covered part. Fixes . (). NO CL ENTRY: 'Revert "Backport to 20.8: Fix maxdistributedconnections"'. ().
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_add_port.md

title: "Command - devspace add port" sidebar_label: devspace add port Add a new port forward configuration ``` devspace add port [flags] ``` ``` Add a new port mapping to this project's devspace.yaml Format is port(:remotePort) comma separated, e.g. devspace add port 8080:80,3000 ``` ``` -h, --help help for port --label-selector string Comma separated key=value label-selector list (e.g. release=test) ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile string The devspace profile to use (if there is any) --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_list_plugins.md

title: "Command - devspace list plugins" sidebar_label: devspace list plugins Lists all installed devspace plugins ``` devspace list plugins [flags] ``` ``` Lists all installed plugins devspace list plugins ``` ``` -h, --help help for plugins ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ```
Project: YDB (App Definition and Development / Database)
File: config-info.md

`config info` is a service command for debugging various issues with . The command displays the final connection parameters, such as the and , obtained by considering parameters from all possible sources. With these parameters, the CLI would connect when executing a command that implies a connection to the database. When specifying the `-v`, in addition to the final connection parameters, values of all connection parameters from all sources that the CLI managed to detect will be displayed, along with the names of those sources in order of priority General format of the command: ```bash {{ ydb-cli }} [global options...] config info ``` `global options` . URL of database cluster. Database path. Authentication parameters:* Access Token. Refresh Token. Service Account Key. Metadata. * Root certificate. URL of IAM service. ```bash $ ydb -e grpcs://another.endpoint:2135 --ca-file some_certs.crt -p db123 config info endpoint: another.endpoint:2135 yc-token: SOMEA12****************21TOKEN iam-endpoint: iam.api.cloud.yandex.net ca-file: some_certs.crt ``` ```bash $ ydb -e grpcs://another.endpoint:2135 --ca-file some_certs.crt -p db123 -v config info Using Yandex.Cloud Passport token from YC_TOKEN env variable endpoint: another.endpoint:2135 yc-token: SOMEA12****************21TOKEN iam-endpoint: iam.api.cloud.yandex.net ca-file: some_certs.crt current auth method: yc-token "ca-file" sources: Value: some_certs.crt. Got from: explicit --ca-file option "database" sources: Value: /some/path. Got from: active profile "testconfiginfo" "endpoint" sources: Value: another.endpoint:2135. Got from: explicit --endpoint option Value: db123.endpoint:2135. Got from: profile "db123" from explicit --profile option Value: some.endpoint:2135. Got from: active profile "testconfiginfo" "iam-endpoint" sources: Value: iam.api.cloud.yandex.net. Got from: default value "sa-key-file" sources: Value: /Users/username/some-sa-key-file. Got from: active profile "testconfiginfo" "yc-token" sources: Value: SOMEA12****************21TOKEN. Got from: YC_TOKEN enviroment variable ```
Project: KICS (Provisioning / Security & Compliance)
File: d7a5616f-0a3f-4d43-bc2b-29d1a183e317.md

title: PostgreSQL Log Connections Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d7a5616f-0a3f-4d43-bc2b-29d1a183e317 Query name: PostgreSQL Log Connections Disabled Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: PostgreSQL database instance should have a 'log_connections' flag with its value set to 'on'<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="16 5" name: create instance google.cloud.gcpsqlinstance: name: GCP instance settings: databaseFlags: name: log_connections value: off tier: db-n1-standard-1 region: us-central1 project: test_project databaseversion: POSTGRES9_6 auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present name: create another instance google.cloud.gcpsqlinstance: name: GCP instance 2 settings: tier: db-n1-standard-1 region: us-central1 project: test_project databaseversion: POSTGRES9_6 auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: create a instance google.cloud.gcpsqlinstance: name: GCP instance settings: databaseFlags: name: log_connections value: on tier: db-n1-standard-1 region: us-central1 project: test_project databaseversion: POSTGRES9_6 auth_kind: serviceaccount serviceaccountfile: /tmp/auth.pem state: present ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_kms_crypto_key.md

+++ title = "googlekmscrypto_key resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlekmscrypto_key" identifier = "inspec/resources/gcp/googlekmscryptokey.md googlekmscryptokey resource" parent = "inspec/resources/gcp" +++ A `googlekmscrypto_key` is used to test a Google CryptoKey resource ```ruby describe googlekmscryptokey(project: 'chef-gcp-inspec', location: 'europe-west2', keyring_name: 'kms-key-ring', name: 'kms-key') do it { should exist } its('cryptokeyname') { should cmp 'kms-key' } its('primary_state') { should eq "ENABLED" } its('purpose') { should eq "ENCRYPT_DECRYPT" } its('nextrotationtime') { should be > Time.now - 100000 } its('create_time') { should be > Time.now - 36560602410 } end describe googlekmscryptokey(project: 'chef-gcp-inspec', location: 'europe-west2', keyring_name: 'kms-key-ring', name: "nonexistent") do it { should_not exist } end ``` describe googlekmscryptokey(project: 'chef-inspec-gcp', location: 'us-east1', keyring_name: 'key-ring', name: 'crypto-key') do its('createtimedate') { should be > Time.now - 36560602410 } end describe googlekmscryptokey(project: 'chef-inspec-gcp', location: 'us-east1', keyring_name: 'key-ring', name: 'crypto-key') do its('nextrotationtime_date') { should be > Time.now - 100000 } end describe googlekmscryptokey(project: 'chef-inspec-gcp', location: 'us-east1', keyring_name: 'key-ring', name: 'crypto-key') do its('purpose') { should eq "ENCRYPT_DECRYPT" } end describe googlekmscryptokey(project: 'chef-inspec-gcp', location: 'us-east1', keyring_name: 'key-ring', name: 'crypto-key') do its('primary_state') { should eq "ENABLED" } end Properties that can be accessed from the `googlekmscrypto_key` resource: `cryptokeyname` : The resource name for the CryptoKey. `create_time` : The time that this resource was created on the server. This is in RFC3339 text format. `labels` : Labels with user-defined metadata to apply to this resource. `purpose` : The immutable purpose of this CryptoKey. See the for possible inputs. Possible values: ENCRYPT_DECRYPT ASYMMETRIC_SIGN ASYMMETRIC_DECRYPT `rotation_period` : Every time this period passes, generate a new CryptoKeyVersion and set it as the primary. The first rotation will take place after the specified period. The rotation period has the format of a decimal number with up to 9 fractional digits, followed by the letter `s` (seconds). It must be greater than a day (ie, 86400). `version_template` : A template describing settings for new crypto key versions. `algorithm` : The algorithm to use when creating a version based on this template. See the for possible inputs. `protection_level` : The protection level to use when creating a version based on this template. Possible values: SOFTWARE HSM `nextrotationtime` : The time when KMS will create a new version of this Crypto Key. `key_ring` : The KeyRing that this key belongs to. Format: `'projects/{{project}}/locations/{{location}}/keyRings/{{keyRing}}'`. Ensure the is enabled for the current project.
Project: YDB (App Definition and Development / Database)
File: temp-table-description.md

`TEMPORARY` / `TEMP` a temporary table that is automatically deleted at the end of the session. If this parameter is not set (left empty), a permanent table is created. Any indexes created on a temporary table will also be deleted at the end of the session, which means that they are temporary as well. A temporary table and a permanent table with the same name are allowed, in which case a temporary table will be selected.
Project: MongoDB (App Definition and Development / Database)
File: burn_in_tests.md

`burnintests` detects the javascript tests (under the ) that are new or have changed since the last git command and then runs those tests in repeated mode to validate their stability. You can use `burnintests` on evergreen by selecting the `burnintests_gen` task when creating a patch, since `burnintests` task is a generated by the . `burnintests` task will be generated on each of the applicable build variants, and may have multiple sub-tasks which run the test suites only for the new or changed javascript tests (note that a javascript test can be included in multiple test suites). Each of those tests will be run 2 times minimum, and 1000 times maximum or for 10 minutes, whichever is reached first. You can also use `burnintests` locally from within the by running the script `python buildscripts/burnintests.py`. For more information about this usage, you can run `python buildscripts/burnintests.py --help`.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: entrypoint.md

Override the default ENTRYPOINT from the image. The ENTRYPOINT of an image is similar to a COMMAND because it specifies what executable to run when the container starts, but it is (purposely) more difficult to override. The ENTRYPOINT gives a container its default nature or behavior. When the ENTRYPOINT is set, the container runs as if it were that binary, complete with default options. More options can be passed in via the COMMAND. But, if a user wants to run something else inside the container, the --entrypoint option allows a new ENTRYPOINT to be specified. Specify multi option commands in the form of a json string.
Project: Flink (App Definition and Development / Streaming & Messaging)
File: set-op.md

title: "Set Operations" weight: 5 type: docs <!-- 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. --> Set Operations are used to combine multiple `SELECT` statements into a single result set. Hive dialect supports the following operations: UNION INTERSECT EXCEPT/MINUS `UNION`/`UNION DISTINCT`/`UNION ALL` returns the rows that are found in either side. `UNION` and `UNION DISTINCT` only returns the distinct rows, while `UNION ALL` does not duplicate. ```sql <query> { UNION [ ALL | DISTINCT ] } <query> [ .. ] ``` ```sql SELECT x, y FROM t1 UNION DISTINCT SELECT x, y FROM t2; SELECT x, y FROM t1 UNION SELECT x, y FROM t2; SELECT x, y FROM t1 UNION ALL SELECT x, y FROM t2; ``` `INTERSECT`/`INTERSECT DISTINCT`/`INTERSECT ALL` returns the rows that are found in both side. `INTERSECT`/`INTERSECT DISTINCT` only returns the distinct rows, while `INTERSECT ALL` does not duplicate. ```sql <query> { INTERSECT [ ALL | DISTINCT ] } <query> [ .. ] ``` ```sql SELECT x, y FROM t1 INTERSECT DISTINCT SELECT x, y FROM t2; SELECT x, y FROM t1 INTERSECT SELECT x, y FROM t2; SELECT x, y FROM t1 INTERSECT ALL SELECT x, y FROM t2; ``` `EXCEPT`/`EXCEPT DISTINCT`/`EXCEPT ALL` returns the rows that are found in left side but not in right side. `EXCEPT`/`EXCEPT DISTINCT` only returns the distinct rows, while `EXCEPT ALL` does not duplicate. `MINUS` is synonym for `EXCEPT`. ```sql <query> { EXCEPT [ ALL | DISTINCT ] } <query> [ .. ] ``` ```sql SELECT x, y FROM t1 EXCEPT DISTINCT SELECT x, y FROM t2; SELECT x, y FROM t1 EXCEPT SELECT x, y FROM t2; SELECT x, y FROM t1 EXCEPT ALL SELECT x, y FROM t2; ```
Project: KICS (Provisioning / Security & Compliance)
File: 800fa019-49dd-421b-9042-7331fdd83fa2.md

title: High Access Key Rotation Period hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 800fa019-49dd-421b-9042-7331fdd83fa2 Query name: High Access Key Rotation Period Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Secret Management URL: ConfigRule should enforce access keys to be rotated within 90 days.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" Resources: ConfigRule: Type: AWS::Config::ConfigRule Properties: ConfigRuleName: access-keys-rotated InputParameters: maxAccessKeyAge: 100 Source: Owner: AWS SourceIdentifier: ACCESSKEYSROTATED MaximumExecutionFrequency: TwentyFour_Hours ``` ```json title="Positive test num. 2 - json file" hl_lines="8" { "Resources": { "ConfigRule": { "Type": "AWS::Config::ConfigRule", "Properties": { "ConfigRuleName": "access-keys-rotated", "InputParameters": { "maxAccessKeyAge": 100 }, "Source": { "Owner": "AWS", "SourceIdentifier": "ACCESSKEYSROTATED" }, "MaximumExecutionFrequency": "TwentyFour_Hours" } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: ConfigRule: Type: AWS::Config::ConfigRule Properties: ConfigRuleName: access-keys-rotated InputParameters: maxAccessKeyAge: 90 Source: Owner: AWS SourceIdentifier: ACCESSKEYSROTATED MaximumExecutionFrequency: TwentyFour_Hours ``` ```json title="Negative test num. 2 - json file" { "Resources": { "ConfigRule": { "Type": "AWS::Config::ConfigRule", "Properties": { "MaximumExecutionFrequency": "TwentyFour_Hours", "ConfigRuleName": "access-keys-rotated", "InputParameters": { "maxAccessKeyAge": 90 }, "Source": { "SourceIdentifier": "ACCESSKEYSROTATED", "Owner": "AWS" } } } } } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.33.md

layout: release date: 2021-07-10 tag: v0.5.33 Added filter-mangement.md @sayantan1413 (#3237) Add maintainers and update code owners @navendu-pottekkat (#3398) Fix for provider_ui not showing images and favicon @sudo-NithishKarthik (#3424) [Provider UI] Fix broken logo image @leecalcote (#3425) Activity indicator: system start on kubernetes @NagaHarshita (#3256) [mesheryctl] @piyushsingariya (#3253) Feature/ayush khandelwal 007/metrics overhaul @Ayush-Khandelwal-007 (#3419) Bump next js to 11.0.1 in provider ui @sudo-NithishKarthik (#3417) Added in @dhruv0000 (#3420) integrating error codes utility into CI @DelusionalOptimist (#3296) integrating error codes utility into CI @DelusionalOptimist (#3296) Thank you to our contributors for making this release possible: @Ayush-Khandelwal-007, @DelusionalOptimist, @NagaHarshita, @Nikhil-Ladha, @dhruv0000, @leecalcote, @navendu-pottekkat, @piyushsingariya, @sayantan1413 and @sudo-NithishKarthik
Project: ClickHouse (App Definition and Development / Database)
File: template-engine.md

What the Database/Table engine does. Relations with other engines if they exist. ``` sql CREATE DATABASE ... ``` or ``` sql CREATE TABLE ... ``` Engine Parameters Query Clauses (for Table engines only) List and virtual columns with description, if they exist. | EngineName | ClickHouse | |--|| | NativeDataTypeName | | Algorithms Specifics of read and write processes Examples of tasks Recommendations for usage Specifics of data storage The example must show usage and use cases. The following text contains the recommended parts of this section. Input table: ``` text ``` Query: ``` sql ``` Result: ``` text ``` Follow up with any text to clarify the example. See Also
Project: Meshery (Provisioning / Automation & Configuration)
File: postgres-with-operator.md

layout: integration title: Postgres With Operator subtitle: Collaborative and visual infrastructure as code for Postgres With Operator image: /assets/img/integrations/postgres-with-operator/icons/color/postgres-with-operator-color.svg permalink: extensibility/integrations/postgres-with-operator docURL: https://docs.meshery.io/extensibility/integrations/postgres-with-operator description: integrations-category: Database integrations-subcategory: App Definition and Development registrant: Artifact Hub components: name: kubegres colorIcon: assets/img/integrations/postgres-with-operator/components/kubegres/icons/color/kubegres-color.svg whiteIcon: assets/img/integrations/postgres-with-operator/components/kubegres/icons/white/kubegres-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