cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: d0f7da39-a2d5-4c78-bb85-4b7f338b3cbb.md

title: SQL DB Instance With SSL Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d0f7da39-a2d5-4c78-bb85-4b7f338b3cbb Query name: SQL DB Instance With SSL Disabled Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: Cloud SQL Database Instance should have SSL enabled<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="24 3 13 39" name: create a instance google.cloud.gcpsqlinstance: name: "{{ resource_name }}-2" region: us-central1 project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present name: create a second instance google.cloud.gcpsqlinstance: name: "{{ resource_name }}-2" settings: tier: db-n1-standard-1 region: us-central1 project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present name: create a third instance google.cloud.gcpsqlinstance: name: "{{ resource_name }}-2" settings: ip_configuration: authorized_networks: name: google dns server value: 8.8.8.8/32 tier: db-n1-standard-1 region: us-central1 project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present name: create a forth instance google.cloud.gcpsqlinstance: name: "{{ resource_name }}-2" settings: ip_configuration: require_ssl: no authorized_networks: name: google dns server value: 8.8.8.8/32 tier: db-n1-standard-1 region: us-central1 project: test_project 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: '{{ resource_name }}-2' settings: ip_configuration: require_ssl: yes authorized_networks: name: google dns server value: 8.8.8.8/32 tier: db-n1-standard-1 region: us-central1 project: test_project auth_kind: serviceaccount serviceaccountfile: /tmp/auth.pem state: present ```
Project: KubeZoo (Provisioning / Automation & Configuration)
File: manually-setup.md

This tutorial introduces how to setup KubeZoo on Kubernetes. KubeZoo should work with any standard Kubernetes cluster out of box, but for demo purposes, in this tutorial, we will use a `kind` cluster as the upstream cluster. Please install the latest version of Run the following command to create local kubezoo enviroment ```console make local-up ``` When all processes are ready, kubezoo will run on local port 6443, make sure that port is not occupied by another application and you will see the following output ``` Export kubezoo server to 6443 Forwarding from 127.0.0.1:6443 -> 6443 Forwarding from [::1]:6443 -> 6443 ``` ```console $ kubectl api-resources --context zoo NAME SHORTNAMES APIVERSION NAMESPACED KIND ... tenants tenant.kubezoo.io/v1alpha1 false Tenant ``` ```console $ kubectl apply -f config/setup/sample_tenant.yaml --context zoo tenant.tenant.kubezoo.io/111111 created ``` The tenant name must be a valid 6-character DNS label prefix (`{5}`). ```console $ kubectl get tenant 111111 --context zoo -o jsonpath='{.metadata.annotations.kubezoo\.io\/tenant\.kubeconfig\.base64}' | base64 --decode > 111111.kubeconfig ``` ```console $ kubectl apply --kubeconfig 111111.kubeconfig -f- <<EOF apiVersion: v1 kind: Pod metadata: name: test spec: containers: name: test image: busybox command: tail args: -f /dev/null resources: limits: cpu: 0.5 memory: '0.5Gi' requests: cpu: 0.5 memory: '0.5Gi' EOF pod/test created ``` Get the pod as the tenant ```console $ kubectl get po --kubeconfig 111111.kubeconfig NAME READY STATUS RESTARTS AGE test 1/1 Running 0 44s ``` Get the pod as the cluster administrator ```console $ kubectl get po -A NAMESPACE NAME READY STATUS RESTARTS AGE 111111-default test 1/1 Running 0 2m28s default kubezoo-0 1/1 Running 0 34m default kubezoo-etcd-0 1/1 Running 0 34m default test 1/1 Running 0 2m41s ... ```
Project: KICS (Provisioning / Security & Compliance)
File: 9b83114b-b2a1-4534-990d-06da015e47aa.md

title: Lambda Permission Misconfigured hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9b83114b-b2a1-4534-990d-06da015e47aa Query name: Lambda Permission Misconfigured Platform: CloudFormation Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: Lambda permission may be misconfigured if the action field is not filled in by 'lambda:InvokeFunction'<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="6" Resources: s3Permission: Type: AWS::Lambda::Permission Properties: FunctionName: !GetAtt function.Arn Action: lambda:GetFunction Principal: s3.amazonaws.com SourceAccount: !Ref 'AWS::AccountId' SourceArn: !GetAtt bucket.Arn ``` ```json title="Positive test num. 2 - json file" hl_lines="8" { "Resources": { "s3Permission": { "Type": "AWS::Lambda::Permission", "Properties": { "SourceArn": "bucket.Arn", "FunctionName": "function.Arn", "Action": "lambda:GetFunction", "Principal": "s3.amazonaws.com", "SourceAccount": "AWS::AccountId" } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: s3Permission: Type: AWS::Lambda::Permission Properties: FunctionName: !GetAtt function.Arn Action: lambda:InvokeFunction Principal: s3.amazonaws.com SourceAccount: !Ref 'AWS::AccountId' SourceArn: !GetAtt bucket.Arn ``` ```json title="Negative test num. 2 - json file" { "Resources": { "s3Permission": { "Type": "AWS::Lambda::Permission", "Properties": { "FunctionName": "function.Arn", "Action": "lambda:InvokeFunction", "Principal": "s3.amazonaws.com", "SourceAccount": "AWS::AccountId", "SourceArn": "bucket.Arn" } } } } ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.10.23.md

RabbitMQ `3.10.23` is a maintenance release in the `3.10.x` . This series . Please refer to the upgrade section from if upgrading from a version prior to 3.10.0. This release requires Erlang 24.3 and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang versions older than 24.3 have reached . This release of RabbitMQ or later versions. Nodes will fail to start on older Erlang releases. Erlang 25.3 is recommended: it offers much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation. Release notes can be found on GitHub at . Make-based source package builds were failing in an offline environment. GitHub issue: Make-based source package builds were failing in an offline environment. GitHub issue: URI parser incorrectly used the `password` query parameter to override the password value in authority (user info) part. The `password` query parameter can be used to specify private key password for upstream connections that use TLS. GitHub issue: URI parser incorrectly used the `password` query parameter to override the password value in authority (user info) part. The `password` query parameter can be used to specify private key password for Shovels that use TLS. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.10.23.tar.xz` instead of the source tarball produced by GitHub.
Project: Meshery (Provisioning / Automation & Configuration)
File: kubedl.md

layout: integration title: Kubedl subtitle: Collaborative and visual infrastructure as code for Kubedl image: /assets/img/integrations/kubedl/icons/color/kubedl-color.svg permalink: extensibility/integrations/kubedl docURL: https://docs.meshery.io/extensibility/integrations/kubedl description: integrations-category: Provisioning integrations-subcategory: Automation & Configuration registrant: Artifact Hub components: 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: general-issues.md

title: General guidelines linkTitle: General headcontent: What to watch out for when migrating data from MySQL, Oracle, or PostgreSQL description: Review limitations and suggested workarounds for migrating data from MySQL, Oracle, or PostgreSQL. menu: preview_yugabyte-voyager: identifier: general-issues parent: known-issues weight: 100 type: docs rightNav: hideH3: true Review limitations and implement suggested workarounds to successfully migrate data from MySQL, Oracle, or PostgreSQL to YugabyteDB. GitHub: Description: If there is an index on a timestamp column, the index should be imported as a range index automatically, as most queries relying on timestamp columns use range predicates. This avoids sequential scans and makes indexed scans accessible. Workaround: Manually add the ASC (range) clause to the exported files. Example An example schema on the source database is as follows: ```sql CREATE INDEX ON timestamp_demo (ts); ``` Suggested change to the schema is to add the `ASC` clause as follows: ```sql CREATE INDEX ON timestamp_demo (ts ASC); ``` GitHub: , , Description: If you define complex names for your source database tables/functions/procedures using backticks or double quotes for example, \`abc xyz\` , \`abc@xyz\`, or "abc@123", the migration hangs during the export data step. Workaround: Rename the objects (tables/functions/procedures) on the source database to a name without special characters. Example An example schema on the source MySQL database is as follows: ```sql CREATE TABLE `xyz abc`(id int); INSERT INTO `xyz abc` VALUES(1); INSERT INTO `xyz abc` VALUES(2); INSERT INTO `xyz abc` VALUES(3); ``` The exported schema is as follows: ```sql CREATE TABLE "xyz abc" (id bigint); ``` The preceding example may hang or result in an error. GitHub: Description: If you migrate your database using a case-sensitive schema name, the migration will fail with a "no schema has been selected" or "schema already exists" error(s). Workaround: Currently, yb-voyager does not support case-sensitive schema names; all schema names are assumed to be case-insensitive (lower-case). If required, you may alter the schema names to a case-sensitive alternative post-migration using the ALTER SCHEMA command. Example An example yb-voyager import-schema command with a case-sensitive schema name is as follows: ```sh yb-voyager import schema --target-db-name voyager --target-db-hostlocalhost --export-dir . --target-db-password password --target-db-user yugabyte --target-db-schema "\"Test\"" ``` The preceding example will result in an error as follows: ```output ERROR: no schema has been selected to create in (SQLSTATE 3F000) ``` Suggested changes to the schema can be done using the following steps: Change the case sensitive schema name during schema migration as follows: ```sh yb-voyager import schema --target-db-name voyager --target-db-hostlocalhost --export-dir . --target-db-password password --target-db-user yugabyte --target-db-schema test ``` Alter the schema name post migration as follows: ```sh ALTER SCHEMA "test" RENAME TO "Test"; ```
Project: ClickHouse (App Definition and Development / Database)
File: grants.md

slug: /en/operations/system-tables/grants Privileges granted to ClickHouse user accounts. Columns: `user_name` (()) User name. `role_name` (()) Role assigned to user account. `access_type` () Access parameters for ClickHouse user account. `database` (()) Name of a database. `table` (()) Name of a table. `column` (()) Name of a column to which access is granted. `ispartialrevoke` () Logical value. It shows whether some privileges have been revoked. Possible values: `0` The row describes a partial revoke. `1` The row describes a grant. `grant_option` () Permission is granted `WITH GRANT OPTION`, see .
Project: Presto (App Definition and Development / Database)
File: hudi-testing-data.md

The archive file `hudi-testing-data.zip` contains data files for 4 Hudi tables. `stocktickscow`: a partitioned copy-on-write table `stocktickscown`: a non-partitioned copy-on-write table `stockticksmor`: a partitioned merge-on-read table `stockticksmorn`: a non-partitioned merge-on-read table `stockticksmornonlylog`: a non-partitioned merge-on-read table with only log files In `HudiTestingDataGenerator`, each merge-on-read table creates two table entries into hive metastore (one table name suffixed `ro` and the other suffixed `rt`), as hudi-hive-sync tool does. The table data is generated following the doc at https://hudi.apache.org/docs/docker_demo/ All the tables have the same data columns: | Name | Type | |--|| | volume | bigint | | ts | varchar | | symbol | varchar | | year | integer | | month | varchar | | high | double | | low | double | | key | varchar | | date | varchar | | close | double | | open | double | | day | varchar | Each partitioned table has a partition column, named `dt`, of type `varchar`, and has partition named `dt=2018-08-31` at the subdirectory `2018/08/31`.
Project: ClickHouse (App Definition and Development / Database)
File: v23.10.4.25-stable.md

sidebar_position: 1 sidebar_label: 2023 Backported in : In the setup plan started to appear in the logs. It should be only in the `runnergetall_tests.log` only. As well, send the failed infrastructure event to CI db. (). Backported in : Do not fetch changed submodules in the builder container. (). Select from system tables when table based on table function. (). Fix restore from backup with `flattennested` and `datatypedefaultnullable` (). Fix segfault during Kerberos initialization (). Fix: RabbitMQ OpenSSL dynamic loading issue (). Fix crash in GCD codec in case when zeros present in data (). Fix crash in FPC codec (). Rewrite jobs to use callable workflow (). Continue rewriting workflows to reusable tests (). Better exception messages ().
Project: KICS (Provisioning / Security & Compliance)
File: 6ad087d7-a509-4b20-b853-9ef6f5ebaa98.md

title: CloudTrail Multi Region Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6ad087d7-a509-4b20-b853-9ef6f5ebaa98 Query name: CloudTrail Multi Region Disabled Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: CloudTrail multi region should be enabled, which means attribute 'ismultiregion_trail' should be set to true<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" name: example1 community.aws.cloudtrail: state: present name: default s3bucketname: mylogbucket region: us-east-1 ismultiregion_trail: false enablelogfile_validation: true cloudwatchlogsrolearn: "arn:aws:iam::123456789012:role/CloudTrailCloudWatchLogs_Role" cloudwatchlogsloggrouparn: "arn:aws:logs:us-east-1:123456789012:log-group:CloudTrail/DefaultLogGroup:*" kmskeyid: "alias/MyAliasName" tags: environment: dev Name: default ``` ```yaml title="Negative test num. 1 - yaml file" name: example1 community.aws.cloudtrail: state: present name: default s3bucketname: mylogbucket region: us-east-1 ismultiregion_trail: true enablelogfile_validation: true cloudwatchlogsrolearn: arn:aws:iam::123456789012:role/CloudTrailCloudWatchLogs_Role cloudwatchlogsloggrouparn: arn:aws:logs:us-east-1:123456789012:log-group:CloudTrail/DefaultLogGroup:* kmskeyid: alias/MyAliasName tags: environment: dev Name: default ```
Project: secureCodeBox (Provisioning / Security & Compliance)
File: scanner-test.md

title: "Scanner Testing" sidebar_position: 3 We employ two types of tests: Unit tests for the parser and integration-tests. Both types of tests are based upon the testing framework. Each scanner has a parser and each parser has a unit test file. The unit test file is named parser.test.js. This file contains different test scenarios. In each test, the results from parser.js and the folder `snapshots` are compared. If they are the same, the unit test is successful. A unit test can look like this: ```js test("parser parses large json result without vulnerable extensions successfully", async () => { const fileContent = await readFile( dirname + "/testFiles/localhost.json", { encoding: "utf8", } ); const findings = await parse(JSON.parse(fileContent)); await expect(validateParser(findings)).resolves.toBeUndefined(); expect(findings).toMatchSnapshot(); }); ``` This test for example expects a test file, i.e a raw scanner output, to be found in `/testFiles/localhost.json` To run a unit-test it suffices to run ```bash make unit-tests ``` in the scanner directory. Each scanner has a folder with integration tests. For the integration tests we check the results of the `scan` function. This function runs an actual SCB scan in the Kind Cluster (Through the ). It expects the following parameters: Name of the scan, scanType, scanner-specific parameters for the scan and the allowed timeout. An integration test for, for example, the amass scanner looks like this: ```js test( "amass should find at least 20 subdomains", async () => { const { count } = await scan( "amass-scanner-dummy-scan", "amass", ["-passive", "-noalts", "-norecursive", "-d", "owasp.org"], 180 ); expect(count).toBeGreaterThanOrEqual(20); }, 6 60 1000 ); ``` For this test to be considered successful, it has to match the expected condition. In this case, the condition is that the count of the findings is greater or equal to 20. To run the test it suffices to run: ```bash make test ``` All previous tests will be deleted and the current test will be run on a clean slate. If no clean install is needed before running the test, it is possible to run only the tests themselves through: ```bash make integration-tests ```
Project: Kraken (Provisioning / Container Registry)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Environments e.g Kuberenetes, AWS, GCP, Data centers, laptop, etc. Additional context Add any other context about the problem here--environment configurations, logs, etc.
Project: YugabyteDB (App Definition and Development / Database)
File: superblocks.md

title: Use Superblocks with YugabyteDB YSQL headerTitle: Superblocks linkTitle: Superblocks description: Use Superblocks to work with distributed SQL databases in YugabyteDB. menu: preview_integrations: identifier: superblocks parent: development-platforms weight: 900 type: docs is a programmable IDE for building internal applications. It allows users to connect to various data sources in order to create rich user interfaces, automate workflows, and schedule jobs. Superblocks provides many integrations, including PostgreSQL. Superblocks can connect to YugabyteDB as its underlying data source by creating a . Your YugabyteDB cluster should be up and running. Refer to . To connect to YugabyteDB, create a new Postgres integration in Superblocks as follows: Supply a name for your integration. Add the host address of your YugabyteDB instance. Change the port from `5432` to `5433`. Change the database name to that of your YugabyteDB instance. Provide the password for your YugabyteDB instance. Optionally, to connect via SSL, provide the CA certificate. If your cluster is in YugabteDB Managed, be sure to add the listed IP addresses to the cluster . With a valid Postgres integration, you can now query your YugabyteDB instance in Superblocks.
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_debug_elasticsearch.md

title: Kubectl-Dba Debug Elasticsearch menu: docs_{{ .version }}: identifier: kubectl-dba-debug-elasticsearch name: Kubectl-Dba Debug Elasticsearch parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Debug helper for elasticsearch database ``` kubectl-dba debug elasticsearch [flags] ``` ``` kubectl dba debug elasticsearch -n demo sample-elasticsearch --operator-namespace kubedb ``` ``` -h, --help help for elasticsearch -o, --operator-namespace string the namespace where the kubedb operator is installed (default "kubedb") ``` ``` --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/runner/.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 --default-seccomp-profile-type string Default seccomp profile --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 --password string Password for basic authentication to the API server --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 --username string Username for basic authentication to the API server ``` - Debug any Database issue