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

layout: integration title: MySQL Operator subtitle: Collaborative and visual infrastructure as code for Mongodb Operator image: /assets/img/integrations/mysql-operator/icons/color/mysql-operator-color.svg permalink: extensibility/integrations/mysql-operator docURL: https://docs.meshery.io/extensibility/integrations/mysql-operator description: integrations-category: App Definition and Development integrations-subcategory: Database registrant: Artifact Hub components: name: inno-db-cluster colorIcon: assets/img/integrations/mysql-operator/components/inno-db-cluster/icons/color/inno-db-cluster-color.svg whiteIcon: assets/img/integrations/mysql-operator/components/inno-db-cluster/icons/white/inno-db-cluster-white.svg description: name: my-sql-backup colorIcon: assets/img/integrations/mysql-operator/components/my-sql-backup/icons/color/my-sql-backup-color.svg whiteIcon: assets/img/integrations/mysql-operator/components/my-sql-backup/icons/white/my-sql-backup-white.svg description: name: cluster-kopf-peering colorIcon: assets/img/integrations/mysql-operator/components/cluster-kopf-peering/icons/color/cluster-kopf-peering-color.svg whiteIcon: assets/img/integrations/mysql-operator/components/cluster-kopf-peering/icons/white/cluster-kopf-peering-white.svg description: name: kopf-peering colorIcon: assets/img/integrations/mysql-operator/components/kopf-peering/icons/color/kopf-peering-color.svg whiteIcon: assets/img/integrations/mysql-operator/components/kopf-peering/icons/white/kopf-peering-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: Apollo (Provisioning / Automation & Configuration)
File: quick-start-docker.md

If you are familiar with Docker, you can use the Docker way to deploy Apollo quickly, so that you can quickly understand Apollo. if you are not very familiar with Docker, please refer to the . If you are deploying Apollo in your company, please refer to the . Since Docker doesn't support windows very well, it is not recommended to use Docker way to deploy in windows environment, unless you know windows docker very well You can refer to for the specific steps, and test whether the installation is successful with the following command ``` docker -v ``` To speed up Docker image download, it is recommended to . Download and to a local directory, such as docker-quick-start. If you are using a machine with an ARM architecture, such as a Mac M1, you will need to download ```bash docker-quick-start docker-compose.yml sql apolloconfigdb.sql apolloportaldb.sql ``` Execute `docker-compose up` in the docker-quick-start directory, the first execution will trigger downloading images and other operations, you need to be patient and wait for some time. If you are using a machine with an ARM architecture, such as a Mac M1, execute `docker-compose -f docker-compose-arm64.yml up` Search all the logs starting with `apollo-quick-start` and see the following logs indicating a successful start. ```log apollo-quick-start | ==== starting service ==== apollo-quick-start | Service logging file is . /service/apollo-service.log apollo-quick-start | Started [45] apollo-quick-start | Waiting for config service startup ....... apollo-quick-start | Config service started. You may visit http://localhost:8080 for service status now! apollo-quick-start | Waiting for admin service startup...... apollo-quick-start | Admin service started apollo-quick-start | ==== starting portal ==== apollo-quick-start | Portal logging file is . /portal/apollo-portal.log apollo-quick-start | Started [254] apollo-quick-start | Waiting for portal startup ....... apollo-quick-start | Portal started. You can visit http://localhost:8070 now! ``` Note 1: The database port is mapped to 13306, so if you want to access the database on the host, you can do so via localhost:13306, username is root and password is left blank. Note 2: If you want to view more service logs, you can log in via `docker exec -it apollo-quick-start bash`, then go to `/apollo-quick-start/service` and `/apollo-quick-start/portal` to view the log information. You can refer to for the steps related to using it. Note that the Demo client needs to be run in a Docker environment with the following command. ```bash docker exec -i apollo-quick-start /apollo-quick-start/demo.sh client ``` By default apollo-configservice will only register the internal IP, only clients started by the above command will be able to connect, if you want external clients to be able to access it, please refer to the .
Project: KICS (Provisioning / Security & Compliance)
File: ae53ce91-42b5-46bf-a84f-9a13366a4f13.md

title: SNS Topic is Publicly Accessible hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ae53ce91-42b5-46bf-a84f-9a13366a4f13 Query name: SNS Topic is Publicly Accessible Platform: CloudFormation Severity: <span style="color:#ff0000">Critical</span> Category: Access Control URL: SNS Topic Policy should not allow any principal to access<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" AWSTemplateFormatVersion: '2010-09-09' Description: '' Resources: snsPolicy: Type: AWS::SNS::TopicPolicy Properties: PolicyDocument: Statement: [ { "Sid": "MyTopicPolicy", "Effect": "Allow", "Principal": "*", "Action": ["sns:Publish"], "Resource": "arn:aws:sns:MyTopic" }] ``` ```json title="Positive test num. 2 - json file" hl_lines="8" { "AWSTemplateFormatVersion": "2010-09-09", "Description": "", "Resources": { "mysnspolicy0" : { "Type" : "AWS::SNS::TopicPolicy", "Properties" : { "PolicyDocument" : { "Id" : "MyTopicPolicy", "Version" : "2012-10-17", "Statement" : [ { "Sid" : "My-statement-id", "Effect" : "Allow", "Principal" : "*", "Action" : "sns:Publish", "Resource" : "*" } ] }, "Topics" : [ { "Ref" : "MySNSTopic" } ] } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: '2010-09-09' Description: '' Resources: snsPolicy: Type: AWS::SNS::TopicPolicy Properties: PolicyDocument: Statement: [ { "Sid": "MyTopicPolicy", "Effect": "Allow", "Principal": "otherPrincipal", "Action": ["sns:Publish"], "Resource": "arn:aws:sns:MyTopic" }] ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Description": "", "Resources": { "mysnspolicy0" : { "Type" : "AWS::SNS::TopicPolicy", "Properties" : { "PolicyDocument" : { "Id" : "MyTopicPolicy", "Version" : "2012-10-17", "Statement" : [ { "Sid" : "My-statement-id", "Effect" : "Allow", "Principal" : "otherPrincipal", "Action" : "sns:Publish", "Resource" : "*" } ] }, "Topics" : [ { "Ref" : "MySNSTopic" } ] } } } } ```
Project: Harbor (Provisioning / Container Registry)
File: 6-05-OVA-collect-logs.md

Test 6-05 - OVA Collect Logs ======= To verify that the logs of an OVA version of Harbor can be retrieved. User guide, installation guide of Harbor OVA version. A running version of Harbor OVA version. A vCenter, at least an ESX host. A linux host with Docker CLI installed (Docker client). TBD TBD None
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: aws-cloudformation-hook.md

title: AWS CloudFormation Hook software: aws cloudformation labels: type: poweredbyopa tutorials: https://www.openpolicyagent.org/docs/latest/aws-cloudformation-hooks/ code: https://github.com/StyraInc/opa-aws-cloudformation-hook blogs: https://blog.styra.com/blog/the-opa-aws-cloudformation-hook inventors: styra docs_features: rest-api-integration: note: | The OPA CloudFormation Hook uses AWS Lambda to consult an OPA instance using the REST API before allowing a CloudFormation stack to be created. Read here in the OPA documentation. AWS CloudFormation Hook that uses OPA to make policy decisions on infrastructure provisioned via AWS CloudFormation
Project: StarRocks (App Definition and Development / Database)
File: array_agg.md

displayed_sidebar: "English" Aggregates values (including `NULL`) in a column into an array (multiple rows to one row), and optionally order the elements by specific columns. From v3.0, array_agg() supports using ORDER BY to sort elements. ```Haskell ARRAY_AGG([distinct] col [order by col0 [desc | asc] [nulls first | nulls last] ...]) ``` `col`: the column whose values you want to aggregate. Supported data types are BOOLEAN, TINYINT, SMALLINT, INT, BIGINT, LARGEINT, FLOAT, DOUBLE, VARCHAR, CHAR, DATETIME, DATE, ARRAY (since v3.1), MAP (since v3.1), and STRUCT (since v3.1). `col0`: the column which decides the order of `col`. There may be more than one ORDER BY column. `[desc | asc]`: specifies whether to sort the elements in ascending order (default) or descending order of `col0`. `[nulls first | nulls last]`: specifies whether null values are placed at the first or last place. Returns a value of the ARRAY type, optionally sorted by `col0`. The order of the elements in an array is random, which means it may be different from the order of the values in the column if no ORDER BY columns or no sorted by order by columns are specified. The data type of the elements in the returned array is the same as the data type of the values in the column. Returns `NULL` if the input is empty and without group-by columns. ARRAYAGGDISTINCT() is an alias of ARRAY_AGG(DISTINCT). Take the following data table as an example: ```plaintext mysql> select * from t; ++++ | a | name | pv | ++++ | 11 | | 33 | | 2 | NULL | 334 | | 1 | fzh | 3 | | 1 | fff | 4 | | 1 | fff | 5 | ++++ ``` Example 1: Group the values in column `a` and aggregate values in column `pv` into an array by ordering `a` by `name`. ```plaintext mysql> select a, array_agg(pv order by name nulls first) from t group by a; +++ | a | array_agg(pv ORDER BY name ASC) | +++ | 2 | [334] | | 11 | [33] | | 1 | [4,5,3] | +++ -- Aggregate values with no order. mysql> select a, array_agg(pv) from t group by a; +++ | a | array_agg(pv) | +++ | 11 | [33] | | 2 | [334] | | 1 | [3,4,5] | +++ 3 rows in set (0.03 sec) ``` Example 2: Aggregate values in column `pv` into an array with ordering by `name`. ```plaintext mysql> select array_agg(pv order by name desc nulls last) from t; +-+ | array_agg(pv ORDER BY name DESC) | +-+ | [3,4,5,33,334] | +-+ 1 row in set (0.02 sec) -- Aggregate values with no order. mysql> select array_agg(pv) from t; +-+ | array_agg(pv) | +-+ | [3,4,5,33,334] | +-+ 1 row in set (0.03 sec) ``` Example 3: Aggregate values in column `pv` using the WHERE clause. If no data in `pv` meets the filter condition, a `NULL` value is returned. ```plaintext mysql> select array_agg(pv order by name desc nulls last) from t where a < 0; +-+ | array_agg(pv ORDER BY name DESC) | +-+ | NULL | +-+ 1 row in set (0.02 sec) -- Aggregate values with no order. mysql> select array_agg(pv) from t where a < 0; ++ | array_agg(pv) | ++ | NULL | ++ 1 row in set (0.03 sec) ``` ARRAY_AGG, ARRAY
Project: Meshery (Provisioning / Automation & Configuration)
File: k8svault-controller.md

layout: integration title: K8s Vault Controller subtitle: Collaborative and visual infrastructure as code for K8s Vault Controller image: /assets/img/integrations/k8svault-controller/icons/color/k8svault-controller-color.svg permalink: extensibility/integrations/k8svault-controller docURL: https://docs.meshery.io/extensibility/integrations/k8svault-controller description: integrations-category: Security & Compliance integrations-subcategory: Security & Compliance registrant: Artifact Hub components: name: vault-binding colorIcon: assets/img/integrations/k8svault-controller/components/vault-binding/icons/color/vault-binding-color.svg whiteIcon: assets/img/integrations/k8svault-controller/components/vault-binding/icons/white/vault-binding-white.svg description: name: vault-mirror colorIcon: assets/img/integrations/k8svault-controller/components/vault-mirror/icons/color/vault-mirror-color.svg whiteIcon: assets/img/integrations/k8svault-controller/components/vault-mirror/icons/white/vault-mirror-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: YugabyteDB (App Definition and Development / Database)
File: delaying-execution.md

title: Functions for delaying execution [YSQL] headerTitle: Functions for delaying execution linkTitle: Delaying execution description: The semantics of the functions for delaying execution. [YSQL] menu: v2.18: identifier: delaying-execution parent: date-time-functions weight: 50 type: docs The three functions pgsleep(double precision), pgsleepfor(interval), and pgsleepuntil(timestamptz) are understood simply. The argument of pgsleep() is interpreted as the number of seconds for which to sleep. Because each has a formal parameter with a different data type, they could all have been implemented as overloads of a single function. Presumably, somebody chose to use different names somewhat whimsically. The fact that they are functions allows them to be invoked within the same SQL statement, just as the demonstration of the semantic difference between statementtimestamp() and clocktimestamp() does above. It's probably more common to use them within PL/pgSQL code. A procedure would have been more natural here than a function. But this has no practical consequence because the invocation perform pgsleep(n) comes to the rescue. Notice that you cannot declare a PL/pgSQL variable with the data type void. (The attempt causes the 0A000 error. This is mapped to the featurenotsupported exception.) If you need to include a pgsleep() invocation in a select into SQL statement in PL/pgSQL code, then you should typecast its return value to text_. (This typecast produces the empty string.) Here is a simple example: ```plpgsql select (pg_sleep(1.0::double precision)::text = '')::text; ``` The result is true. Here is a simple example: ```plpgsql select (pgsleepfor(make_interval(secs=>1))::text = '')::text; ``` The result is true. Here is a simple example: ```plpgsql select (pgsleepuntil( (clocktimestamp() + makeinterval(secs=>1))::timestamptz )::text = '')::text; ``` The result is true. Notice that pgsleepuntil() function has no overloads other than the one with the single timestamptz parameter. This is yet another reason always to use timestamptz for moment values and only to convert to other data type values on the fly if the need arises.
Project: YDB (App Definition and Development / Database)
File: load-actors-stop.md

Using this command, you can stop either entire load or only the specified part of it. | Parameter | Description | | | `Tag` | Tag of the load actor to stop. You can view the tag in the cluster Embedded UI. | | `RemoveAllTags` | If this parameter value is set to `True`, all the load actors are stopped. | The command below stops the load tagged `123`: ```proto Stop: { Tag: 123 } ``` To stop the entire load, run this command: ```proto Stop: { RemoveAllTags: true } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: istio-past-results.md

layout: past-results-layout title: Meshery-Istio Past Results permalink: installation/compatibility-matrix/meshery-istio-past-results abstract: a complete compatibility matrix and project test status dashboard. language: en display-title: "false" list: exclude type: "project" service-mesh: "meshery-istio" subheading: "Meshery-Istio"
Project: Flink (App Definition and Development / Streaming & Messaging)
File: oss.md

title: Aliyun OSS weight: 4 type: docs aliases: /deployment/filesystems/oss.html /ops/filesystems/oss.html <!-- 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. --> (Aliyun OSS) is widely used, particularly popular among Chinas cloud users, and it provides cloud object storage for a variety of use cases. You can use OSS with Flink for reading and writing data as well in conjunction with the You can use OSS objects like regular files by specifying paths in the following format: ```plain oss://<your-bucket>/<object-name> ``` Below shows how to use OSS in a Flink job: ```java // Read from OSS bucket env.readTextFile("oss://<your-bucket>/<object-name>"); // Write to OSS bucket stream.writeAsText("oss://<your-bucket>/<object-name>"); // Use OSS as checkpoint storage Configuration config = new Configuration(); config.set(CheckpointingOptions.CHECKPOINT_STORAGE, "filesystem"); config.set(CheckpointingOptions.CHECKPOINTS_DIRECTORY, "oss://<your-bucket>/<object-name>"); env.configure(config); ``` To use `flink-oss-fs-hadoop`, copy the respective JAR file from the `opt` directory to a directory in `plugins` directory of your Flink distribution before starting Flink, e.g. ```bash mkdir ./plugins/oss-fs-hadoop cp ./opt/flink-oss-fs-hadoop-{{< version >}}.jar ./plugins/oss-fs-hadoop/ ``` `flink-oss-fs-hadoop` registers default FileSystem wrappers for URIs with the oss:// scheme. After setting up the OSS FileSystem wrapper, you need to add some configurations to make sure that Flink is allowed to access your OSS buckets. To allow for easy adoption, you can use the same configuration keys in as in Hadoop's `core-site.xml` You can see the configuration keys in the . There are some required configurations that must be added to (Other configurations defined in Hadoop OSS documentation are advanced configurations which used by performance tuning): ```yaml fs.oss.endpoint: Aliyun OSS endpoint to connect to fs.oss.accessKeyId: Aliyun access key ID fs.oss.accessKeySecret: Aliyun access key secret ``` An alternative `CredentialsProvider` can also be configured in the , e.g. ```yaml fs.oss.credentials.provider: com.aliyun.oss.common.auth.EnvironmentVariableCredentialsProvider ``` Other credential providers can be found under . {{< top >}}
Project: ClickHouse (App Definition and Development / Database)
File: SECURITY.md

<!-- the file is autogenerated by utils/security-generator/generate_security.py --> Security fixes will be announced by posting them in the . The following versions of ClickHouse server are currently being supported with security updates: | Version | Supported | |:-|:-| | 24.4 | | | 24.3 | | | 24.2 | | | 24.1 | | | 23.* | | | 23.8 | | | 23.7 | | | 23.6 | | | 23.5 | | | 23.4 | | | 23.3 | | | 23.2 | | | 23.1 | | | 22.* | | | 21.* | | | 20.* | | | 19.* | | | 18.* | | | 1.* | | We're extremely grateful for security researchers and users that report vulnerabilities to the ClickHouse Open Source Community. All reports are thoroughly investigated by developers. To report a potential vulnerability in ClickHouse please send the details about it to . We do not offer any financial rewards for reporting issues to us using this method. Alternatively, you can also submit your findings through our public bug bounty program hosted by and be rewarded for it as per the program scope and rules of engagement. You think you discovered a potential security vulnerability in ClickHouse You are unsure how a vulnerability affects ClickHouse You need help tuning ClickHouse components for security You need help applying security related updates Your issue is not security related Each report is acknowledged and analyzed by ClickHouse maintainers within 5 working days. As the security issue moves from triage, to identified fix, to release planning we will keep the reporter updated. A public disclosure date is negotiated by the ClickHouse maintainers and the bug submitter. We prefer to fully disclose the bug as soon as possible once a user mitigation is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination. The timeframe for disclosure is from immediate (especially if it's already publicly known) to 90 days. For a vulnerability with a straightforward mitigation, we expect the report date to disclosure date to be on the order of 7 days.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_backup.md

title: kbcli backup Backup command. ``` -h, --help help for backup ``` ``` --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 ``` - Create a backup for the cluster. - Delete a backup. - Describe a backup - List backups.
Project: YugabyteDB (App Definition and Development / Database)
File: 14-intersect.md

title: "INTERSECT" In this exercise we will query the orders and country tables and return the result sets that are found in both tables. ``` SELECT ship_country FROM orders INTERSECT SELECT country FROM suppliers; ``` This query should return 12 rows In this exercise we will query the orders and country tables, return the result sets that are found in both tables and oder them by ship\country_. ``` SELECT ship_country FROM orders INTERSECT SELECT country FROM suppliers ORDER BY ship_country; ``` This query should return 12 rows