cwielenb/CNCF-Dataset huggingface dataset:
Project: Checkov (Provisioning / Security & Compliance)
File: GitHub Actions.md

layout: default published: true title: GitHub Actions nav_order: 3 Integrating Checkov into GitHub Actions provides a simple, automatic way of applying policies to your Terraform code both during pull request review and as part of any build process. Check out our . Add a new step in the `workflow.yml`. ```tree .github workflows ``` Here is a basic example: ```yaml name: Checkov on: push: branches: master jobs: build: runs-on: ubuntu-latest steps: uses: actions/checkout@v2 name: Set up Python 3.8 uses: actions/setup-python@v4 with: python-version: 3.8 name: Test with Checkov id: checkov uses: bridgecrewio/checkov-action@master with: directory: example/examplea framework: terraform ``` Any time after you push your code to GitHub, it will run your job. If Checkov finds any errors, it will fail the build. In the original examples code, the file aws_efs_file_system.sharedstore.tf is not set to encrypted: ```python resource "awsefsfile_system" "sharedstore" { creationtoken = var.efs["creationtoken"] lifecycle_policy { transitiontoia = var.efs["transitiontoia"] } kmskeyid = var.efs["kmskeyid"] encrypted = false performancemode = var.efs["performancemode"] provisionedthroughputinmibps = var.efs["provisionedthroughputinmibps"] throughputmode = var.efs["throughputmode"] } ``` This will fail a Checkov test: The previous error can be fixed by setting the value of encryption to true.
Project: cert-manager (Provisioning / Security & Compliance)
File: bug.md

name: Bug report about: Report a bug to help us improve cert-manager <!-- Bugs should be filed for issues encountered whilst operating cert-manager. You should first attempt to resolve your issues through the community support channels, e.g. Slack, in order to rule out individual configuration errors. Please provide as much detail as possible. --> Describe the bug: <!-- A clear and concise description of what the bug is. Tip: you can use ``` <code here> ``` for code blocks of your kubectl output or YAML files. --> Expected behaviour: <!--A concise description of what you expected to happen.--> Steps to reproduce the bug: <!--Steps to reproduce the bug should be clear and easily reproducible to help people gain an understanding of the problem.--> Anything else we need to know?: Environment details:: Kubernetes version: Cloud-provider/provisioner: cert-manager version: Install method: e.g. helm/static manifests /kind bug
Project: ShardingSphere (App Definition and Development / Database)
File: show-migration-check-status.en.md

+++ title = "SHOW MIGRATION CHECK STATUS" weight = 11 +++ The `SHOW MIGRATION CHECK STATUS` syntax is used to query migration check status for specified migration job. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowMigrationCheckStatus ::= 'SHOW' 'MIGRATION' 'CHECK' 'STATUS' migrationJobId migrationJobId ::= string ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} `migrationJobId` needs to be obtained through syntax query | Columns | Description | ||| | tables | migration check table | | result | check result | | finishedpercentage | check finished finishedpercentage | | remaining_seconds | check remaining time | | checkbegintime | check begin time | | checkendtime | check end time | | error_message | error message | Query migration check status ```sql SHOW MIGRATION CHECK STATUS 'j010180026753ef0e25d3932d94d1673ba551'; ``` ```sql mysql> SHOW MIGRATION CHECK STATUS 'j010180026753ef0e25d3932d94d1673ba551'; ++--++-+-+-+++ | tables | result | finishedpercentage | remainingseconds | checkbegintime | checkendtime | durationseconds | errormessage | ++--++-+-+-+++ | t_order | true | 100 | 0 | 2022-11-01 17:57:39.940 | 2022-11-01 17:57:40.587 | 0 | | ++--++-+-+-+++ 1 row in set (0.01 sec) ``` `SHOW`, `MIGRATION`, `CHECK`, `STATUS`
Project: KICS (Provisioning / Security & Compliance)
File: 8bbb242f-6e38-4127-86d4-d8f0b2687ae2.md

title: AMI Not Encrypted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8bbb242f-6e38-4127-86d4-d8f0b2687ae2 Query name: AMI Not Encrypted Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: AWS AMI Encryption is not enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="25 29 7" resource "aws_ami" "positive1" { name = "terraform-example" virtualization_type = "hvm" rootdevicename = "/dev/xvda" ebsblockdevice { device_name = "/dev/xvda" snapshot_id = "snap-xxxxxxxx" volume_size = 8 } } resource "aws_ami" "positive2" { name = "terraform-example" virtualization_type = "hvm" rootdevicename = "/dev/xvda1" ebsblockdevice { device_name = "/dev/xvda1" snapshot_id = "snap-xxxxxxxx" volume_size = 8 encrypted = false } } resource "aws_ami" "positive3" { name = "terraform-example" virtualization_type = "hvm" rootdevicename = "/dev/xvda1" } ``` ```tf title="Negative test num. 1 - tf file" resource "aws_ami" "negative1" { name = "terraform-example" virtualization_type = "hvm" rootdevicename = "/dev/xvda2" ebsblockdevice { device_name = "/dev/xvda2" snapshot_id = "snap-xxxxxxxx" volume_size = 8 encrypted = true } } ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: issue-priorities.md

title: "Issue Priorities" <!-- Licensed 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. --> Expectation: Drop everything else and work continuously to resolve. An outage means that some piece of infrastructure that the community relies on is down. A P0 issue is more urgent than simply blocking the next release. Example P0 issues: the build is broken, halting all development the website is down a vulnerability requires a point release ASAP Expectation: Continuous status updates. P1 bugs should not be unassigned. Most P1 bugs should block release. Example P1 issues: data loss error important component is nonfunctional for important use cases major performance regression security related issues (CVEs) failing postcommit test flaky test Expectation: Most tickets fall into this priority. These can be planned and executed by anyone who is interested. No special urgency is associated, but if no action is taken on a P2 ticket for a long time, it indicates it is actually just P3/nice-to-have. Example P2 issues typical feature request bug that affects some use cases but don't make a component nonfunctional ignored ("sickbayed") test Expectation: Nice-to-have improvements. Example P3 issues feature request that is nice-to-have ticket filed as P2 that no one finds time to work on Expectation: Nice-to-have improvements that are also very small and easy. Usually it is quicker to just fix them than to file a bug, but the issue can be referenced by a pull request and shows up in release notes. Example P4 issues spelling errors in comments or code
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.141.md

layout: release date: 2023-09-18 tag: v0.6.141 [bug] Update healthcheck.go @theBeginner86 (#8770) [chore] Fix lint @theBeginner86 (#8821) [UI] Added Connect Helm Repo button in connections page @Yashsharma1911 (#8816) Format k8s response @MUzairS15 (#8775) Notification Center @aabidsofi19 (#8733) Bump @cypress/request and cypress in /ui @dependabot (#8792) [UI] Prevent rjsf modal rerendering @Yashsharma1911 (#8787) [bug] Update healthcheck.go @theBeginner86 (#8770) [chore] Fix lint @theBeginner86 (#8821) Bump @cypress/request and cypress in /ui @dependabot (#8792) Notification Center @aabidsofi19 (#8733) Fixes the issue in Docs Search: Unwanted display of search result on separate line from bullet point in safari browser(7402) @phanithinks (#8690) meshmodel docs @parth721 (#8656) Thank you to our contributors for making this release possible: @MUzairS15, @Yashsharma1911, @aabidsofi19, @alphaX86, @dependabot, @leecalcote, @parth721, @phanithinks and @theBeginner86
Project: StarRocks (App Definition and Development / Database)
File: left.md

displayed_sidebar: "English" This function returns a specified number of characters from the left side of a given string. The unit for length: utf8 character. Note: This function is also named as . ```SQL VARCHAR left(VARCHAR str,INT len) ``` ```SQL MySQL > select left("Hello starrocks",5); +-+ | left('Hello starrocks', 5) | +-+ | Hello | +-+ ``` LEFT
Project: StarRocks (App Definition and Development / Database)
File: multi_distinct_sum.md

displayed_sidebar: "English" Returns the sum of distinct values in `expr`, equivalent to sum(distinct expr). ```Haskell multidistinctsum(expr) ``` `expr`: the columns involved in the calculation. Column values can be of the following types: TINYINT, SMALLINT, INT, LARGEINT, FLOAT, DOUBLE, or DECIMAL. The mapping between column values and return value types is as follows: BOOLEAN -> BIGINT TINYINT -> BIGINT SMALLINT -> BIGINT INT -> BIGINT BIGINT -> BIGINT FLOAT -> DOUBLE DOUBLE -> DOUBLE LARGEINT -> LARGEINT DECIMALV2 -> DECIMALV2 DECIMAL32 -> DECIMAL128 DECIMAL64 -> DECIMAL128 DECIMAL128 -> DECIMAL128 Create a table with `k0` as the INT field. ```sql CREATE TABLE tabl (k0 BIGINT NOT NULL) ENGINE=OLAP DUPLICATE KEY(`k0`) COMMENT "OLAP" DISTRIBUTED BY HASH(`k0`) PROPERTIES( "replication_num" = "3", "storage_format" = "DEFAULT" ); ``` Insert values into the table. ```sql -- INSERT INTO tabl VALUES ('0'), ('1'), ('1'), ('1'), ('2'), ('2'); ``` Use multidistinctsum() to calculate the sum of distinct values in the `k0` column. ```plain text MySQL > select multidistinctsum(k0) from tabl; ++ | multidistinctsum(k0) | ++ | 3 | ++ 1 row in set (0.03 sec) ``` The distinct values of `k0` is 0, 1, 2 and we can get 3 after adding them together.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-12872.en.md

Customizable client attributes in `clientinfo`. Introduced a new field `client_attrs` in the `clientinfo` object. This enhancement enables the initialization of `client_attrs` with specific attributes derived from the `clientinfo` fields, immediately up on accepting an MQTT connection. The `client_attrs` fields can be initially populated from one of the following `clientinfo` fields: `cn`: The common name from the TLS client's certificate. `dn`: The distinguished name from the TLS client's certificate, that is, the certificate "Subject". `clientid`: The MQTT client ID provided by the client. `username`: The username provided by the client. `user_property`: Extract a property value from 'User-Property' of the MQTT CONNECT packet. Additional attributes may be merged into `client_attrs` from authentication responses. Supported authentication backends include: HTTP: Attributes can be included in the JSON object of the HTTP response body through a `client_attrs` field. JWT: Attributes can be included via a `client_attrs` claim within the JWT. If `client_attrs` is initialized before authentication, it can be used in external authentication requests. For instance, `${client_attrs.property1}` can be used within request templates directed at an HTTP server for the purpose of authenticity validation. The `client_attrs` can be utilized in authorization configurations or request templates, enhancing flexibility and control. Examples include: In `acl.conf`, use `{allow, all, all, ["${client_attrs.namespace}/#"]}` to apply permissions based on the `namespace` attribute. In other authorization backends, `${client_attrs.namespace}` can be used within request templates to dynamically include client attributes.
Project: YugabyteDB (App Definition and Development / Database)
File: refresh_matview.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="457" height="115" viewbox="0 0 457 115"><path class="connector" d="M0 22h15m76 0h10m111 0h10m53 0h30m117 0h20m-152 0q5 0 5 5v8q0 5 5 5h127q5 0 5-5v-8q0-5 5-5m5 0h7m2 0h2m2 0h2m-457 50h2m2 0h2m2 0h7m113 0h30m53 0h30m38 0h20m-73 0q5 0 5 5v8q0 5 5 5h48q5 0 5-5v-8q0-5 5-5m5 0h10m52 0h20m-238 0q5 0 5 5v23q0 5 5 5h213q5 0 5-5v-23q0-5 5-5m5 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="76" height="25" rx="7"/><text class="text" x="25" y="22">REFRESH</text><rect class="literal" x="101" y="5" width="111" height="25" rx="7"/><text class="text" x="111" y="22">MATERIALIZED</text><rect class="literal" x="222" y="5" width="53" height="25" rx="7"/><text class="text" x="232" y="22">VIEW</text><rect class="literal" x="305" y="5" width="117" height="25" rx="7"/><text class="text" x="315" y="22">CONCURRENTLY</text><a xlink:href="../../../syntaxresources/grammardiagrams#matview-name"><rect class="rule" x="15" y="55" width="113" height="25"/><text class="text" x="25" y="72">matview_name</text></a><rect class="literal" x="158" y="55" width="53" height="25" rx="7"/><text class="text" x="168" y="72">WITH</text><rect class="literal" x="241" y="55" width="38" height="25" rx="7"/><text class="text" x="251" y="72">NO</text><rect class="literal" x="309" y="55" width="52" height="25" rx="7"/><text class="text" x="319" y="72">DATA</text><polygon points="392,79 396,79 396,65 392,65" style="fill:black;stroke-width:0"/></svg>
Project: ThreatMapper (Provisioning / Security & Compliance)
File: CONTRIBUTING.md

First off, thank you for taking the time to contribute! Here are some important resources: : If you need to share a security vulnerability, please refer to our Security Policy. : Any questions - join us on Slack : Find and contribute to ThreatMapper documentation on the wiki. : ThreatMapper is 100% open source, using the Apache 2.0 license. : The Apache 2.0 license applies to all contributions offered to the ThreatMapper project. : The ThreatMapper community strives to be open and welcoming to all. Head over to our and share what's going on. It's generally useful to include details of your installation, as ThreatMapper is under constant development and we fix bugs fast. `docker images list` and `docker ps -a`, or the equivalent Kubernetes commands are a good start. Logs from any containers that may be misbehaving are also useful. If you believe you've found a security vulnerability, please refer to our . For all other bugs, please . If so, go ahead and add details to the existing issue. If the bug appears to be new, please . The template will prompt you for the information that will help us to understand and address the issue. Thank you. Please send a with a clear explanation of what you're seeking to achieve, and what you have done. Code Style: we're flexible and accomodating. Copy the style of the code adjacent to your contributions, keep it clear and easy to understand for other developers and we're all good. If it's a well-formed enhancement, please . Explain the enhancement and any supporting information - who it benefits, why it's important etc. If you'd like to discuss the idea before proposing it on GitHub, share it on our and we will work through it together. You can reach out to the ThreatMapper community leads at community *at* deepfence *dot* io.
Project: ClickHouse (App Definition and Development / Database)
File: v20.8.8.2-lts.md

Backported in : Avoid unnecessary network errors for remote queries which may be cancelled while execution, like queries with `LIMIT`. (). Backported in : Fixed crash on `CREATE TABLE ... AS sometable` query when `sometable` was created `AS table_function()` Fixes . (). Backported in : Fix ColumnConst comparison which leads to crash. This fixed . (). Backported in : Update embedded timezone data to version 2020d (also update cctz to the latest master). ().
Project: secureCodeBox (Provisioning / Security & Compliance)
File: SECURITY.md

<!-- SPDX-FileCopyrightText: the secureCodeBox authors SPDX-License-Identifier: Apache-2.0 --> Our release cycle for new features (minor update) is roughly every two weeks (we will usually make a new release after each review). | Version | Security Fixes | Supported* | | - | | | | 4.x.x | :whitecheckmark: | :whitecheckmark: | | 3.15.x | :whitecheckmark: | :whitecheckmark: | | <= 2.9.x | :x: | :x: | | < 2.0 | :x: | :x: | Upcoming major updates will come with a time window in which both major versions (starting with v2.x.x) will receive security updates and bugfixes. The concrete support intervall will be probably a couple of months and will be published when the next major version will be released. We currently plan to provide support for the latest minor release only. We try to make bugfixes and high severity fixes available as patch release for the current minor release as early as possible. If you are interested in extended support for older versions with security updates of our project please get in touch with the project team via Slack or email <secureCodeBox@iteratec.com>. You have found a vulnerability in the project that shouldn't be disclosed as public issue before it's fixed? Please get in touch with the project team via Slack or email <secureCodeBox@iteratec.com>. You can expect a fast reaction within the next days. We will keep you updated about the next steps and inform you if the vulnerability is accepted and when its fixed or if its ordeclined somehow.
Project: OpenYurt (Provisioning / Automation & Configuration)
File: README.md

YurtHub is a node daemon that supports node autonomy in each edge node. It caches the states of necessary APIServer objects in the local storage when cluster-edge networking is established. In case an edge node is offline, YurtHub guarantees that all the registered components in the node can access the cached APIServer object states, pretending the APIServer is still alive. <div align="left"> <img src="../../docs/img/yurthub.png" width=70% title="YurtHub architecture"> </div> \ Here are a few key components in YurtHub: Http Server: proxying all the http requests sent to the local listeners to the corresponding handler based on the network connectivity with the cloud site APIServer. Load Balancer: sending the requests to one of the cloud site APIServer endpoints. It supports round-robin or priority based routing. Cache Manager: providing interfaces to manage the data saved in the local storage. The data are updated based on the https response from the cloud site APIServer, and are read by the `Local Proxy` in case node is offline. Certificate Manager: managing the client certificate for all the components that may access the cloud site APIServer. For example, YurtHub may use the certificate generated by Kubelet to communicate with the cloud site APIServer. Health Check: periodically checking the network connectivity between the cloud site APIServer and the node. Filter: some filters are provided for mutating the response data from cloud site APIServer, `servicetopology`, `discardcloudservice`, `masterservice` filters are present now. YurtHub is deployed as a Kubelet static Pod (). And YurtHub will be installed automatically by `` command. The cached data are saved in the following node disk location ``` /etc/kubernetes/cache/{component}/{resource}/{namespace}/{name}.json ``` component: obtained from the header of the http request. The key is "User-Agent". resource: the type of the cached APIServer object such as `pods`, `configmaps`, `services` and so on. namespace: the namespace of the cached APIServer object, optional. Cluster scoped objects do not have namespace. name: the name of the cached APIServer object. Only response for built-in agent names such as kubelet/flanneld/coredns/kube-proxy can be cached on local disk. In order to leverage the cache capability of Yurthub for customize node components that need to access cloud site APIserver, please do the following: Add component `User-Agent` in `cache_agents` field of `kube-system/yurthb-cfg` configmap. take `foo` and `bar` component as example: ``` apiVersion: v1 kind: ConfigMap metadata: name: yurt-hub-cfg namespace: kube-system data: cache_agents: "foo, bar" ``` If you want to enable cache capability for all components, please configure `*` for `cache_agents` field of `kube-system/yurthb-cfg` configmap.
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_data_verify_mongodb.md

title: Kubectl-Dba Data Verify Mongodb menu: docs_{{ .version }}: identifier: kubectl-dba-data-verify-mongodb name: Kubectl-Dba Data Verify Mongodb parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Verify data to a mongodb resource Use this cmd to verify data existence in a mongodb object ``` kubectl-dba data verify mongodb [flags] ``` ``` kubectl dba data verify mg -n demo mg-rs --rows 500 ``` ``` -h, --help help for mongodb -r, --rows int number of rows to verify (default 100) ``` ``` --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 ``` - Verify data in a database
Project: ShardingSphere (App Definition and Development / Database)
File: count-single-table.en.md

+++ title = "COUNT SINGLE_TABLE RULE" weight = 3 +++ The `COUNT SINGLE TABLE` syntax is used to query number of single table for specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql CountSingleTable::= 'COUNT' 'SINGLE' 'TABLE' ('FROM' databaseName)? databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When `databaseName` is not specified, the default is the currently used `DATABASE`. If `DATABASE` is not used, `No database selected` will be prompted. | Column | Description | ||--| | database | The database name where the single table is located | | count | The count of single table | Query the number of single rules for specified database. ```sql COUNT SINGLE TABLE ``` ```sql mysql> COUNT SINGLE TABLE; +-+--+ | database | count | +-+--+ | ds | 2 | +-+--+ 1 row in set (0.02 sec) ``` `COUNT`, `SINGLE`, `TABLE`, `FROM`