cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 28727987-e398-49b8-aef1-8a3e7789d111.md

title: IP Aliasing Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 28727987-e398-49b8-aef1-8a3e7789d111 Query name: IP Aliasing Disabled Platform: GoogleDeploymentManager Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Kubernetes Clusters must be created with Alias IP ranges enabled, which means the attribute 'ipAllocationPolicy' must be defined and the subattribute 'useIpAliases' must be set to 'true'.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" resources: name: cluster type: container.v1.cluster properties: description: my-cluster ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="6" resources: name: cluster type: container.v1.cluster properties: description: my-cluster ipAllocationPolicy: subnetworkName: my-network ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="8" resources: name: cluster type: container.v1.cluster properties: description: my-cluster ipAllocationPolicy: subnetworkName: my-network useIpAliases: false ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: cluster type: container.v1.cluster properties: description: my-cluster ipAllocationPolicy: subnetworkName: my-network useIpAliases: true ```
Project: TDengine (App Definition and Development / Database)
File: 18-escape.md

title: Escape Characters description: This document describes the usage of escape characters in TDengine. | Escape Character | Actual Meaning | | :--: | | | `\'` | Single quote `'` | | `\"` | Double quote `"` | | `\n` | Line Break | | `\r` | Carriage Return | | `\t` | tab | | `\\` | Back Slash `\ ` | | `\%` | `%` see below for details | | `\` | `` see below for details | If there are escape characters in identifiers (database name, table name, column name) Identifier without ``: Error will be returned because identifier must be constituted of digits, ASCII characters or underscore and can't be started with digits Identifier quoted with ``: Original content is kept, no escaping If there are escape characters in values The escape characters will be escaped as the above table. If the escape character doesn't match any supported one, the escape character `\ ` will be ignored(`\x` remaining). `%` and `` are used as wildcards in `like`. `\%` and `\` should be used to represent literal `%` and `` in `like`. If `\%` and `\` are used out of `like` context, the evaluation result is `\%` and `\`, instead of `%` and ``.
Project: Flink (App Definition and Development / Streaming & Messaging)
File: blackhole.md

title: BlackHole weight: 15 type: docs aliases: /dev/table/connectors/blackhole.html <!-- 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. --> {{< label "Sink: Bounded" >}} {{< label "Sink: UnBounded" >}} The BlackHole connector allows for swallowing all input records. It is designed for: high performance testing. UDF to output, not substantive sink. Just like /dev/null device on Unix-like operating systems. The BlackHole connector is built-in. How to create a BlackHole table ```sql CREATE TABLE blackhole_table ( f0 INT, f1 INT, f2 STRING, f3 DOUBLE ) WITH ( 'connector' = 'blackhole' ); ``` Alternatively, it may be based on an existing schema using the . ```sql CREATE TABLE blackhole_table WITH ('connector' = 'blackhole') LIKE source_table (EXCLUDING ALL) ``` Connector Options <table class="table table-bordered"> <thead> <tr> <th class="text-left" style="width: 25%">Option</th> <th class="text-center" style="width: 8%">Required</th> <th class="text-center" style="width: 7%">Default</th> <th class="text-center" style="width: 10%">Type</th> <th class="text-center" style="width: 50%">Description</th> </tr> </thead> <tbody> <tr> <td><h5>connector</h5></td> <td>required</td> <td style="word-wrap: break-word;">(none)</td> <td>String</td> <td>Specify what connector to use, here should be 'blackhole'.</td> </tr> </tbody> </table>
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.54.md

layout: release date: 2021-09-08 tag: v0.5.54 [Install] Adapter: Kubernetes Manifests for NGINX Service Mesh @SirZeck (#4118) [Install] K8s: Enable 'meshery-server' Service Account with approve p @leecalcote (#4114) [Install] Kubernetes: Support v1.22 CRD v1 @leecalcote (#4115) Fix performance profile retrieval issue @utkarsh-pro (#4109) [Meshery] Lifecycle: move off deprecated alpha API for CRDs @leecalcote (#4104) migrate to meshkit errors in reset.go/ restart.go @nehaLohia27 (#3901) Fetch manifest if not present during `system stop` for kubernetes @suhaniii (#4083) Refactor YAML structure to a single file (for mesheryctl reference) @alphaX86 (#3985) [Pattern] add default value for pattern files, capitalize each word as title prop @bariqhibat (#4116) Fix Pattern syncup with rjsf form @Abhishek-kumar09 (#4085) [UI] User Preferences: Display Wait Indicator @K-Kumar-01 (#4106) [UI] [Connection Wizard] Change operator inactive state color @sudo-NithishKarthik (#4012) [Extensions] dependency add for meshery extensions @bariqhibat (#4112) [UI] Supports accordion style menu in collapsed menu drawer @CipherGirl (#3890) Added DelusionalOptimist to CI Maintainers @adithyaakrishna (#4099) Refactor YAML structure to a single file (for mesheryctl reference) @alphaX86 (#3985) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @CipherGirl, @K-Kumar-01, @SirZeck, @adithyaakrishna, @alphaX86, @bariqhibat, @leecalcote, @nehaLohia27, @sudo-NithishKarthik, @suhaniii and @utkarsh-pro
Project: KICS (Provisioning / Security & Compliance)
File: 52ffcfa6-6c70-4ea6-8376-d828d3961669.md

title: CloudTrail Log File Validation Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 52ffcfa6-6c70-4ea6-8376-d828d3961669 Query name: CloudTrail Log File Validation Disabled Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: CloudTrail log file validation should be enabled to determine whether a log file has not been tampered<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1 9" resource "aws_cloudtrail" "positive1" { name = "positive1" s3bucketname = "bucketlog1" } resource "aws_cloudtrail" "positive2" { name = "positive2" s3bucketname = "bucketlog2" enablelogfile_validation = false } ``` ```tf title="Negative test num. 1 - tf file" resource "aws_cloudtrail" "negative1" { name = "negative1" s3bucketname = "bucketlog1" enablelogfile_validation = true } ```
Project: ShardingSphere (App Definition and Development / Database)
File: notice.en.md

title: Notice description : "Disclaimers to help you structure your page" The notice shortcode shows 4 types of disclaimers to help you structure your page. ``` {{%/ notice note /%}} A notice disclaimer {{%/ /notice /%}} ``` renders as {{% notice note %}} A notice disclaimer {{% /notice %}} ``` {{%/ notice info /%}} An information disclaimer {{%/ /notice /%}} ``` renders as {{% notice info %}} An information disclaimer {{% /notice %}} ``` {{%/ notice tip /%}} A tip disclaimer {{%/ /notice /%}} ``` renders as {{% notice tip %}} A tip disclaimer {{% /notice %}} ``` {{%/ notice warning /%}} A warning disclaimer {{%/ /notice /%}} ``` renders as {{% notice warning %}} A warning disclaimer {{% /notice %}}
Project: Meshery (Provisioning / Automation & Configuration)
File: aws-dynamodb-controller.md

layout: integration title: AWS DynamoDB subtitle: Collaborative and visual infrastructure as code for AWS DynamoDB image: /assets/img/integrations/aws-dynamodb-controller/icons/color/aws-dynamodb-controller-color.svg permalink: extensibility/integrations/aws-dynamodb-controller docURL: https://docs.meshery.io/extensibility/integrations/aws-dynamodb-controller description: integrations-category: App Definition and Development integrations-subcategory: Database registrant: GitHub components: name: field-export colorIcon: assets/img/integrations/aws-dynamodb-controller/components/field-export/icons/color/field-export-color.svg whiteIcon: assets/img/integrations/aws-dynamodb-controller/components/field-export/icons/white/field-export-white.svg description: name: adopted-resource colorIcon: assets/img/integrations/aws-dynamodb-controller/components/adopted-resource/icons/color/adopted-resource-color.svg whiteIcon: assets/img/integrations/aws-dynamodb-controller/components/adopted-resource/icons/white/adopted-resource-white.svg description: name: backup colorIcon: assets/img/integrations/aws-dynamodb-controller/components/backup/icons/color/backup-color.svg whiteIcon: assets/img/integrations/aws-dynamodb-controller/components/backup/icons/white/backup-white.svg description: name: table colorIcon: assets/img/integrations/aws-dynamodb-controller/components/table/icons/color/table-color.svg whiteIcon: assets/img/integrations/aws-dynamodb-controller/components/table/icons/white/table-white.svg description: name: global-table colorIcon: assets/img/integrations/aws-dynamodb-controller/components/global-table/icons/color/global-table-color.svg whiteIcon: assets/img/integrations/aws-dynamodb-controller/components/global-table/icons/white/global-table-white.svg description: featureList: [ "Handle more than 10 trillion requests per day and can support peaks of more than 20 million requests per second. ", "Secure your data with encryption at rest, automatic backup and restore, and guaranteed reliability with an SLA of up to 99.999% availability.", "Fast and flexible NoSQL database service for any scale" ] 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.7.40.md

layout: release date: 2024-03-29 tag: v0.7.40 Relationship between AWS FieldExport and k8s resources. @RipulHandoo (#10535) Add meshery-nighthawk helm chart @lekaf974 (#10581) feat: Mesheryctl Connections command @RipulHandoo (#10516) Improve some UI elements in dashboard @sudhanshutech (#10628) UI Extension: GitHub Action - Performance Analysis @leecalcote (#10625) [RTK] Migrate User component to rtk @dottharun (#10270) fix(MesheryPatterns): update designs data when updating information through info modal @dragon-slayer875 (#10620) feat(docs): add error code name to search link (#10635) @elasticspoon (#10638) [DOCS] replace backticks with bold formatting @iArchitSharma (#10633) [Docs]: Updating Docs for Contributing to Model Relationships @pandeyshubham03 (#10627) Suggested Reading added in default Layout @iArchitSharma (#10611) Thank you to our contributors for making this release possible: @MUzairS15, @RipulHandoo, @Yashsharma1911, @dottharun, @dragon-slayer875, @elasticspoon, @iArchitSharma, @leecalcote, @lekaf974, @pandeyshubham03 and @sudhanshutech
Project: StarRocks (App Definition and Development / Database)
File: SHOW_PROPERTY.md

displayed_sidebar: "English" Views the properties of a user. Currently, only the maximum number of connections can be viewed using this command. :::tip The current user can view its own property. Only users with the `user_admin` role can view the property of other users. ::: ```SQL SHOW PROPERTY [FOR 'username'] [LIKE 'maxuser_connections'] ``` | Parameter | Required | Description | | -- | -- | -- | | user_name | No | The user name. If not specified, the property of the current user is viewed. | | maxuserconnections | No | The maximum number of connections for a user. | Example 1: View the maximum number of connections for the current user. ```Plain SHOW PROPERTY; +-+-+ | Key | Value | +-+-+ | maxuserconnections | 10000 | +-+-+ ``` Example 2: View the maximum number of connections for user `jack`. ```SQL SHOW PROPERTY FOR 'jack'; ``` Or ```SQL SHOW PROPERTY FOR 'jack' LIKE 'maxuserconnections'; ``` ```Plain +-+-+ | Key | Value | +-+-+ | maxuserconnections | 100 | +-+-+ ``` : Sets the maximum number of connections for a user.
Project: KICS (Provisioning / Security & Compliance)
File: e6b4b943-6883-47a9-9739-7ada9568f8ca.md

title: EBS Volume Snapshot Not Encrypted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e6b4b943-6883-47a9-9739-7ada9568f8ca Query name: EBS Volume Snapshot Not Encrypted Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: The value on AWS EBS Volume Snapshot Encryptation must be true<br> ```tf title="Positive test num. 1 - tf file" hl_lines="4" resource "awsebsvolume" "positive1" { availability_zone = "us-west-2a" size = 40 encrypted = false tags = { Name = "HelloWorld" } } resource "awsebssnapshot" "positive1" { volumeid = awsebs_volume.positive1.id tags { Name = "Production" } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="10" resource "awsebsvolume" "positive2" { availability_zone = "us-west-2a" size = 40 tags = { Name = "HelloWorld" } } resource "awsebssnapshot" "positive2" { volumeid = awsebs_volume.positive2.id tags { Name = "Production" } } ``` ```tf title="Negative test num. 1 - tf file" resource "awsebsvolume" "negative1" { availability_zone = "us-west-2a" size = 40 encrypted = true tags = { Name = "HelloWorld" } } resource "awsebssnapshot" "negative1" { volumeid = awsebs_volume.negative1.id tags { Name = "Production" } } ```
Project: KICS (Provisioning / Security & Compliance)
File: 592ad21d-ad9b-46c6-8d2d-fad09d62a942.md

title: Permissive Access to Create Pods hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 592ad21d-ad9b-46c6-8d2d-fad09d62a942 Query name: Permissive Access to Create Pods Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: The permission to create pods in a cluster should be restricted because it allows privilege escalation.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="39 9 48 21 60 30" apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: secret-reader rules: apiGroups: [""] resources: ["pods"] verbs: "get" "watch" create apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: secret-reader2 rules: apiGroups: [""] resources: ["*"] verbs: ["get", "watch", "create"] apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: secret-reader3 rules: apiGroups: [""] resources: ["pods"] verbs: ["get", "watch", "*"] apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: secret-reader4 rules: apiGroups: [""] resources: ["*"] verbs: ["get", "watch", "*"] apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: secret-reader5 rules: apiGroups: [""] resources: ["pods"] verbs: "get" "watch" "c*e" apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: secret-reader6 rules: apiGroups: [""] resources: ["p*ds"] verbs: ["get", "watch", "create"] ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="26" apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: secret-reader rules: apiGroups: "*" resources: "*" verbs: get list watch apiGroups: apiextensions.k8s.io resources: custom verbs: create delete apiGroups: "*" resources: "*" verbs: create delete get list patch update watch ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: secret-reader rules: apiGroups: [""] resources: ["pods"] verbs: ["get", "watch", "list"] apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: secret-reader2 rules: apiGroups: [""] resources: ["secrets"] verbs: ["get", "watch", "create"] apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: secret-reader4 rules: apiGroups: [""] resources: ["pods"] verbs: "get" "watch" ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: secret-reader rules: apiGroups: apiextensions.k8s.io resources: "*" verbs: create delete ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 06_io_tfrecord.md

Prompt: Write a sample Java code snippet that writes data to a TFRecord file using Apache Beam. Response: Your Apache Beam pipeline can write data to a TFRecord file using the Apache Beam TFRecordIO connector. Here is an example of how to use the TFRecordIO connector to accomplish this: ```java package tfrecord; import org.apache.beam.sdk.Pipeline; import org.apache.beam.sdk.io.Compression; import org.apache.beam.sdk.io.TFRecordIO; import org.apache.beam.sdk.options.Description; import org.apache.beam.sdk.options.PipelineOptions; import org.apache.beam.sdk.options.PipelineOptionsFactory; import org.apache.beam.sdk.options.Validation; import org.apache.beam.sdk.transforms.Create; import org.apache.beam.sdk.transforms.DoFn; import org.apache.beam.sdk.transforms.ParDo; import org.apache.beam.vendor.guava.v3212_jre.com.google.common.base.Charsets; import java.util.Arrays; import java.util.List; // Pipeline to write data to a TFRecord file using Apache Beam. public class WriteTFRecordFile { // Pipeline options for writing data to a TFRecord file. public interface WriteTFRecordFileOptions extends PipelineOptions { @Description("File path prefix to write TFRecords files to") @Validation.Required String getFilePathPrefix(); void setFilePathPrefix(String filePathPrefix); } // Main method to run the pipeline public static void main(String[] args) { // Parse the pipeline options from the command line WriteTFRecordFileOptions options = PipelineOptionsFactory.fromArgs(args) .withValidation().as(WriteTFRecordFileOptions.class); // Create the pipeline Pipeline p = Pipeline.create(options); // Create a list of sample records List<String> records = Arrays.asList( "Record 1", "Record 2", "Record 3", "Record 4", "Record 5" ); // Create a PCollection of sample records p.apply("Create collection of records", Create.of(records)) // Convert each record to bytes using a DoFn .apply( "Convert records to bytes", ParDo.of( new DoFn<String, byte[]>() { @DoFn.ProcessElement public void processElement(ProcessContext c) { c.output(c.element().getBytes(Charsets.UTF_8)); } })) // Write the records to a TFRecord file .apply( "Write to TFRecord file", TFRecordIO.write() .to(options.getFilePathPrefix()) .withCompression(Compression.UNCOMPRESSED) .withNumShards(1)); // Run the pipeline p.run(); } } ``` This code snippet utilizes the pipeline options pattern to parse command-line arguments.
Project: KICS (Provisioning / Security & Compliance)
File: getting-started.md

``` docker run -t -v {pathtohostfolderto_scan}:/path checkmarx/kics:latest scan -p /path -o "/path/" ``` ``` docker run -t -v {pathtohost_folder}:/path checkmarx/kics:latest scan -p /path/{filename}.{extension} -o "/path/" ``` ](https://raw.githubusercontent.com/Checkmarx/kics/23c62655308523e1bf6aa8ae5852848deb263651/docs/img/faster.gif)
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: sbom-image-purl-output.md

When generating SBOMs, scan them for PURL ([package URL](https://github.com/package-url/purl-spec/blob/master/PURL-SPECIFICATION.rst)) information, and save a list of found PURLs to the specified path in the output image. There is no default.
Project: ArangoDB (App Definition and Development / Database)
File: keeping_state.md

+++ title = "Keeping state" description = "" weight = 10 tags = ["backtrace"] +++ The first thing we are going to need is somewhere to store the stack backtrace. We could take the easier route and simply store it into an allocated block and keep the pointer as a custom payload in a `result<T, std::pair<errorcode, std::uniqueptr<stack_backtrace>>>` (see previous section on ). But let us assume that we care so deeply about bounded execution times that ever calling `malloc` is unacceptable. We therefore are going to need some completely static and trivially typed storage perhaps kept per-thread to avoid the need to keep mutexes. {{% snippet "errorcodeextended.cpp" "errorcodeextended1" %}} The extended error info is kept in a sixteen item long, thread local, ring buffer. We continuously increment the current index pointer which is a 16 bit value which will wrap after 65,535. This lets us detect an attempt to access recycled storage, and thus return item-not-found instead of the wrong extended error info.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.134.md

layout: release date: 2023-09-01 tag: v0.6.134 Add `visibility` query param to the `/api/filter` endpoint @Aritra8438 (#8555) [CI] MeshKit Error Util: duplicate errors causing failures @suhail34 (#8450) disable cypress fail on uncaught exception or unhandled promise rejec @MarioArriaga92 (#8641) Display notification according access of role on publish designs/filters @sudhanshutech (#8480) [UI] Connections: External Link and Light Mode Issue @senali-d (#8540) feat: added icon to show the current status of adapter deployement @Yana-Gupta (#8586) Export RJSFWrapper to Extension Point @Yashsharma1911 (#8639) fix: hide navbar and sidebar in fullscreen mode @Udit-takkar (#8611) Bump cypress from 12.17.4 to 13.1.0 in /provider-ui @dependabot (#8631) Bump @mui/material from 5.14.3 to 5.14.7 in /provider-ui @dependabot (#8634) Bump cypress from 12.17.4 to 13.1.0 in /provider-ui @dependabot (#8631) Bump @mui/material from 5.14.3 to 5.14.7 in /provider-ui @dependabot (#8634) Thank you to our contributors for making this release possible: @Aritra8438, @MarioArriaga92, @Udit-takkar, @Yana-Gupta, @Yashsharma1911, @dependabot, @dependabot[bot], @leecalcote, @senali-d, @sudhanshutech and @suhail34
Project: YDB (App Definition and Development / Database)
File: limit_offset.md

`LIMIT`: limits the output to the specified number of rows. By default, the output is not restricted. `OFFSET`: specifies the offset from the beginning (in rows). By default, it's zero. Examples ```yql SELECT key FROM my_table LIMIT 7; ``` ```yql SELECT key FROM my_table LIMIT 7 OFFSET 3; ``` ```yql SELECT key FROM my_table LIMIT 3, 7; -- equivalent to the previous example ```
Project: Harbor (Provisioning / Container Registry)
File: 1-08-admin-log-in-log-out.md

Test 1-08 - Admin User Log In and Log Out (DB Mode or LDAP mode) ======= To verify that an admin user can log in and log out. User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database or LDAP server. A linux host with Docker CLI installed (Docker client). The admin user logs in to the UI by username. The admin user logs out from the UI. Use the incorrect password of the admin user to log in to the UI and check the error message. On a Docker client host, use `docker login <harbor_host>` command to verify the admin user can log in. Use `docker login <harbor_host>` command to log in with incorrect password. The admin user can log in/out successfully in Step 1 & 2. The error message in Step 3 should not show which input value is incorrect. It should only display the username and password combination is incorrect. Docker client can log in in Step 4. Docker client fails to log in in Step 5. None