cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: d2731f3d-a992-44ed-812e-f4f1c2747d71.md

title: VPC Flow Logs Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d2731f3d-a992-44ed-812e-f4f1c2747d71 Query name: VPC Flow Logs Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Every VPC resource should have an associated Flow Log<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "alicloud_vpc" "main" { cidr_block = "192.168.0.0/24" name = var.name } resource "alicloudvpcflow_log" "default" { dependson = ["alicloudvpc.default"] resourceid = alicloudvpc.default.id resource_type = "VPC" traffic_type = "All" logstorename = var.logstorename projectname = var.projectname flowlogname = var.name status = "Active" } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloud_vpc" "main" { cidr_block = "192.168.0.0/24" name = var.name } resource "alicloudvpcflow_log" "default" { dependson = ["alicloudvpc.main"] resourceid = alicloudvpc.main.id resource_type = "VPC" traffic_type = "All" logstorename = var.logstorename projectname = var.projectname flowlogname = var.name status = "Active" } ```
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: hab_setup.md

+++ title = "Configure the Chef Habitat CLI" description = "Set up the Chef Habitat CLI" gh_repo = "habitat" [menu] [menu.habitat] title = "Set up the Chef Habitat CLI" identifier = "habitat/install/hab-setup Install Chef Habitat" parent = "habitat/install" weight = 20 +++ Once Chef Habitat has been installed, the `hab` CLI makes it easy to get your workstation configured by guiding through the setup process. To set up your workstation, run `hab cli setup` and follow the instructions. <img alt="screenshot of hab cli setup output in CLI" src="/images/habitat/hab-setup.png"> Setup asks you to create a new origin and a set of origin keys. Optionally, you can also provide a Chef Habitat personal access token to upload packages to the public depot and share them with the Chef Habitat community. See the for details on generating and using your access token. For more information about using Chef Habitat Builder, see the section on . You will also be asked if you want to register Supervisor control gateway secret (see for further details). You can change your settings at any time by re-running the `hab cli setup` command. <img alt="screenshot of completed hab cli setup in CLI" src="/images/habitat/hab-setup-complete.png"> That's it. You're all set up and ready to use Chef Habitat to build and run packages!
Project: Scylla (App Definition and Development / Database)
File: ISSUE_TEMPLATE.md

This is Scylla's bug tracker, to be used for reporting bugs only. If you have a question about Scylla, and not a bug, please ask it in our mailing-list at scylladb-dev@googlegroups.com or in our slack channel. [] I have read the disclaimer above, and I am reporting a suspected malfunction in Scylla. Installation details Scylla version (or git commit hash): Cluster size: OS (RHEL/CentOS/Ubuntu/AWS AMI): Hardware details (for performance issues) Delete if unneeded Platform (physical/VM/cloud instance type/docker): Hardware: sockets= cores= hyperthreading= memory= Disks: (SSD/HDD, count)
Project: Kapitan (Provisioning / Automation & Configuration)
File: kap_8_modularize_kapitan.md

Kapitan is packaged in PYPI and as a binary along with all its dependencies. Adding an extra key/security backend means that we need to ship another dependency with that PYPI package, making deploying changes more complicated. This project would modularize kapitan into core dependencies and extra modules. ```sh pip3 install --user kapitan # to install only core dependencies Pip3 install --user kapitan[gkms] # gkms is the module ``` The main module includes the essential kapitan dependencies and reclass dependencies, which will be included in the requirement.txt file. The extra module will be defined in the `setup.py` file. The extra dependencies are of secret backends like (AWS Key backend, Google KMS Key backend, Vault Key backend etc.) and Helm support.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: file.md

Specifies a Containerfile which contains instructions for building the image, either a local file or an http or https URL. If more than one Containerfile is specified, FROM instructions are only be accepted from the last specified file. If a build context is not specified, and at least one Containerfile is a local file, the directory in which it resides is used as the build context. Specifying the option `-f -` causes the Containerfile contents to be read from stdin.
Project: KICS (Provisioning / Security & Compliance)
File: ebb2118a-03bc-4d53-ab43-d8750f5cb8d3.md

title: CloudTrail Not Integrated With CloudWatch hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ebb2118a-03bc-4d53-ab43-d8750f5cb8d3 Query name: CloudTrail Not Integrated With CloudWatch Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: CloudTrail should be integrated with CloudWatch<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="2 27 14" name: positive1 community.aws.cloudtrail: state: present name: default s3bucketname: mylogbucket region: us-east-1 ismultiregion_trail: true enablelogfile_validation: true kmskeyid: "alias/MyAliasName" tags: environment: dev Name: default name: positive2 community.aws.cloudtrail: state: present name: default s3bucketname: mylogbucket region: us-east-1 ismultiregion_trail: true enablelogfile_validation: true cloudwatchlogsrolearn: "arn:aws:iam::123456789012:role/CloudTrailCloudWatchLogs_Role" kmskeyid: "alias/MyAliasName" tags: environment: dev Name: default name: positive3 community.aws.cloudtrail: state: present name: default s3bucketname: mylogbucket region: us-east-1 ismultiregion_trail: true enablelogfile_validation: true cloudwatchlogsloggrouparn: "arn:aws:logs:us-east-1:123456789012:log-group:CloudTrail/DefaultLogGroup:*" kmskeyid: "alias/MyAliasName" tags: environment: dev Name: default ``` ```yaml title="Negative test num. 1 - yaml file" name: create multi-region trail with validation and tags negative community.aws.cloudtrail: state: present name: default s3bucketname: mylogbucket region: us-east-1 ismultiregion_trail: true enablelogfile_validation: true cloudwatchlogsrolearn: "arn:aws:iam::123456789012:role/CloudTrailCloudWatchLogs_Role" cloudwatchlogsloggrouparn: "arn:aws:logs:us-east-1:123456789012:log-group:CloudTrail/DefaultLogGroup:*" kmskeyid: "alias/MyAliasName" tags: environment: dev Name: default ```
Project: ArangoDB (App Definition and Development / Database)
File: tryx_failure_likely.md

+++ title = "`BOOSTOUTCOMETRYXFAILURELIKELY(expr)`" description = "Evaluate an expression which results in an understood type, emitting the `T` if successful, immediately returning `tryoperationreturn_as(X)` from the calling function if unsuccessful." +++ Evaluate an expression which results in a type matching the following customisation points, emitting the `T` if successful, immediately returning {{% api "tryoperationreturn_as(X)" %}} from the calling function if unsuccessful: `BOOSTOUTCOMEV2NAMESPACE::`{{% api "tryoperationhasvalue(X)" %}} `BOOSTOUTCOMEV2NAMESPACE::`{{% api "tryoperationreturnas(X)" %}} `BOOSTOUTCOMEV2NAMESPACE::`{{% api "tryoperationextractvalue(X)" %}} Default overloads for these customisation points are provided. See . Hints are given to the compiler that the expression will be unsuccessful. If you expect success, you should use {{% api "BOOSTOUTCOMETRYX(expr)" %}} instead. An internal temporary to hold the value of the expression is created, which generally invokes a copy/move. Availability: GCC and clang only. Use `#ifdef BOOSTOUTCOMETRYX` to determine if available. Overridable: Not overridable. Definition: See {{% api "BOOSTOUTCOMETRYV(expr)" %}} for most of the mechanics. This macro makes use of a proprietary extension in GCC and clang to emit the `T` from a successful expression. You can thus use `BOOSTOUTCOMETRYX(expr)` directly in expressions e.g. `auto x = y + BOOSTOUTCOMETRYX(foo(z));`. Be aware there are compiler quirks in preserving the rvalue/lvalue/etc-ness of emitted `T`'s, specifically copy or move constructors may be called unexpectedly and/or copy elision not work as expected. If these prove to be problematic, use {{% api "BOOSTOUTCOMETRY(var, expr)" %}} instead. Header: `<boost/outcome/try.hpp>`
Project: StarRocks (App Definition and Development / Database)
File: url_decode.md

displayed_sidebar: "English" Translates a string back from the format. This function is an inverse of . This functions is supported from v3.2. ```haskell VARCHAR url_decode(VARCHAR str) ``` `str`: the string to decode. If `str` is not a string, the system will try implicit cast first. Returns a decoded string. ```plaintext mysql> select urldecode('https%3A%2F%2Fdocs.starrocks.io%2Fdocs%2Fintroduction%2FStarRocksintro%2F'); ++ | urldecode('https%3A%2F%2Fdocs.starrocks.io%2Fdocs%2Fintroduction%2FStarRocksintro%2F') | ++ | https://docs.starrocks.io/docs/introduction/StarRocks_intro/ | ++ ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: preserve-fd.md

Pass down to the process the additional file descriptors specified in the comma separated list. It can be specified multiple times. This option is only supported with the crun OCI runtime. It might be a security risk to use this option with other OCI runtimes. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines)
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-error-conditions-unsupported-call-error-class.md

layout: global title: UNSUPPORTED_CALL error class displayTitle: UNSUPPORTED_CALL error class 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. <!-- DO NOT EDIT THIS FILE. It was generated automatically by `org.apache.spark.SparkThrowableSuite`. --> Cannot call the method "`<methodName>`" of the class "`<className>`". This error class has the following derived error classes: The row shall have a schema to get an index of the field `<fieldName>`.
Project: YugabyteDB (App Definition and Development / Database)
File: managed-cli-peering.md

title: ybm CLI vpc peering resource headerTitle: ybm vpc peering linkTitle: vpc peering description: YugabyteDB Managed CLI reference VPC Peering resource. headcontent: Manage account peering connections menu: preview_yugabyte-cloud: identifier: managed-cli-peering parent: managed-cli-reference weight: 20 type: docs Use the `vpc peering` resource to perform operations on , including the following: create and delete peering connections get information about a peering connection ```text Usage: ybm vpc peering [command] [flags] ``` Create a peering connection on GCP: ```sh ybm vpc peering create \ --name demo-peer \ --yb-vpc-name demo-vpc \ --cloud-provider GCP \ --app-vpc-project-id project \ --app-vpc-name application-vpc-name \ --app-vpc-cidr 10.0.0.0/18 ``` Create a peering connection. | Flag | Description | | : | : | | --name | Required. Name for the peering. | | --yb-vpc-name | Required. Name of the YugabyteDB VPC to be peered. | | --cloud-provider | Required. Cloud provider of the VPC being peered. `AWS` or `GCP`. | | --app-vpc-project-id | Required for GCP. Project ID of the application VPC being peered. GCP only. | | --app-vpc-name | Required for GCP. Name of the application VPC being peered. GCP only. | | --app-vpc-cidr | Required for AWS. CIDR of the application VPC. Optional for GCP. | | --app-vpc-account-id | Required for AWS. Account ID of the application VPC. AWS only. | | --app-vpc-id | Required for AWS. ID of the application VPC. AWS only. | | --app-vpc-region | Required for AWS. Region of the application VPC. AWS only. | Delete a specified peering connection. | Flag | Description | | : | : | | --name | Required. Name of the peering connection. | List the VPC peering connections configured for your account. | Flag | Description | | : | : | | --name | Name of a peering. |
Project: MySQL (App Definition and Development / Database)
File: LICENSE.md

MIT License Copyright (c) 2014-2017 Pavel Kalvoda Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Project: KICS (Provisioning / Security & Compliance)
File: 4c7ebcb2-eae2-461e-bc83-456ee2d4f694.md

title: Stackdriver Logging Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 4c7ebcb2-eae2-461e-bc83-456ee2d4f694 Query name: Stackdriver Logging Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Kubernetes Engine Clusters must have Stackdriver Logging enabled, which means the attribute 'logging_service' must be defined and different from 'none'<br> ```tf title="Positive test num. 1 - tf file" hl_lines="18 6" resource "googlecontainercluster" "positive1" { name = "marcellus-wallace" location = "us-central1-a" initialnodecount = 3 logging_service = "none" timeouts { create = "30m" update = "40m" } } resource "googlecontainercluster" "positive2" { name = "marcellus-wallace" location = "us-central1-a" initialnodecount = 3 logging_service = "logging.googleapis.com" timeouts { create = "30m" update = "40m" } } ``` ```tf title="Negative test num. 1 - tf file" resource "googlecontainercluster" "negative1" { name = "marcellus-wallace" location = "us-central1-a" initialnodecount = 3 logging_service = "logging.googleapis.com/kubernetes" timeouts { create = "30m" update = "40m" } } resource "googlecontainercluster" "negative1" { name = "marcellus-wallace" location = "us-central1-a" initialnodecount = 3 timeouts { create = "30m" update = "40m" } } ```
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: v1.2.0.md

id: v1.2.0 title: v1.2.0 description: Backstage Release v1.2.0 These are the release notes for the v1.2.0 release of . A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for the hard work in getting this release developed and done. The TechDocs addon framework is now generally available! See the documentation for more information on how to customize your views. The new `@backstage/plugin-adr` lets you track your active ADRs inside Backstage! Contributed by The CodeScene Backstage plugin exposes a page component that will list the existing projects and their analysis data on your CodeScene instance. Contributed by Gerrit integration is here! See docs on and for more information. Contributed by Bitbucket Server and Bitbucket Cloud have been split up internally as the feature sets differ slightly, new scaffolder actions and integrations config has been added to accommodate a gradual migration. Contributed by Server-to-server authentication tokens issued from a TokenManager (specifically, ServerTokenManager) now has an expiry time set, for one hour in the future from when issued. This improves security. The ability to pass in and validate tokens that either have a missing exp claim, or an exp claim that expired in the past, is now deprecated. Trying to do so will lead to logged warnings, and in a future release will instead lead to errors. Added support for `oidc` as an auth provider for kubernetes authentication and added an optional `oidcTokenProvider` config value. This will allow users to authenticate to kubernetes clusters using ID tokens obtained from the configured auth provider in their Backstage instance. Contributed by @dbravovmw(https://github.com/dbravovmw). #11328(https://github.com/backstage/backstage/pull/11328) The `TaskScheduleDefinition` of the backend task scheduler has been updated to also accept an options object containing duration information in the form of days, hours, seconds and so on. This allows for scheduling without importing luxon. Added the ability to render a custom component when an entity is not found `@backstage/plugin-scaffolder-backend-module-rails`, please upgrade to the latest version if you are using this module. We recommend that you keep your Backstage project up to date with this latest release. For more guidance on how to upgrade, check out the documentation for . Below you can find a list of links and references to help you learn about and start using this new release. , , and Backstage's for discussions and support Backstage , , and Sign up for our if you want to be informed about what is happening in the world of Backstage.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 21_io_bigtable.md

Prompt: Is Cloud Bigtable supported in Apache Beam? Response: is a service that provides enterprise-grade NoSQL database service with single-digit millisecond latency, limitless scale, and 99.999% availability for large analytical and operational workloads. Apache Beam has a built-in connector for Cloud Bigtable that lets you read data from and write data to Bigtable. For more information, see the BigtableIO connector documentation: To get started with Cloud Bigtable and Apache Beam, refer to the . Here is an example of Apache Beam pipeline code for reading data from a Bigtable table: ```python with beam.Pipeline(options=options) as p: output = (p | "Read from Bigtable" >> ReadFromBigtable( projectid=projectid, instanceid=instanceid, tableid=tableid, ) | "Extract cells" >> beam.Map(lambda row: row._cells) | "Log Data" >> Map(logging.info)) ``` For performance benchmarks of the Bigtable IO connector, see .
Project: SlimToolkit (Provisioning / Security & Compliance)
File: fuzzy_mode_convert_table.md

| json type \ dest type | bool | int | uint | float |string| | | | | |--|--| | number | positive => true <br/> negative => true <br/> zero => false| 23.2 => 23 <br/> -32.1 => -32| 12.1 => 12 <br/> -12.1 => 0|as normal|same as origin| | string | empty string => false <br/> string "0" => false <br/> other strings => true | "123.32" => 123 <br/> "-123.4" => -123 <br/> "123.23xxxw" => 123 <br/> "abcde12" => 0 <br/> "-32.1" => -32| 13.2 => 13 <br/> -1.1 => 0 |12.1 => 12.1 <br/> -12.3 => -12.3<br/> 12.4xxa => 12.4 <br/> +1.1e2 =>110 |same as origin| | bool | true => true <br/> false => false| true => 1 <br/> false => 0 | true => 1 <br/> false => 0 |true => 1 <br/>false => 0|true => "true" <br/> false => "false"| | object | true | 0 | 0 |0|originnal json| | array | empty array => false <br/> nonempty array => true| [] => 0 <br/> [1,2] => 1 | [] => 0 <br/> [1,2] => 1 |[] => 0<br/>[1,2] => 1|original json|
Project: KICS (Provisioning / Security & Compliance)
File: 905f4741-f965-45c1-98db-f7a00a0e5c73.md

title: SNS Topic is Publicly Accessible hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 905f4741-f965-45c1-98db-f7a00a0e5c73 Query name: SNS Topic is Publicly Accessible Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: SNS Topic Policy should not allow any principal to access<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="50 23" name: Create alarm SNS topic community community.aws.sns_topic: name: "alarms" state: present display_name: "alarm SNS topic" delivery_policy: http: defaultHealthyRetryPolicy: minDelayTarget: 2 maxDelayTarget: 4 numRetries: 3 numMaxDelayRetries: 5 backoffFunction: "<linear|arithmetic|geometric|exponential>" disableSubscriptionOverrides: True defaultThrottlePolicy: maxReceivesPerSecond: 10 subscriptions: endpoint: "myemailaddress@example.com" protocol: "email" endpoint: "mymobilenumber" protocol: "sms" policy: Version: '2022-05-02' Statement: Action: Publish Effect: Allow Principal: "*" name: Create alarm SNS topic sns_topic: name: "alarms" state: present display_name: "alarm SNS topic" delivery_policy: http: defaultHealthyRetryPolicy: minDelayTarget: 2 maxDelayTarget: 4 numRetries: 3 numMaxDelayRetries: 5 backoffFunction: "<linear|arithmetic|geometric|exponential>" disableSubscriptionOverrides: True defaultThrottlePolicy: maxReceivesPerSecond: 10 subscriptions: endpoint: "myemailaddress@example.com" protocol: "email" endpoint: "mymobilenumber" protocol: "sms" policy: Version: '2022-05-02' Statement: Effect: Allow Action: Publish Principal: '*' ``` ```yaml title="Negative test num. 1 - yaml file" name: Create alarm SNS topic community community.aws.sns_topic: name: alarms state: present display_name: alarm SNS topic delivery_policy: http: defaultHealthyRetryPolicy: minDelayTarget: 2 maxDelayTarget: 4 numRetries: 3 numMaxDelayRetries: 5 backoffFunction: <linear|arithmetic|geometric|exponential> disableSubscriptionOverrides: true defaultThrottlePolicy: maxReceivesPerSecond: 10 policy: Version: '2022-05-02' Statement: Effect: Allow Action: Publish Principal: NotAll name: Create alarm SNS topic sns_topic: name: alarms state: present display_name: alarm SNS topic delivery_policy: http: defaultHealthyRetryPolicy: minDelayTarget: 2 maxDelayTarget: 4 numRetries: 3 numMaxDelayRetries: 5 backoffFunction: <linear|arithmetic|geometric|exponential> disableSubscriptionOverrides: true defaultThrottlePolicy: maxReceivesPerSecond: 10 policy: Version: '2022-05-02' Statement: Effect: Allow Action: Publish Principal: NotAll ```