cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 149fa56c-4404-4f90-9e25-d34b676d5b39.md

title: AKS RBAC Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 149fa56c-4404-4f90-9e25-d34b676d5b39 Query name: AKS RBAC Disabled Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Azure Container Service (AKS) instance should have role-based access control (RBAC) enabled<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="21 23" name: Create an AKS instance azurermaks: name: myAKS resource_group: myResourceGroup location: eastus dns_prefix: akstest kubernetes_version: 1.14.6 linux_profile: admin_username: azureuser ssh_key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAA... service_principal: client_id: "cf72ca99-f6b9-4004-b0e0-bee10c521948" client_secret: "Password1234!" agentpoolprofiles: name: default count: 1 vmsize: StandardDS1_v2 type: VirtualMachineScaleSets max_count: 3 min_count: 1 enable_rbac: no name: Create an AKS instance v2 azurermaks: name: myAKS resource_group: myResourceGroup location: eastus dns_prefix: akstest kubernetes_version: 1.14.6 linux_profile: admin_username: azureuser ssh_key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAA... service_principal: client_id: "cf72ca99-f6b9-4004-b0e0-bee10c521948" client_secret: "Password1234!" agentpoolprofiles: name: default count: 1 vmsize: StandardDS1_v2 type: VirtualMachineScaleSets max_count: 3 min_count: 1 ``` ```yaml title="Negative test num. 1 - yaml file" name: Create an AKS instance v3 azurermaks: name: myAKS resource_group: myResourceGroup location: eastus dns_prefix: akstest kubernetes_version: 1.14.6 linux_profile: admin_username: azureuser ssh_key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAA... service_principal: client_id: cf72ca99-f6b9-4004-b0e0-bee10c521948 client_secret: Password1234! agentpoolprofiles: name: default count: 1 vmsize: StandardDS1_v2 type: VirtualMachineScaleSets max_count: 3 min_count: 1 enable_rbac: yes ```
Project: Apache Heron (App Definition and Development / Streaming & Messaging)
File: cluster-config-metrics.md

id: version-0.20.0-incubating-cluster-config-metrics title: Metrics Manager sidebar_label: Metrics Manager original_id: cluster-config-metrics <!-- 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. --> You can configure all of the [Metrics Managers](heron-architecture#metrics-manager) (MMs) in a topology using the parameters below. You can configure how the MM collects and transmits data in one (but only one) of two ways: time based or size based. If you choose time based, you can specify the maximum batch time (in milliseconds) for reading from and writing to the MM's socket; if you choose size based, you can specify maximum batch sizes (in bytes) instead. Config | Meaning | Default :-- |:- |:- `heron.metricsmgr.network.read.batch.time.ms` | The maximum batch time in milliseconds for the MM to read from the socket | 16 `heron.metricsmgr.network.write.batch.time.ms` | The maximum batch time in milliseconds for the MM to write to the socket | 16 Config | Meaning | Default :-- |:- |:- `heron.metricsmgr.network.read.batch.size.bytes` | Size based, the maximum batch size in bytes to read from socket | 32768 `heron.metricsmgr.network.write.batch.size.bytes` | Size based, the maximum batch size in bytes to write to socket | 32768 Each MM instance has a socket buffer for reading and writing metrics data. You can set maximum buffer sizes for both send and receive buffers. Config | Meaning | Default :-- |:- |:- `heron.metricsmgr.network.options.socket.send.buffer.size.bytes` | The maximum socket's send buffer size in bytes | 6553600 `heron.metricsmgr.network.options.socket.received.buffer.size.bytes` | The maximum socket's received buffer size in bytes of the metrics manager's network options | 8738000
Project: Vitess (App Definition and Development / Database)
File: rowlog.md

`rowlog` is a diagnostic tool for researching issues reported by users in vreplication workflows. These are usually reported as data mismatches or loss and are not reproducible because of the huge amounts of data involved and data privacy reasons. Also, the database configurations vary greatly: number/type/size of columns, collations, keys/indexes etc. In order to rule out that the problem is not related to the core vreplication algorithm this tool has been built. `rowlog` is a standalone command-line tool. For a given set of primary keys for a table (only non-composite integer primary keys are supported) it outputs the binlogs associated with these ids, both on the source and on the target. The binlogs on the source and target will usually not be identical because vreplication can "merge" multiple binlog entries during the initial copy phase. `rowlog` uses the vstream API to stream events for the specified table from both the source and target keyspaces. Here is an example of how to invoke it: ``` go build ./rowlog -ids 1,3,4 -table customer -pk customer_id -source commerce -target customer -vtctld localhost:15999 -vtgate localhost:15991 -cells zone1 -topoimplementation etcd2 -topoglobalserveraddress localhost:2379 -topoglobalroot /vitess/global ``` The resulting binlog entries are output to two tab-separated files which can be inspected to validate if data being copied is consistent. Initial version is for unsharded keyspaces but can be easily extended for sharded. Another possible enhancement is to also stream the events to the _vt.vreplication table so that we can track the source gtid positions related to the sql applied on the target. However this requires changes in vreplication: currently the sidecar _vt database is not streamed.
Project: Druid (App Definition and Development / Database)
File: overlord.md

id: overlord title: "Overlord service" sidebar_label: "Overlord" <!-- ~ Licensed to the Apache Software Foundation (ASF) under one ~ or more contributor license agreements. See the NOTICE file ~ distributed with this work for additional information ~ regarding copyright ownership. The ASF licenses this file ~ to you under the Apache License, Version 2.0 (the ~ "License"); you may not use this file except in compliance ~ with the License. You may obtain a copy of the License at ~ ~ http://www.apache.org/licenses/LICENSE-2.0 ~ ~ Unless required by applicable law or agreed to in writing, ~ software distributed under the License is distributed on an ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY ~ KIND, either express or implied. See the License for the ~ specific language governing permissions and limitations ~ under the License. --> The Overlord service is responsible for accepting tasks, coordinating task distribution, creating locks around tasks, and returning statuses to callers. The Overlord can be configured to run in one of two modes - local or remote (local being default). In local mode, the Overlord is also responsible for creating Peons for executing tasks. When running the Overlord in local mode, all MiddleManager and Peon configurations must be provided as well. Local mode is typically used for simple workflows. In remote mode, the Overlord and MiddleManager are run in separate services and you can run each on a different server. This mode is recommended if you intend to use the indexing service as the single endpoint for all Druid indexing. For Apache Druid Overlord service configuration, see . For basic tuning guidance for the Overlord service, see . For a list of API endpoints supported by the Overlord, please see the . If a MiddleManager has task failures above a threshold, the Overlord will blacklist these MiddleManagers. No more than 20% of the MiddleManagers can be blacklisted. Blacklisted MiddleManagers will be periodically whitelisted. The following variables can be used to set the threshold and blacklist timeouts. ``` druid.indexer.runner.maxRetriesBeforeBlacklist druid.indexer.runner.workerBlackListBackoffTime druid.indexer.runner.workerBlackListCleanupPeriod druid.indexer.runner.maxPercentageBlacklistWorkers ``` The autoscaling mechanisms currently in place are tightly coupled with our deployment infrastructure but the framework should be in place for other implementations. We are highly open to new implementations or extensions of the existing mechanisms. In our own deployments, MiddleManager services are Amazon AWS EC2 nodes and they are provisioned to register themselves in a environment. If autoscaling is enabled, new MiddleManagers may be added when a task has been in pending state for too long. MiddleManagers may be terminated if they have not run any tasks for a period of time.
Project: ShardingSphere (App Definition and Development / Database)
File: icla.en.md

+++ title = "Sign ICLA Guide" weight = 3 chapter = true +++ Apache CLA short for Apache Contributor License Agreement, the purpose of this agreement is to clearly define the terms under which intellectual property has been contributed to the ASF and thereby allow us to defend the project should there be a legal dispute regarding the software at some future time. A signed ICLA is required to be on file before an individual is given commit rights to any ASF project. The process of submitting ICLA are: First, click the link and find CLAs under the Contributor License Agreements section. At the top of the page, there are two download links choose ICLA(Individual Contributor License Agreement) and download it. Open the PDF, and fill in the following columns in English. To be noticed: Leave a space between family name and last name, remember capitalize the first letter, please write family name at first. Preferred Apache id(s) is a required field for committers. The signature at the bottom of the document: Apache only accept hand-written signature or gpg signature, here we suggest choosing hand-written way. Print the document and sign your name on the paper, or use electric pen. If you are a new committer, please scan all pages into a single pdf file, and attach the pdf file to an email to secretary@apache.org. The rest of the case, please send the file to the person who contact you.
Project: StarRocks (App Definition and Development / Database)
File: null_or_empty.md

displayed_sidebar: "English" This function returns true when the string is empty or NULL. Otherwise, it returns false. ```Haskell BOOLEAN NULLOREMPTY (VARCHAR str) ``` ```Plain Text MySQL > select nullorempty(null); ++ | nullorempty(NULL) | ++ | 1 | ++ MySQL > select nullorempty(""); +-+ | nullorempty('') | +-+ | 1 | +-+ MySQL > select nullorempty("a"); +--+ | nullorempty('a') | +--+ | 0 | +--+ ``` NULLOREMPTY
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_iam_service_account.md

+++ title = "googleiamservice_account resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleiamservice_account" identifier = "inspec/resources/gcp/googleiamserviceaccount.md googleiamserviceaccount resource" parent = "inspec/resources/gcp" +++ A `googleiamservice_account` is used to test a Google ServiceAccount resource ```ruby describe googleiamservice_account(project: 'chef-gcp-inspec', name: "display-name@project-id.iam.gserviceaccount.com") do it { should exist } its('display_name') { should cmp '' } end describe googleiamservice_account(project: 'chef-gcp-inspec', name: "nonexistent@project-id.iam.gserviceaccount.com") do it { should_not exist } end ``` Properties that can be accessed from the `googleiamservice_account` resource: `name` : The name of the service account. `project_id` : Id of the project that owns the service account. `unique_id` : Unique and stable id of the service account `email` : Email address of the service account. `display_name` : User specified description of service account. `oauth2clientid` : OAuth2 client id for the service account. Ensure the is enabled for the current project.
Project: StarRocks (App Definition and Development / Database)
File: SHOW_DATABASES.md

displayed_sidebar: "English" Views databases in your current StarRocks cluster or an external data source. StarRocks supports viewing databases of an external data source from v2.3 onwards. ```SQL SHOW DATABASES [FROM <catalog_name>] ``` | Parameter | Required | Description | | -- | | | | catalogname | No | The name of the internal catalog or an external catalog.<ul><li>If you do not specify the parameter or specify the name of the internal catalog, which is `defaultcatalog`, you can view databases in your current StarRocks cluster.</li><li>If you set the value of the parameter to the name of an external catalog, you can view databases in the corresponding external data source. You can run to view internal and external catalogs.</li></ul> | Example 1: View databases in your current StarRocks cluster. ```SQL SHOW DATABASES; ``` Or ```SQL SHOW DATABASES FROM default_catalog; ``` The output of the preceding statements is as follows. ```SQL +-+ | Database | +-+ | db1 | | db2 | | db3 | +-+ ``` Example 2: View databases in a Hive cluster by using the `Hive1` external catalog. ```SQL SHOW DATABASES FROM hive1; +--+ | Database | +--+ | hive_db1 | | hive_db2 | | hive_db3 | +--+ ```
Project: Meshery (Provisioning / Automation & Configuration)
File: aws-load-balancer-controller.md

layout: integration title: AWS Load Balancer subtitle: Collaborative and visual infrastructure as code for AWS Load Balancer image: /assets/img/integrations/aws-load-balancer-controller/icons/color/aws-load-balancer-controller-color.svg permalink: extensibility/integrations/aws-load-balancer-controller docURL: https://docs.meshery.io/extensibility/integrations/aws-load-balancer-controller description: integrations-category: Cloud Native Network integrations-subcategory: Service Proxy registrant: Artifact Hub components: name: ingress-class-params colorIcon: assets/img/integrations/aws-load-balancer-controller/components/ingress-class-params/icons/color/ingress-class-params-color.svg whiteIcon: assets/img/integrations/aws-load-balancer-controller/components/ingress-class-params/icons/white/ingress-class-params-white.svg description: featureList: [ "Manage AWS Elastic Load Balancers for a Kubernetes cluster.", "Provide high performance traffic serving that can scale to millions of requests per second.", "Supports IP address targeting mode for Network Load Balancers." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Elastic Load Balancing (ELB) automatically distributes incoming application traffic across multiple targets and virtual appliances in one or more Availability Zones (AZs)." language: en list: include type: extensibility category: integrations
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-data-sources-text.md

layout: global title: Text Files displayTitle: Text Files license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Spark SQL provides `spark.read().text("file_name")` to read a file or directory of text files into a Spark DataFrame, and `dataframe.write().text("path")` to write to a text file. When reading a text file, each line becomes each row that has string "value" column by default. The line separator can be changed as shown in the example below. The `option()` function can be used to customize the behavior of reading or writing, such as controlling behavior of the line separator, compression, and so on. <div class="codetabs"> <div data-lang="python" markdown="1"> {% includeexample textdataset python/sql/datasource.py %} </div> <div data-lang="scala" markdown="1"> {% includeexample textdataset scala/org/apache/spark/examples/sql/SQLDataSourceExample.scala %} </div> <div data-lang="java" markdown="1"> {% includeexample textdataset java/org/apache/spark/examples/sql/JavaSQLDataSourceExample.java %} </div> </div> Data source options of text can be set via: the `.option`/`.options` methods of `DataFrameReader` `DataFrameWriter` `DataStreamReader` `DataStreamWriter` `OPTIONS` clause at <table> <thead><tr><th><b>Property Name</b></th><th><b>Default</b></th><th><b>Meaning</b></th><th><b>Scope</b></th></tr></thead> <tr> <td><code>wholetext</code></td> <td><code>false</code></td> <td>If true, read each file from input path(s) as a single row.</td> <td>read</td> </tr> <tr> <td><code>lineSep</code></td> <td><code>\r</code>, <code>\r\n</code>, <code>\n</code> (for reading), <code>\n</code> (for writing)</td> <td>Defines the line separator that should be used for reading or writing.</td> <td>read/write</td> </tr> <tr> <td><code>compression</code></td> <td>(none)</td> <td>Compression codec to use when saving to file. This can be one of the known case-insensitive shorten names (none, bzip2, gzip, lz4, snappy and deflate).</td> <td>write</td> </tr> </table> Other generic options can be found in <a href="https://spark.apache.org/docs/latest/sql-data-sources-generic-options.html"> Generic File Source Options</a>.
Project: Trivy-Operator (Provisioning / Security & Compliance)
File: exposedsecret-report.md

An instance of the `ExposedSecretReport` represents the secrets found in a container image of a given Kubernetes workload. It consists of a list exposed secrets with a summary grouped by severity. For a multi-container workload the Trivy Operator will create multiple instances of the `ExposedSecretsReports` in the workload's namespace with the owner reference set to that workload. Each report follows the naming convention `<workload kind>-<workload name>-<container-name>`. The following listing shows a sample `ExposedSecretReport` associated with the ReplicaSet named `app-574ddcb559` in the `default` namespace that has the `app` container. ```yaml apiVersion: aquasecurity.github.io/v1alpha1 kind: ExposedSecretReport metadata: creationTimestamp: "2022-06-29T14:25:54Z" generation: 2 labels: resource-spec-hash: 8495697ff5 trivy-operator.container.name: app trivy-operator.resource.kind: ReplicaSet trivy-operator.resource.name: app-67b77f5965 trivy-operator.resource.namespace: default name: replicaset-app-67b77f5965-app namespace: default ownerReferences: apiVersion: apps/v1 blockOwnerDeletion: false controller: true kind: ReplicaSet name: app-67b77f5965 uid: 04a744fe-1126-42d5-bb8b-0917bdb51a28 resourceVersion: "1420" uid: 2b2697bb-d528-4d4d-8312-a74dcab6ac65 report: artifact: repository: myimagewithsecret tag: v0.20.1 registry: server: index.docker.io scanner: name: Trivy vendor: Aqua Security version: 0.35.0 secrets: category: Stripe match: 'publishable_key: *' ruleID: stripe-access-token severity: HIGH target: "/app/config/secret.yaml" title: Stripe category: Stripe match: 'secret_key: *' ruleID: stripe-access-token severity: HIGH target: "/app/config/secret.yaml" title: Stripe summary: criticalCount: 0 highCount: 2 lowCount: 0 mediumCount: 0 updateTimestamp: "2022-06-29T14:29:37Z" ```
Project: Meshery (Provisioning / Automation & Configuration)
File: windows.md

layout: default title: Install Meshery CLI on Windows permalink: installation/windows type: installation category: mesheryctl redirect_from: installation/platforms/windows display-title: "true" language: en list: include image: /assets/img/platforms/wsl2.png abstract: Install Meshery CLI on Windows On Windows systems, `mesheryctl` can be installed via Scoop or can be . {% include mesheryctl/installation-scoop.md %} Follow the to install the mesheryctl CLI. Then, execute: <pre class="codeblock-pre"> <div class="codeblock"><div class="clipboardjs">./mesheryctl system start</div></div> </pre> Optionally, move the mesheryctl binary to a directory in your PATH. <!-- Meshery server supports customizing authentication flow callback URL, which can be configured in the following way <pre class="codeblock-pre"> <div class="codeblock"><div class="clipboardjs">MESHERYSERVERCALLBACK_URL=https://custom-host ./mesheryctl system start</div></div> </pre> Type `yes` when prompted to choose to configure a file. To get started, choose Docker as your platform to deploy Meshery. --> Guides to using Meshery's various features and components. {% assign sorted_guides = site.pages | sort: "name" %} <ul> {% for item in sorted_guides %} {% if item.type=="guides" and item.category=="mesheryctl" and item.list!="exclude" and item.language=="en" -%} <li><a href="{{ site.baseurl }}{{ item.url }}">{{ item.title }}</a> </li> {% endif %} {% endfor %} <li><a href="{{ site.baseurl }}/guides/upgrade#upgrading-meshery-cli">Upgrading Meshery CLI</a></li> </ul> {% include related-discussions.html tag="mesheryctl" %} {:toc}
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.0.18.en.md

Add low level tuning settings for QUIC listeners. Add pod disruption budget to helm chart QUIC transport Multistreams support and QUIC TLS cacert support. Add two new Erlang apps 'tools' and 'covertool' to the release. So we can run profiling and test coverage analysis on release packages. New common TLS option 'hibernate_after' to reduce memory footprint per idle connecion, default: 5s. Validate `bytes` param to `GET /trace/:name/log` to not exceed signed 32bit integer. To prevent errors caused by an incorrect EMQX node cookie provided from an environment variable, we have implemented a fail-fast mechanism. Previously, when an incorrect cookie was provided, the command would still attempt to ping the node, leading to the error message 'Node xxx not responding to pings'. With the new implementation, if a mismatched cookie is detected, a message will be logged to indicate that the cookie is incorrect, and the command will terminate with an error code of 1 without trying to ping the node. Fix bridge metrics when running in async mode with batching enabled (`batch_size` > 1). Fix error message when the target node of `emqx_ctl cluster join` command is not running. Allow 'emqx ctl cluster' command to be issued before Mnesia starts. Prior to this change, EMQX `replicant` could not use `manual` discovery strategy. Now it's possible to join cluster using 'manual' strategy. Fix bad http response format when client ID is not found in `clients` APIs Avoid parsing config files for node name and cookie when executing non-boot commands in bin/emqx. Report memory usage to statsd and prometheus using the same data source as dashboard. Prior to this fix, the memory usage data source was collected from an outdated source which did not work well in containers. Fixed configuration issue when choosing to use SSL for a Postgres connection (`authn`, `authz` and bridge). The connection could fail to complete with a previously working configuration after an upgrade from 5.0.13 to newer EMQX versions. Fix Swagger API schema generation. `deprecated` metadata field is now always boolean, as suggests.