cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 61cf9883-1752-4768-b18c-0d57f2737709.md

title: EKS Cluster Has Public Access CIDRs hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 61cf9883-1752-4768-b18c-0d57f2737709 Query name: EKS Cluster Has Public Access CIDRs Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: Amazon EKS public endpoint is enables and accessible to all: 0.0.0.0/0"<br> ```tf title="Positive test num. 1 - tf file" hl_lines="8 30" resource "awsekscluster" "positive1" { name = "example" rolearn = awsiam_role.example.arn vpc_config { subnetids = [awssubnet.example1.id, aws_subnet.example2.id] endpointpublicaccess = true publicaccesscidrs = ["0.0.0.0/0"] } depends_on = [ awsiamrolepolicyattachment.example-AmazonEKSClusterPolicy, ] } output "endpoint" { value = awsekscluster.example.endpoint } output "kubeconfig-certificate-authority-data" { value = awsekscluster.example.certificate_authority[0].data } resource "awsekscluster" "positive2" { name = "without_example" rolearn = awsiam_role.example.arn vpc_config { subnetids = [awssubnet.example1.id, aws_subnet.example2.id] endpointpublicaccess = true } depends_on = [ awsiamrolepolicyattachment.example-AmazonEKSClusterPolicy, ] } ``` ```tf title="Negative test num. 1 - tf file" resource "awsekscluster" "negative1" { name = "example" rolearn = awsiam_role.example.arn vpc_config { subnetids = [awssubnet.example1.id, aws_subnet.example2.id] endpointpublicaccess = true publicaccesscidrs = ["1.1.1.1/1"] } depends_on = [ awsiamrolepolicyattachment.example-AmazonEKSClusterPolicy, ] } output "endpoint" { value = awsekscluster.example.endpoint } output "kubeconfig-certificate-authority-data" { value = awsekscluster.example.certificate_authority[0].data } ```
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: README.md

This module is the seatunnel job entrypoint. SeaTunnel jobs are started by the below process. seatunnel-core-flink: The flink job starter. seatunnel-core-flink-sql: The flink sql job starter. seatunnel-core-spark: The spark job starter. seatunnel-spark-starter: The spark job starter for connector-v2. seatunnel-flink-starter: The flink job starter for connector-v2. seatunnel-starter: The seatunnel engine job starter for connector-v2.
Project: Meshery (Provisioning / Automation & Configuration)
File: fbug_report.md

name: General Bug Report about: Report an issue to help improve the project. title: '' labels: 'kind/bug' assignees: '' <!-- A brief description of the issue. --> <!-- A brief description of what you expected to happen. --> <!-- Add screenshots, if applicable, to help explain your problem. --> Host OS: Mac Linux Windows Platform: Docker or Kubernetes Meshery Server Version: stable-v Meshery Client Version: stable-v <!-- Optional Go to '...' Click on '....' Scroll down to '....' See error --> - Meshery documentation and Wireframes and in Figma Questions: and
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.169.md

layout: release date: 2023-11-02 tag: v0.6.169 [Server] Pattern API response @MUzairS15 (#9292) [UI] Fixed styling of Unauthenticated Modal @captain-Akshay (#9290) Fixes in Connections/MeshSync tables @sudhanshutech (#9265) [UI] Make the eventActors avatar overlapping stack @aabidsofi19 (#9264) fix: Dashboard card missing title and background @MeenuyD (#9243) Thank you to our contributors for making this release possible: @Aisuko, @MUzairS15, @MeenuyD, @aabidsofi19, @captain-Akshay, @leecalcote, @sudhanshutech and @theBeginner86
Project: KOTS (App Definition and Development / Application Definition & Image Build)
File: README.md

This is a working demo for packaging Sentry as a Kots application. Create a new Kots application in the Create a new application, name it, and select 'Kots' when asked "How do you want to package your application?". If the Kots option is not visible, email contact@replicated.com and we'll enable it. Select the 'Releases' tab of the vendor portal, delete the default yaml files and upload all the files from the `manifests` directory of this repo. These files include plain Kubernetes yaml for sample app (Sentry), along with the following Kots-specific yaml specs: replicated-app.yaml - specifies application title and icon, for display in the kots admin console preflight.yaml - specifies tests to run against the target cluster, prior to deployment of the app support-bundle.yaml - specifies how custom diagnostic info should be collected, analyzed, and displayed Create a release, and promote that release to a deployment channel Create a customer and download an application license Select the Customers option on the left menu, create a new customer, and assign the customer to a channel. Select the Channels option from the left menu, and review the 'Install' command, which will show `your-app-slug` and a Replicated URL to install with Kots. Install the Kots kubectl plugin ```shell curl https://kots.io/install | bash ``` Test the deployment: Choose `your-namespace` which will be the namespace for every component of the deployed application and the kots admin console ```shell kubectl kots install replicated://your-app-slug --namespace your-namespace ``` You will be prompted to provide a password (to control access to the admin console), and then to connect to http://localhost:8800 , where you can login with the password you just specified, and then upload the customer license. Clean up ```shell kubectl delete ns your-namespace ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_kms_crypto_key_iam_policy.md

+++ title = "googlekmscryptokeyiam_policy resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlekmscryptokeyiam_policy" identifier = "inspec/resources/gcp/googlekmscryptokeyiampolicy.md googlekmscryptokeyiampolicy resource" parent = "inspec/resources/gcp" +++ A `googlekmscryptokeyiam_policy` is used to test a Google CryptoKey Iam Policy resource ```ruby describe googlekmscryptokeyiampolicy(project: "project", location: "location", keyringname: "keyringname", cryptokeyname: "cryptokey_name") do it { should exist } end googlekmscryptokeyiampolicy(project: "project", location: "location", keyringname: "keyringname", cryptokeyname: "cryptokey_name").bindings.each do |binding| describe binding do its('role') { should eq 'roles/editor'} its('members') { should include 'user:testuser@example.com'} end end ``` Properties that can be accessed from the `googlekmscryptokeyiam_policy` resource: `iambindingroles` : The list of roles that exist on the policy. `bindings` : Associates a list of members to a role. `role` : Role that is assigned to members. For example, roles/viewer, roles/editor, or roles/owner. `members` : Specifies the identities requesting access for a Cloud Platform resource. `audit_configs` : Specifies cloud audit logging configuration for this policy. `service` : Specifies a service that will be enabled for audit logging. For example, `storage.googleapis.com`, `cloudsql.googleapis.com`. `allServices` is a special value that covers all services. `auditlogconfigs` : The configuration for logging of each type of permission. `log_type` : The log type that this config enables. For example, ADMINREAD, DATAWRITE or DATA_READ `exempted_members` : Specifies the identities that do not cause logging for this type of permission. Ensure the is enabled for the current project.
Project: YugabyteDB (App Definition and Development / Database)
File: superset.md

title: Use Apache Superset with YugabyteDB YSQL headerTitle: Apache Superset linkTitle: Apache Superset description: Use Apache Superset to explore and visulize data in YugabyteDB. menu: v2.18: identifier: superset parent: tools weight: 20 type: docs is an open-source data exploration and visualization tool that helps you query data stored in YugabyteDB and visualize it using basic line charts to highly detailed geospatial charts. You can use Superset to quickly explore and visualize data stored in databases and data warehouses. You can explore data without writing complex SQL queries, create rich reports and custom dashboards to visualize this data, and get insights quickly. Your YugabyteDB cluster should be up and running. Refer to . You also need to load a relevant database in your YugabyteDB for exploration and visualization. For a local installation, you can load the Northwind sample database with the `./bin/yugabyted demo connect` command from your shell, or you can follow the . You can install Superset using (recommended) or from scratch using . Launch Superset in your browser at `http://<hostname-or-IP-address>:8088`. If you've installed on your local computer, navigate to `localhost:8088` or `127.0.0.1:8088`. Superset comes with a standard PostgreSQL driver that also connects to YugabyteDB. You can also manually install the to connect to YugabyteDB. To connect Apache Superset to YugabyteDB: Navigate to Data > Databases > + Databases, and choose PostgreSQL from the Connect a database menu. Enter your YugabyteDB tablet server's hostname or IP address with standard credentials and click Finish. {{< note title="Note" >}} As of Docker version 18.03, the `host.docker.internal` hostname connects to your Docker host from inside a Docker container. {{< /note >}} Verify that you can access the available databases and schemas under "Data". Navigate to Data > Datasets, and click "+Datasets". The dropdown list should show the databases and schemas available to explore and visualize. You've successfully created a connection to your YugabyteDB database, and you can now start exploring and visualizing your databases using Apache Superset. Refer to the Apache to learn more about Superset's data exploration capabilities. If you're creating your first dashboard using Superset, check out the .
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: contributing.md

If you're interested in contributing to Monokle Desktop that's great - we love you! Please follow these steps to get started: Read our . Fork/clone the Monokle Desktop repo and make sure you can build/run Monokle Desktop as described in . Have a look at the high-level document to get an overview of Monokle Desktop's architecture. Either start working on an idea of your own that you would like to contribute - or have a look at the - focus on those assigned to an upcoming . To help you find a good issue to start with we have labeled easy issues with . Once you've found an issue, fork / clone the Monokle Desktop repo and start working on it, and let us know by commenting on the issue (so we don't start working on it also). Once you've implemented the issue open a PR back to the Monokle Desktop repo so we can review and give you feedback. When all is good we will approve the PR so it can be merged. If you've decided to move on to even greater things without finishing the issue that's fine also (kudos for dedicating some time to an open-source project!), let us know so we can plan accordingly! Always feel free to reach out to us on our if you have any questions on any of the above - or anything else Monokle Desktop-related. Thank you!
Project: YDB (App Definition and Development / Database)
File: init.md

title: "Instructions for initializing the driver in {{ ydb-short-name }}" description: "The article describes the examples of the code for connecting to {{ ydb-short-name }} (driver creation) in different {{ ydb-short-name }} SDKs." {% include %} To connect to {{ ydb-short-name }}, you need to specify the required and additional parameters that define the driver's behavior (learn more in ). Below are examples of the code for connecting to {{ ydb-short-name }} (driver creation) in different {{ ydb-short-name }} SDKs. {% list tabs %} Go (native) ```golang package main import ( "context" "github.com/ydb-platform/ydb-go-sdk/v3" ) func main() { ctx, cancel := context.WithCancel(context.Background()) defer cancel() db, err := ydb.Open(ctx, "grpc://localhost:2136/local") if err != nil { panic(err) } defer db.Close() // ... } ``` Go (database/sql) {% cut "Using a connector (recommended)" %} ```golang package main import ( "context" "database/sql" "os" "github.com/ydb-platform/ydb-go-sdk/v3" ) func main() { ctx, cancel := context.WithCancel(context.Background()) defer cancel() nativeDriver, err := ydb.Open(ctx, os.Getenv("YDBCONNECTIONSTRING"), ) if err != nil { panic(err) } defer nativeDriver.Close(ctx) connector, err := ydb.Connector(nativeDriver) if err != nil { panic(err) } defer connector.Close() db := sql.OpenDB(connector) defer db.Close() // ... } ``` {% endcut %} {% cut "Using a connection string" %} The `database/sql` driver is registered when importing the package of a specific driver separated by an underscore: ```golang package main import ( "database/sql" _ "github.com/ydb-platform/ydb-go-sdk/v3" ) func main() { db, err := sql.Open("ydb", "grpc://localhost:2136/local") if err != nil { panic(err) } defer db.Close() // ... } ``` {% endcut %} Java {% include %} C# (.NET) ```C# using Ydb.Sdk; var config = new DriverConfig( endpoint: "grpc://localhost:2136", database: "/local" ); await using var driver = await Driver.CreateInitialized(config); ``` PHP ```php <?php use YdbPlatform\Ydb\Ydb; $config = [ // Database path 'database' => '/ru-central1/b1glxxxxxxxxxxxxxxxx/etn0xxxxxxxxxxxxxxxx', // Database endpoint 'endpoint' => 'ydb.serverless.yandexcloud.net:2135', // Auto discovery (dedicated server only) 'discovery' => false, // IAM config 'iam_config' => [ // 'rootcertfile' => './CA.pem', // Root CA file (uncomment for dedicated server) ], 'credentials' => new \YdbPlatform\Ydb\Auth\Implement\AccessTokenAuthentication('AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA') // use from reference/ydb-sdk/auth ]; $ydb = new Ydb($config); ``` {% endlist %}
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_sql_database_instances.md

+++ title = "googlesqldatabase_instances resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlesqldatabase_instances" identifier = "inspec/resources/gcp/googlesqldatabaseinstances.md googlesqldatabaseinstances resource" parent = "inspec/resources/gcp" +++ A `googlesqldatabase_instances` is used to test a Google DatabaseInstance resource ```ruby describe googlesqldatabase_instances(project: 'chef-gcp-inspec') do its('instance_states') { should include 'RUNNABLE' } its('instance_names') { should include 'my-database' } end ``` describe googlesqldatabase_instances(project: 'chef-inspec-gcp') do its('count') { should be <= 100} end describe googlesqldatabase_instances(project: 'chef-inspec-gcp') do its('instance_zones') { should include "us-east1-b" } end describe googlesqldatabase_instances(project: 'chef-inspec-gcp') do its('instance_regions') { should include "us-east1" } end describe googlesqldatabase_instances(project: 'chef-inspec-gcp') do its('instance_states') { should include "RUNNABLE" } end googlesqldatabaseinstances(project: 'chef-inspec-gcp').where(instancename: /mysqldb/).instancenames.each do |instancename| describe googlesqldatabaseinstance(project: 'chef-inspec-gcp', database: instancename) do it { should exist } its('databaseversion') { should eq "MYSQL5_7" } end end Properties that can be accessed from the `googlesqldatabase_instances` resource: See the resource for more information. `backend_types` : an array of `googlesqldatabaseinstance` backendtype `connection_names` : an array of `googlesqldatabaseinstance` connectionname `instance_versions` : an array of `googlesqldatabaseinstance` databaseversion `failover_replicas` : an array of `googlesqldatabaseinstance` failoverreplica `instance_types` : an array of `googlesqldatabaseinstance` instancetype `ip_addresses` : an array of `googlesqldatabaseinstance` ipaddresses `ipv6_addresses` : an array of `googlesqldatabaseinstance` ipv6address `masterinstancenames` : an array of `googlesqldatabaseinstance` masterinstance_name `maxdisksizes` : an array of `googlesqldatabaseinstance` maxdisk_size `instance_names` : an array of `googlesqldatabase_instance` name `instance_regions` : an array of `googlesqldatabase_instance` region `replica_configurations` : an array of `googlesqldatabaseinstance` replicaconfiguration `settings` : an array of `googlesqldatabase_instance` settings `instance_zones` : an array of `googlesqldatabaseinstance` gcezone `instance_states` : an array of `googlesqldatabase_instance` state 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.
Project: external-secrets (Provisioning / Security & Compliance)
File: vault.md

The `VaultDynamicSecret` Generator provides an interface to HashiCorp Vault's . Specifically, it enables obtaining dynamic secrets not covered by the . Any Vault authentication method supported by the provider can be used here (`provider` block of the spec). All secrets engines should be supported by providing matching `path`, `method` and `parameters` values to the Generator spec (see example below). Exact output keys and values depend on the Vault secret engine used; nested values are stored into the resulting Secret in JSON format. ```yaml {% include 'generator-vault.yaml' %} ``` Example `ExternalSecret` that references the Vault generator: ```yaml {% include 'generator-vault-example.yaml' %} ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.58.md

layout: release date: 2021-09-17 tag: v0.5.58 fix seed content registration bugs @DelusionalOptimist (#4205) [Extension] RJSF - remove description and add tooltip to fields @bariqhibat (#4171) Fix meshery-operator helm chart @panyuenlau (#4196) Added Connectivity check for NATS and MeshSync + Minor Refactor @dhruv0000 (#4191) fixed ui tests failing @warunicorn19 (#4194) Added support for seeded content in local provider @Revolyssup (#4173) tag for k8s - channel switch @suhaniii (#4132) mesheryctl: Fix system start --reset to reset the meshconfig before s @amitech (#4166) Added more tests for `mesheryctl/internal/cli/root/config` @shikharvashistha (#4084) Added more tests for `mesheryctl/internal/cli/root/config` @shikharvashistha (#4084) fix: broken link in adapters @Shatakshi0805 (#4175) Thank you to our contributors for making this release possible: @DelusionalOptimist, @Revolyssup, @Shatakshi0805, @amitech, @bariqhibat, @dhruv0000, @leecalcote, @navendu-pottekkat, @panyuenlau, @piyushsingariya, @shikharvashistha, @sudo-NithishKarthik, @suhaniii, @utkarsh-pro and @warunicorn19
Project: Apache RocketMQ (App Definition and Development / Streaming & Messaging)
File: Design_Filter.md

RocketMQ - a distributed message queue, is different with all other MQ middleware, on the way of filtering messages. It's do the filter when the messages are subscribed via consumer side.RocketMQ do it lies in the separate storage mechanism that Producer side writing messages and Consumer subscribe messages, Consumer side will get an index from a logical message queue ConsumeQueue when subscribing, then read message entity from CommitLog using the index. So in the end, it is still impossible to get around its storage structure.The storage structure of ConsumeQueue is as follows, and there is a 8-byte Message Tag hashcode, The message filter based on Tag value is just used this Message Tag hash-code. The RocketMQ has two mainly filter types: Tag filtering: Consumer can specify not only the message topic but also the message tag values, when subscribing. Multiple tag values need to be separated by '||'. When consumer subscribing a message, it builds the subscription request into a `SubscriptionData` object and sends a pull message request to the Broker side. Before the Broker side reads data from the RocketMQ file storage layer - Store, it will construct a `MessageFilter` using the `SubscriptionData` object and then pass it to the Store. Store get a record from `ConsumeQueue`, and it will filter the message by the saved tag hashcode, it is unable to filter the messages exactly in the server side because of only the hashcode will be used when filtering, Therefore, after the Consumer pulls the message, it also needs to compare the original tag string of the message. If the original tag string is not same with the expected, the message will be ignored. SQL92 filtering: This filter behavior is almost same with the above `Tag filtering` method. The only difference is on the way how Store works. The rocketmq-filter module is responsible for the construction and execution of the real SQL expression. Executing an SQL expression every time a filter is executed affects efficiency, so RocketMQ uses BloomFilter to avoid doing it every time. The expression context of SQL92 is a property of the message.
Project: StarRocks (App Definition and Development / Database)
File: get_query_profile.md

displayed_sidebar: "English" Obtains the profile of a query by using its `queryid`. This function returns empty if the `queryid` does not exist or is incorrect. To use this function, you must enable the profiling feature, that is, set the session variable `enableprofile` to `true` (`set enableprofile = true;`). If this feature is not enabled, an empty profile is returned. This function is supported from v3.0. ```Haskell getqueryprofile(x) ``` `x`: the query_id string. The supported data type is VARCHAR. The query profile contains the following fields. For more information about the query profile, see . ```SQL Query: Summary: Planner: Execution Profile 7de16a85-761c-11ed-917d-00163e14d435: Fragment 0: Pipeline (id=2): EXCHANGESINK (plannode_id=18): LOCALMERGESOURCE (plannodeid=17): Pipeline (id=1): LOCALSORTSINK (plannodeid=17): AGGREGATEBLOCKINGSOURCE (plannodeid=16): Pipeline (id=0): AGGREGATEBLOCKINGSINK (plannodeid=16): EXCHANGESOURCE (plannode_id=15): Fragment 1: ... Fragment 2: ... ``` ```sql -- Enable the profiling feature. set enable_profile = true; -- Run a simple query. select 1; -- Get the query_id of the query. select lastqueryid(); +--+ | lastqueryid() | +--+ | bd3335ce-8dde-11ee-92e4-3269eb8da7d1 | +--+ -- Obtain the query profile. select getqueryprofile('502f3c04-8f5c-11ee-a41f-b22a2c00f66b'); -- Use the regexp_extract function to obtain the QueryPeakMemoryUsage in the profile that matches the specified pattern. select regexpextract(getquery_profile('bd3335ce-8dde-11ee-92e4-3269eb8da7d1'), 'QueryPeakMemoryUsage: [0-9\.] [KMGB]', 0); +--+ | regexpextract(getquery_profile('bd3335ce-8dde-11ee-92e4-3269eb8da7d1'), 'QueryPeakMemoryUsage: [0-9.] [KMGB]', 0) | +--+ | QueryPeakMemoryUsage: 3.828 KB | +--+ ```