cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: b0749c53-e3ff-4d09-bbe4-dca94e2e7a38.md

title: Check Databricks Cluster AWS Attribute Best Practices hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b0749c53-e3ff-4d09-bbe4-dca94e2e7a38 Query name: Check Databricks Cluster AWS Attribute Best Practices Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: One or some Databricks Cluster AWS Attribute Best Practices are not respected<br> ```tf title="Positive test num. 1 - tf file" hl_lines="11" resource "databricks_cluster" "positive1" { cluster_name = "data" sparkversion = data.databricksspark_version.latest.id nodetypeid = data.databricksnodetype.smallest.id autotermination_minutes = 20 autoscale { min_workers = 1 max_workers = 50 } aws_attributes { availability = "SPOT" zone_id = "auto" firstondemand = 1 spotbidprice_percent = 100 } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="13" resource "databricks_cluster" "positive2" { cluster_name = "data" sparkversion = data.databricksspark_version.latest.id nodetypeid = data.databricksnodetype.smallest.id autotermination_minutes = 20 autoscale { min_workers = 1 max_workers = 50 } aws_attributes { availability = "SPOTWITHFALLBACK" zone_id = "auto" firstondemand = 0 spotbidprice_percent = 100 } } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="10" resource "databricks_cluster" "positive3" { cluster_name = "data" sparkversion = data.databricksspark_version.latest.id nodetypeid = data.databricksnodetype.smallest.id autotermination_minutes = 20 autoscale { min_workers = 1 max_workers = 50 } aws_attributes { availability = "SPOTWITHFALLBACK" zone_id = "auto" spotbidprice_percent = 100 } } ``` <details><summary>Positive test num. 4 - tf file</summary> ```tf hl_lines="12" resource "databricks_cluster" "positive4" { cluster_name = "data" sparkversion = data.databricksspark_version.latest.id nodetypeid = data.databricksnodetype.smallest.id autotermination_minutes = 20 autoscale { min_workers = 1 max_workers = 50 } aws_attributes { availability = "SPOTWITHFALLBACK" zone_id = "us-west-2a" firstondemand = 1 spotbidprice_percent = 100 } } ``` </details> ```tf title="Negative test num. 1 - tf file" resource "databricks_cluster" "negative" { cluster_name = "Shared Autoscaling" sparkversion = data.databricksspark_version.latest.id nodetypeid = data.databricksnodetype.smallest.id autotermination_minutes = 20 autoscale { min_workers = 1 max_workers = 50 } aws_attributes { availability = "SPOTWITHFALLBACK" zone_id = "auto" firstondemand = 1 spotbidprice_percent = 100 } } ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: directory.md

+++ title = "directory resource" draft = false gh_repo = "inspec" platform = "os" [menu] [menu.inspec] title = "directory" identifier = "inspec/resources/os/directory.md directory resource" parent = "inspec/resources/os" +++ Use the `directory` Chef InSpec audit resource to test if the file type is a directory. This is equivalent to using the and the `be_directory` matcher, but provides a simpler and more direct way to test directories. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `directory` resource block declares the location of the directory to be tested, and then one (or more) matchers. describe directory('path') do its('property') { should cmp 'value' } end All of the properties available to may be used with `directory`. {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: YugabyteDB (App Definition and Development / Database)
File: installer.md

title: Prerequisites - YBA Installer headerTitle: Prerequisites for YBA linkTitle: YBA prerequisites description: Prerequisites for installing YugabyteDB Anywhere using YBA Installer headContent: What you need to install YugabyteDB Anywhere menu: v2.18_yugabyte-platform: identifier: prerequisites-installer parent: install-yugabyte-platform weight: 20 type: docs You can install YugabyteDB Anywhere (YBA) using the following methods: | Method | Using | Use If | | : | : | : | | YBA Installer | yba-ctl CLI | You are performing a new installation. | | Replicated | Docker containers | Your installation already uses Replicated. | | Kubernetes | Helm chart | You're deploying in Kubernetes. | All installation methods support installing YBA with and without (airgapped) Internet connectivity. Licensing (such as a license file in the case of Replicated, or appropriate repository access in the case of Kubernetes) may be required prior to installation. Contact {{% support-platform %}} for assistance. <ul class="nav nav-tabs-alt nav-tabs-yb"> <li> <a href="../installer/" class="nav-link active"> <i class="fa-solid fa-building" aria-hidden="true"></i>YBA Installer</a> </li> <li> <a href="../default/" class="nav-link"> <i class="fa-solid fa-cloud"></i>Replicated</a> </li> <li> <a href="../kubernetes/" class="nav-link"> <i class="fa-regular fa-dharmachakra" aria-hidden="true"></i>Kubernetes</a> </li> </ul> You can install YugabyteDB Anywhere using YBA Installer on the following Linux distributions: CentOS 7 AlmaLinux 8 AlmaLinux 9 Ubuntu 18 Ubuntu 20 RedHat Enterprise Linux 7 RedHat Enterprise Linux 8 YugabyteDB Anywhere may also work on other Linux distributions; contact your YugabyteDB support representative if you need added support. Python v3.8 to 3.11 must be installed, and both `python` and `python3` must point to Python 3. One way to achieve this is to use `alternatives`. For example: ```sh sudo yum install @python38 -y sudo alternatives --config python sudo alternatives --config python3 python -V python3 -V ``` A node running YugabyteDB Anywhere is expected to meet the following requirements: 4 cores 8 GB memory 215 GB disk space Ensure that the following ports are available: 443 (HTTPS) 5432 (PostgreSQL) 9090 (Prometheus) These are configurable. If custom ports are used, those must be available instead. For more information on ports used by YugabyteDB, refer to .
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: API-005-state-store-behavior.md

Proposed As we continue to solidify our API spec, we need to explicitly define component behaviors in the spec and make sure those are implemented in our implementation. This document captures our decisions on state store behaviors. It's expected that we'll create more of such documents to capture explicit component behavior decisions. Dapr supports two flavors of optimistic concurrency: first-write wins and last-write wins. First-write wins is implemented through ETag. User code can express concurrency intention with a config annotation attached to a request. See Config annotation* for details. Future version of Dapr may support call throttling through application channel. We'll choose last-write wins as the default. Dapr supports both eventual consistency and strong consistency. Actors always use strong consistency. We'll choose eventual consistency as default for services other than actors. Dapr-compatible Actor state stores shall support ACID transaction. Dapr doesn't mandate specific transaction isolation level at this point. However, when deemed necessary, we can easily add those to Config annotation* as needed. User payload can contain an optional config* annotation/element that expresses various constraints and policies to be applied to the call, including: Concurrency model: first-write or last-write Consistency model: strong or eventual Retry policies: Interval Pattern: linear, expotential Circuit-breaker Timeout (before an open circuit-breaker is reset) An Dapr-compatible state store shall provide an endpoint that answers to configuration probe and returns (among others): Supported concurrency model Supported consistency model A state store instance shall return the specific configuration of the current instance. It's considered out of scope to require state store to dynamically apply new configurations. Update state store API spec to reflect above decisions Create backlog of issues to implement above decisions
Project: NeuVector (Provisioning / Security & Compliance)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at doug@dougamartin.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: harborregistry.md

HarborRegistry requires a configuration file to start, which is located at `/etc/registry/config.yml` within the container. Any changes made to this config file are temporary and will not persist once the pod is restarted. This config file is stored within the `services/harborregistry/harborregistry.yml` file and loaded into the container as `/etc/registry/pre-config.yml`. A custom container entrypoint, `services/harborregistry/entrypoint.sh`, then transposes provided environment variables into this config file and saves the results as `/etc/registry/config.yml`. `CORE_SECRET`* This value is a pre-shared key that must match between the various services connecting to `harbor-core`. The default value is set to `secret123` when Harbor is run locally or during CI testing. This value is retrieved from a secret created when Harbor is first set up on a running Lagoon. `HARBOR_NGINX_ENDPOINT`* This environment variable tells `harborregistry` where its NGINX ingress controller, `harbor-nginx`, is running in order to construct proper push and pull instructions in the UI, among other things. The default value is set to `http://harbor-nginx:8080` when run locally or during CI testing. Lagoon attempts to obtain and set this variable automagically when run in production. If that process fails, this service will fail to run. `JOBSERVICE_SECRET`* This value is a pre-shared key that must match between the various services connecting to `harbor-jobservice`. The default value is set to `secret123` when Harbor is run locally or during CI testing. This value is retrieved from a secret created when Harbor is first set up on a running Lagoon. `REGISTRY_HTTP_SECRET`* This value is a pre-shared key that must match between the various services connecting to `harborregistry`. The default value is set to `secret123` when Harbor is run locally or during CI testing. This value is retrieved from a secret created when Harbor is first set up on a running Lagoon. `REGISTRY_REDIS_PASSWORD`* This environment variable tells `harborregistryctl` the password that should be used to connect to Redis. The default value is an empty string.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-aux-show-tblproperties.md

layout: global title: SHOW TBLPROPERTIES displayTitle: SHOW TBLPROPERTIES 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. This statement returns the value of a table property given an optional value for a property key. If no key is specified then all the properties are returned. ```sql SHOW TBLPROPERTIES table_identifier [ ( unquotedpropertykey | propertykeyasstringliteral ) ] ``` table_identifier* Specifies the table name of an existing table. The table may be optionally qualified with a database name. Syntax: `[ databasename. ] tablename` unquoted_property_key* Specifies the property key in unquoted form. The key may consists of multiple parts separated by dot. Syntax: `[ keypart1 ] [ .keypart2 ] [ ... ]` property_key_as_string_literal* Specifies a property key value as a string literal. Note Property value returned by this statement excludes some properties that are internal to spark and hive. The excluded properties are : All the properties that start with prefix `spark.sql` Property keys such as: `EXTERNAL`, `comment` All the properties generated internally by hive to store statistics. Some of these properties are: `numFiles`, `numPartitions`, `numRows`. ```sql -- create a table `customer` in database `salesdb` USE salesdb; CREATE TABLE customer(custcode INT, name VARCHAR(100), custaddr STRING) TBLPROPERTIES ('created.by.user' = 'John', 'created.date' = '01-01-2001'); -- show all the user specified properties for table `customer` SHOW TBLPROPERTIES customer; ++-+ | key| value| ++-+ | created.by.user| John| | created.date|01-01-2001| |transient_lastDdlTime|1567554931| ++-+ -- show all the user specified properties for a qualified table `customer` -- in database `salesdb` SHOW TBLPROPERTIES salesdb.customer; ++-+ | key| value| ++-+ | created.by.user| John| | created.date|01-01-2001| |transient_lastDdlTime|1567554931| ++-+ -- show value for unquoted property key `created.by.user` SHOW TBLPROPERTIES customer (created.by.user); +--+ |value| +--+ | John| +--+ -- show value for property `created.date`` specified as string literal SHOW TBLPROPERTIES customer ('created.date'); +-+ | value| +-+ |01-01-2001| +-+ ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_global_addresses.md

+++ title = "googlecomputeglobal_addresses resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputeglobal_addresses" identifier = "inspec/resources/gcp/googlecomputeglobaladdresses.md googlecomputeglobaladdresses resource" parent = "inspec/resources/gcp" +++ A `googlecomputeglobal_addresses` is used to test a Google GlobalAddress resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputeglobal_addresses(project: 'chef-gcp-inspec', name: 'inspec-gcp-global-address') do its('count') { should be >= 1 } its('names') { should include 'inspec-gcp-global-address' } its('ip_versions') { should include 'IPV6' } end ``` Properties that can be accessed from the `googlecomputeglobal_addresses` resource: See the resource for more information. `addresses` : an array of `googlecomputeglobal_address` address `creation_timestamps` : an array of `googlecomputeglobaladdress` creationtimestamp `descriptions` : an array of `googlecomputeglobal_address` description `ids` : an array of `googlecomputeglobal_address` id `names` : an array of `googlecomputeglobal_address` name `labels` : (Beta only) an array of `googlecomputeglobal_address` labels `label_fingerprints` : (Beta only) an array of `googlecomputeglobaladdress` labelfingerprint `ip_versions` : an array of `googlecomputeglobaladdress` ipversion `regions` : an array of `googlecomputeglobal_address` region `prefix_lengths` : an array of `googlecomputeglobaladdress` prefixlength `address_types` : an array of `googlecomputeglobaladdress` addresstype `purposes` : an array of `googlecomputeglobal_address` purpose `networks` : an array of `googlecomputeglobal_address` network This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: YugabyteDB (App Definition and Development / Database)
File: savepoint_create.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="183" height="35" viewbox="0 0 183 35"><path class="connector" d="M0 22h15m89 0h10m54 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="89" height="25" rx="7"/><text class="text" x="25" y="22">SAVEPOINT</text><a xlink:href="../../../syntaxresources/grammardiagrams#name"><rect class="rule" x="114" y="5" width="54" height="25"/><text class="text" x="124" y="22">name</text></a><polygon points="179,29 183,29 183,15 179,15" style="fill:black;stroke-width:0"/></svg>
Project: YDB (App Definition and Development / Database)
File: options_static.md

`--user <username>` : The username and password based authentication mode is used with the username set in this option value. Additionally , you can specify: `--password-file <filename>` : The password is read from the specified file. `--no-password` : Defines an empty password. The password will be requested interactively if none of the password identification options listed above are specified in the command line parameters.
Project: Trivy (Provisioning / Security & Compliance)
File: wolfi.md

Trivy supports these scanners for OS packages. | Scanner | Supported | | :--: | :-: | | SBOM | | | Vulnerability | | | License | | The table below outlines the features offered by Trivy. | Feature | Supported | |::|::| | Detect unfixed vulnerabilities | - | | | | Same as . Wolfi Linux offers its own security advisories, and these are utilized when scanning Wolfi for vulnerabilities. Everything else is the same as . See . Same as .
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-pattern.md

layout: default title: mesheryctl-pattern permalink: reference/mesheryctl/pattern redirect_from: reference/mesheryctl/pattern/ type: reference display-title: "false" language: en command: pattern subcommand: nil Cloud Native Patterns Management Manage cloud and cloud native infrastructure using predefined patterns. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl pattern [flags] </div> </pre> Apply pattern file: <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl pattern apply --file [path to pattern file | URL of the file] </div> </pre> Delete pattern file: <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl pattern delete --file [path to pattern file] </div> </pre> View pattern file: <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl pattern view [pattern name | ID] </div> </pre> List all patterns: <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl pattern list </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for pattern -t, --token string Path to token file default from current context </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -v, --verbose verbose output </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk.md

title: "operator-sdk" CLI tool for building Kubernetes extensions and tools. ``` operator-sdk [flags] ``` ``` The first step is to initialize your project: operator-sdk init [--plugins=<PLUGIN KEYS> [--project-version=<PROJECT VERSION>]] <PLUGIN KEYS> is a comma-separated list of plugin keys from the following table and <PROJECT VERSION> a supported project version for these plugins. Plugin keys | Supported project versions --+- ansible.sdk.operatorframework.io/v1 | 3 declarative.go.kubebuilder.io/v1 | 2, 3 deploy-image.go.kubebuilder.io/v1-alpha | 3 go.kubebuilder.io/v2 | 2, 3 go.kubebuilder.io/v3 | 3 go.kubebuilder.io/v4 | 3 grafana.kubebuilder.io/v1-alpha | 3 helm.sdk.operatorframework.io/v1 | 3 hybrid.helm.sdk.operatorframework.io/v1-alpha | 3 quarkus.javaoperatorsdk.io/v1-beta | 3 For more specific help for the init command of a certain plugins and project version configuration please run: operator-sdk init --help --plugins=<PLUGIN KEYS> [--project-version=<PROJECT VERSION>] Default plugin keys: "go.kubebuilder.io/v4" Default project version: "3" ``` ``` -h, --help help for operator-sdk --plugins strings plugin keys to be used for this subcommand execution --project-version string project version (default "3") --verbose Enable verbose logging ``` - Alpha-stage subcommands - Manage operator bundle metadata - Clean up an Operator deployed with the 'run' subcommand - Load completions for the specified shell - Scaffold a Kubernetes API or webhook - Update the project configuration - Invokes a specific generator - Initialize a new project - Manage the Operator Lifecycle Manager installation in your cluster - Migrates packagemanifests to bundles - Run an Operator in a variety of environments - Runs scorecard - Print the operator-sdk version