cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 71ea648a-d31a-4b5a-a589-5674243f1c33.md

title: Public Port Wide hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 71ea648a-d31a-4b5a-a589-5674243f1c33 Query name: Public Port Wide Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: AWS Security Group should not have public port wide<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" name: example ec2 group amazon.aws.ec2_group: name: example description: an example EC2 group vpc_id: 12345 region: eu-west-1 rules: proto: tcp from_port: 80 to_port: 82 cidr_ip: 0.0.0.0/0 proto: tcp from_port: 2 to_port: 22 cidr_ipv6: ::/0 ``` ```yaml title="Negative test num. 1 - yaml file" name: example ec2 group v2 amazon.aws.ec2_group: name: example description: an example EC2 group vpc_id: 12345 region: eu-west-1 rules: proto: tcp from_port: 80 to_port: 80 cidr_ip: 0.0.0.0/0 proto: tcp from_port: 22 to_port: 22 cidr_ip: 10.0.0.0/8 ```
Project: Meshery (Provisioning / Automation & Configuration)
File: nginx-sm.md

layout: default title: Meshery Adapter for NGINX Service Mesh name: Meshery Adapter for NGINX Service Mesh component: NGINX Service Mesh earliest_version: v1.2.0 port: 10010/gRPC project_status: stable github_link: https://github.com/meshery/meshery-nginx-sm image: /assets/img/service-meshes/nginx-sm.svg white_image: /assets/img/service-meshes/nginx-sm-white.svg permalink: extensibility/adapters/nginx-sm redirect_from: service-meshes/adapters/nginx-sm language: en {% assign sortedtestsgroup = site.compatibility | group_by: "meshery-component" %} {% for group in sortedtestsgroup %} {% if group.name == "meshery-nginx-sm" %} {% assign items = group.items | sort: "meshery-component-version" | reverse %} {% for item in items %} {% if item.meshery-component-version != "edge" %} {% if item.overall-status == "passing" %} {% assign adapterversiondynamic = item.meshery-component-version %} {% break %} {% elsif item.overall-status == "failing" %} {% continue %} {% endif %} {% endif %} {% endfor %} {% endif %} {% endfor %} {% include compatibility/adapter-status.html %} The {{ page.name }} is currently under construction ({{ page.project_status }} state). Want to contribute? Check our . The {{page.name}} can install {{page.earliest_version}} of {{page.component}} ewE E . A number of sample applications can be installed using the {{page.name}}. Lifecycle management of {{page.component}} Lifecycle management of sample applications Performance testing The {{ page.name }} includes a handful of sample applications. Use Meshery to deploy any of these sample applications. - A microservice application that allows users to vote for their favorite emoji, and tracks votes received on a leaderboard. - Follow this to set up and deploy the BookInfo sample app on Istio using Meshery. - Httpbin is a simple HTTP request and response service. - Application that helps you manage your bookshelf. Identify overhead involved in running {{page.component}}, various {{page.component}} configurations while running different workloads and on different infrastructure. The adapter facilitates data plane and control plane performance testing. Prometheus integration Grafana integration
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-qry-select-case.md

layout: global title: CASE Clause displayTitle: CASE Clause 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. `CASE` clause uses a rule to return a specific result based on the specified condition, similar to if/else statements in other programming languages. ```sql CASE [ expression ] { WHEN booleanexpression THEN thenexpression } [ ... ] [ ELSE else_expression ] END ``` boolean_expression* Specifies any expression that evaluates to a result type `boolean`. Two or more expressions may be combined together using the logical operators ( `AND`, `OR` ). then_expression* Specifies the then expression based on the `booleanexpression` condition; `thenexpression` and `else_expression` should all be same type or coercible to a common type. else_expression* Specifies the default expression; `thenexpression` and `elseexpression` should all be same type or coercible to a common type. ```sql CREATE TABLE person (id INT, name STRING, age INT); INSERT INTO person VALUES (100, 'John', 30), (200, 'Mary', NULL), (300, 'Mike', 80), (400, 'Dan', 50); SELECT id, CASE WHEN id > 200 THEN 'bigger' ELSE 'small' END FROM person; ++--+ | id | CASE WHEN (id > 200) THEN bigger ELSE small END | ++--+ | 100 | small | | 200 | small | | 300 | bigger | | 400 | bigger | ++--+ SELECT id, CASE id WHEN 100 then 'bigger' WHEN id > 300 THEN '300' ELSE 'small' END FROM person; ++--+ | id | CASE WHEN (id = 100) THEN bigger WHEN (id = CAST((id > 300) AS INT)) THEN 300 ELSE small END | ++--+ | 100 | bigger | | 200 | small | | 300 | small | | 400 | small | ++--+ SELECT * FROM person WHERE CASE 1 = 1 WHEN 100 THEN 'big' WHEN 200 THEN 'bigger' WHEN 300 THEN 'biggest' ELSE 'small' END = 'small'; ++-+-+ | id | name | age | ++-+-+ | 100 | John | 30 | | 200 | Mary | NULL | | 300 | Mike | 80 | | 400 | Dan | 50 | ++-+-+ ```
Project: Meshery (Provisioning / Automation & Configuration)
File: github-actions-runners.md

layout: integration title: Github Actions Runners subtitle: Collaborative and visual infrastructure as code for Github Actions Runners image: /assets/img/integrations/github-actions-runners/icons/color/github-actions-runners-color.svg permalink: extensibility/integrations/github-actions-runners docURL: https://docs.meshery.io/extensibility/integrations/github-actions-runners description: integrations-category: App Definition and Development integrations-subcategory: Source Version Control registrant: Artifact Hub components: name: horizontal-runner-autoscaler colorIcon: assets/img/integrations/github-actions-runners/components/horizontal-runner-autoscaler/icons/color/horizontal-runner-autoscaler-color.svg whiteIcon: assets/img/integrations/github-actions-runners/components/horizontal-runner-autoscaler/icons/white/horizontal-runner-autoscaler-white.svg description: name: runner-deployment colorIcon: assets/img/integrations/github-actions-runners/components/runner-deployment/icons/color/runner-deployment-color.svg whiteIcon: assets/img/integrations/github-actions-runners/components/runner-deployment/icons/white/runner-deployment-white.svg description: name: runner-replica-set colorIcon: assets/img/integrations/github-actions-runners/components/runner-replica-set/icons/color/runner-replica-set-color.svg whiteIcon: assets/img/integrations/github-actions-runners/components/runner-replica-set/icons/white/runner-replica-set-white.svg description: name: runner colorIcon: assets/img/integrations/github-actions-runners/components/runner/icons/color/runner-color.svg whiteIcon: assets/img/integrations/github-actions-runners/components/runner/icons/white/runner-white.svg description: name: runner-set colorIcon: assets/img/integrations/github-actions-runners/components/runner-set/icons/color/runner-set-color.svg whiteIcon: assets/img/integrations/github-actions-runners/components/runner-set/icons/white/runner-set-white.svg description: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.156.md

layout: release date: 2023-10-10 tag: v0.6.156 Revert commits added by mistake @MUzairS15 (#9068) [UI] Added helm connection Wizard @Yashsharma1911 (#8965) Bulk Operations and Metadata Renderers @aabidsofi19 (#9018) [README.md] bold styling not applied to text @xiangpingjiang (#9054) added links in MeshMap Documentation @ATREAY (#9059) Thank you to our contributors for making this release possible: @ATREAY, @Aisuko, @MUzairS15, @Yashsharma1911, @aabidsofi19, @leecalcote and @xiangpingjiang
Project: StarRocks (App Definition and Development / Database)
File: datalakeIntro.md

In addition to efficient analytics of local data, StarRocks can work as the compute engine to analyze data stored in data lakes such as Apache Hudi, Apache Iceberg, and Delta Lake. One of the key features of StarRocks is its external catalog, which acts as the linkage to an externally maintained metastore. This functionality provides users with the capability to query external data sources seamlessly, eliminating the need for data migration. As such, users can analyze data from different systems such as HDFS and Amazon S3, in various file formats such as Parquet, ORC, and CSV, etc. The preceding figure shows a data lake analytics scenario where StarRocks is responsible for data computing and analysis, and the data lake is responsible for data storage, organization, and maintenance. Data lakes allow users to store data in open storage formats and use flexible schemas to produce reports on "single source of truth" for various BI, AI, ad-hoc, and reporting use cases. StarRocks fully leverages the advantages of its vectorization engine and CBO, significantly improving the performance of data lake analytics.
Project: YugabyteDB (App Definition and Development / Database)
File: expireat.md

title: EXPIREAT linkTitle: EXPIREAT description: EXPIREAT menu: preview: parent: api-yedis weight: 2062 aliases: /preview/api/redis/expireat /preview/api/yedis/expireat type: docs `EXPIREAT key ttl-as-timestamp` EXPIREAT has the same effect as EXPIRE, but instead of specifying the number of seconds representing the TTL (time to live), it takes an absolute Unix timestamp (seconds since January 1, 1970). A timestamp in the past will delete the key immediately. Returns integer reply, specifically 1 if the timeout was set and 0 if key does not exist. ```sh $ SET yugakey "Yugabyte" ``` ``` "OK" ``` ```sh $ EXPIREAT yugakey 1293840000 ``` ``` (integer) 1 ``` ```sh $ EXISTS yugakey ``` ``` (integer) 0 ``` , , ,
Project: KICS (Provisioning / Security & Compliance)
File: c759d6f2-4dd3-4160-82d3-89202ef10d87.md

title: MySQL Instance With Local Infile On hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c759d6f2-4dd3-4160-82d3-89202ef10d87 Query name: MySQL Instance With Local Infile On Platform: GoogleDeploymentManager Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: MySQL Instance should not have Local Infile On<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8" resources: name: db-instance type: sqladmin.v1beta4.instance properties: databaseVersion: MYSQL57 settings: databaseFlags: name: local_infile value: on ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: db-instance type: sqladmin.v1beta4.instance properties: databaseVersion: MYSQL57 settings: databaseFlags: name: local_infile value: off ``` ```yaml title="Negative test num. 2 - yaml file" resources: name: db-instance type: sqladmin.v1beta4.instance properties: databaseVersion: MYSQL57 settings: databaseFlags: name: logqueriesnotusingindexes value: on ```
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.1.0.3.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | Binary partitioner* New BinaryPartitioner that partitions BinaryComparable keys by hashing a configurable part of the bytes array corresponding to the key. | Major | We should always generate a new configure script for the c++ code* If you are compiling c++, the configure script will now be automatically regenerated as it should be. This requires autoconf version 2.61 or greater.
Project: Harbor (Provisioning / Container Registry)
File: 2-12-LDAP-user-push-multiple-images.md

Test 2-12 - User Push Multiple Images (LDAP Mode) ======= To verify that a non-admin user can push multiple images to a project in LDAP mode. User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against an LDAP or AD server. ( auth_mode is set to ldap_auth* .) The user data is stored in an LDAP or AD server. A linux host with Docker CLI installed (Docker client). At least a non-admin user and the user has at least a project as project admin. Same as Test 2-02 except that users are from LDAP/AD. Same as Test 2-02. None
Project: Trivy (Provisioning / Security & Compliance)
File: LICENSE.md

BSD 3-Clause License Copyright 2023 test All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: azure.md

+++ title = "Chef InSpec and Azure" draft = false gh_repo = "inspec" [menu] [menu.inspec] title = "Azure" identifier = "inspec/cloud/azure" parent = "inspec/cloud" +++ Chef InSpec has resources for auditing Azure. With Chef InSpec 4 or greater, you can create a profile for testing AWS resources with `inspec init profile`: ```bash $ inspec init profile --platform azure <PROFILE_NAME> Create new profile at /Users/me/<PROFILE_NAME> Creating directory libraries Creating file README.md Creating directory controls Creating file controls/example.rb Creating file inspec.yml Creating file inputs.yml Creating file libraries/.gitkeep ``` Assuming the `inputs.yml` file contains your Azure project ID, you can execute this sample profile using the following command: ```bash inspec exec <PROFILENAME> --input-file=<PROFILENAME>/inputs.yml -t gcp:// ``` To use Chef InSpec Azure resources, you will need to create a Service Principal Name (SPN) for auditing an Azure subscription. This can be done on the command line or from the Azure Portal: The information from the SPN can be specified either in the file `~/.azure/credentials`, as environment variables, or by using Chef InSpec target URIs. By default, Chef InSpec is configured to look at `~/.azure/credentials`, and it should contain: ```powershell [<SUBSCRIPTION_ID>] clientid = "<CLIENTID>" clientsecret = "<CLIENTSECRET>" tenantid = "<TENANTID>" ``` {{< note >}} In the Azure web portal, these values are labeled differently: The client_id is referred to as the 'Application ID' The client_secret is referred to as the 'Key (Password Type)' The tenant_id is referred to as the 'Directory ID' {{< /note >}} With the credentials in place, you can now execute Chef InSpec. ```bash inspec exec <PROFILE_NAME> -t azure:// ``` You may also set the Azure credentials via environment variables: `AZURESUBSCRIPTIONID` `AZURECLIENTID` `AZURECLIENTSECRET` `AZURETENANTID` For example: ```bash AZURESUBSCRIPTIONID="2fbdbb02-df2e-11e6-bf01-fe55135034f3" \ AZURECLIENTID="58dc4f6c-df2e-11e6-bf01-fe55135034f3" \ AZURECLIENTSECRET="Jibr4iwwaaZwBb6W" \ AZURETENANTID="6ad89b58-df2e-11e6-bf01-fe55135034f3" inspec exec my-profile -t azure:// ``` If you have created a `~/.azure/credentials` file as above, you may also use the Chef InSpec command line `--target` / `-t` option to select a subscription ID. For example: ```bash inspec exec my-profile -t azure://2fbdbb02-df2e-11e6-bf01-fe55135034f3 ``` {{< inspec/inspec_resources platform="azure" >}}
Project: Ansible (Provisioning / Automation & Configuration)
File: proposal.md

Hi! Ansible has a Proposal process for large feature ideas or changes in current design and functionality, such as this. If you are still interested in seeing this new feature get into Ansible, please submit a proposal for it using this process. <https://github.com/ansible/proposals/blob/master/proposalsprocessproposal.md> Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time. The mailing list and irc are great ways to ask questions, or post if you don't think this particular issue is resolved. #ansible-devel on <https://groups.google.com/forum/#!forum/ansible-devel> Or check this page for a more complete list of communication channels and their purposes: <https://docs.ansible.com/ansible/latest/community/communication.html> Thank you!
Project: Chef InSpec (Provisioning / Security & Compliance)
File: waivers.md

+++ title = "Waivers" draft = false gh_repo = "inspec" [menu] [menu.inspec] title = "Waivers" identifier = "inspec/Waivers" parent = "inspec" weight = 110 +++ Waivers allow you to waive controls and to dictate the running and/or reporting of those controls. A waiver file identifies: which controls are waived a description of why it is waived (optionally) whether they should be skipped from running (optionally) an expiration date for the waiver Chef InSpec supports waiver files in YAML, JSON, or CSV file formats. To use a waiver file, invoke `inspec exec` with `--waiver-file [path]`. For example: ```bash inspec exec path/to/profile --waiver-file waivers.yaml ``` Specify the following parameters in the waiver file: `control_id` required : The ID of the control to be waived. `expiration_date` optional : The expiration date of the waiver file in YYYY-MM-DD format. Waiver files expire at 00:00 at the local time of the system on the specified date. Waiver files without an expiration date are permanent. `run` optional : If absent, `true`, or `yes`, the control will run and be reported, but failures in the control won't make the overall run fail. If `false` or `no`, the control will not run. You may use any of `yes`, `no`, `true`, or `false`. To avoid confusion, you should explicitly specify whether the control should run or not. `justification` required : A description of the waiver. This might include a reason for the waiver or the person who signed off on the waiver. Example in YAML: ```yaml waivercontrol123: expiration_date: 2019-10-15 justification: Not needed until Q3. @secteam xccdforg.cisecurity.benchmarksrule1.1.1.4Ensuremountingofhfsfilesystemsisdisabled: expiration_date: 2020-03-01 justification: "This might be a bug in the test. @qateam" run: false ``` Example in JSON: ```json { "waivercontrol123": { "expiration_date": "2019-10-15T00:00:00.000Z", "justification": "Not needed until Q3. @secteam" }, "xccdforg.cisecurity.benchmarksrule1.1.1.4Ensuremountingofhfsfilesystemsisdisabled": { "expiration_date": "2020-03-01T00:00:00.000Z", "justification": "This might be a bug in the test. @qateam", "run": false } } ``` Example in CSV: ```plain controlid,justification,run,expirationdate waivercontrol123,Not needed until Q3,TRUE,2019-10-15T00:00:00.000Z xccdforg.cisecurity.benchmarksrule1.1.1.4Ensuremountingofhfsfilesystemsisdisabled,This might be a bug in the test. @qateam,FALSE,2020-03-01T00:00:00.000Z ``` which looks like this: | controlid | justification | run | expirationdate | |||-|--| | waivercontrol123 | Not needed until Q3 | TRUE | 2019-10-15T00:00:00.000Z | | xccdforg.cisecurity.benchmarksrule1.1.1.4Ensuremountingofhfsfilesystemsisdisabled | This might be a bug in the test. @qateam | FALSE | 2020-03-01T00:00:00.000Z |
Project: ClickHouse (App Definition and Development / Database)
File: approxtopk.md

slug: /en/sql-reference/aggregate-functions/reference/approxtopk sidebar_position: 212 Returns an array of the approximately most frequent values and their counts in the specified column. The resulting array is sorted in descending order of approximate frequency of values (not by the values themselves). ``` sql approxtopk(N)(column) approxtopk(N, reserved)(column) ``` This function does not provide a guaranteed result. In certain situations, errors might occur and it might return frequent values that arent the most frequent values. We recommend using the `N < 10` value; performance is reduced with large `N` values. Maximum value of `N = 65536`. Parameters `N` The number of elements to return. Optional. Default value: 10. `reserved` Defines, how many cells reserved for values. If uniq(column) > reserved, result of topK function will be approximate. Optional. Default value: N * 3. Arguments `column` The value to calculate frequency. Example Query: ``` sql SELECT approxtopk(2)(k) FROM VALUES('k Char, w UInt64', ('y', 1), ('y', 1), ('x', 5), ('y', 1), ('z', 10)); ``` Result: ``` text approxtopk(2)(k) [('y',3,0),('x',1,0)] ``` Is an alias to `approxtopk` function See Also