cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 5a627dfa-a4dd-4020-a4c6-5f3caf4abcd6.md

title: Check use no LTS Spark Version hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 5a627dfa-a4dd-4020-a4c6-5f3caf4abcd6 Query name: Check use no LTS Spark Version Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: Spark Version is not a Long-term Support<br> ```tf title="Positive test num. 1 - tf file" hl_lines="8" data "databricksnodetype" "postive1withgpu" { local_disk = true min_cores = 16 gbpercore = 1 min_gpus = 1 } data "databrickssparkversion" "postive1gpuml" { gpu = true ml = true } resource "databrickscluster" "positive1research" { cluster_name = "Research Cluster" sparkversion = data.databrickssparkversion.postive1gpu_ml.id nodetypeid = data.databricksnodetype.postive1withgpu.id autotermination_minutes = 20 autoscale { min_workers = 1 max_workers = 50 } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="11" data "databricksnodetype" "positive2withgpu" { local_disk = true min_cores = 16 gbpercore = 1 min_gpus = 1 } data "databrickssparkversion" "positive2gpuml" { gpu = true ml = true longtermsupport = false } resource "databrickscluster" "positive2research" { cluster_name = "Research Cluster" sparkversion = data.databrickssparkversion.positive2gpu_ml.id nodetypeid = data.databricksnodetype.positive2withgpu.id autotermination_minutes = 20 autoscale { min_workers = 1 max_workers = 50 } } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="10" data "databricksnodetype" "positive3withgpu" { local_disk = true min_cores = 16 gbpercore = 1 min_gpus = 1 } resource "databrickscluster" "positive3research" { cluster_name = "Research Cluster" spark_version = "3.3.1" nodetypeid = data.databricksnodetype.positive2withgpu.id autotermination_minutes = 20 autoscale { min_workers = 1 max_workers = 50 } } ``` ```tf title="Negative test num. 1 - tf file" data "databricksnodetype" "negative1withgpu" { local_disk = true min_cores = 16 gbpercore = 1 min_gpus = 1 } data "databrickssparkversion" "negative1gpuml" { gpu = true ml = true longtermsupport = true } resource "databrickscluster" "negative1research" { cluster_name = "Research Cluster" sparkversion = data.databrickssparkversion.negative1gpu_ml.id nodetypeid = data.databricksnodetype.negative1withgpu.id autotermination_minutes = 20 autoscale { min_workers = 1 max_workers = 50 } } ``` ```tf title="Negative test num. 2 - tf file" data "databricksnodetype" "negative2withgpu" { local_disk = true min_cores = 16 gbpercore = 1 min_gpus = 1 } resource "databrickscluster" "negative2research" { cluster_name = "Research Cluster" spark_version = "3.2.1" nodetypeid = data.databricksnodetype.negative2withgpu.id autotermination_minutes = 20 autoscale { min_workers = 1 max_workers = 50 } } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: scoop.md

layout: default title: Scoop permalink: installation/windows/scoop type: installation category: mesheryctl redirect_from: installation/platforms/scoop display-title: "false" language: en list: include image: /assets/img/platforms/scoop.png abstract: Install Meshery CLI on Windows with Scoop {% include mesheryctl/installation-scoop.md %} Guides to using Meshery's various features and components. {% assign sorted_guides = site.pages | sort: "name" %} <ul> {% for item in sorted_guides %} {% if item.type=="guides" and item.category=="mesheryctl" and item.list!="exclude" and item.language=="en" -%} <li><a href="{{ site.baseurl }}{{ item.url }}">{{ item.title }}</a> </li> {% endif %} {% endfor %} <li><a href="{{ site.baseurl }}/guides/upgrade#upgrading-meshery-cli">Upgrading Meshery CLI</a></li> </ul>
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_project_iam_bindings.md

+++ title = "googleprojectiam_bindings resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleprojectiam_bindings" identifier = "inspec/resources/gcp/googleprojectiambindings.md googleprojectiambindings resource" parent = "inspec/resources/gcp" +++ This resource is deprecated. Please use `google_project_iam_policy` instead Use the `googleprojectiam_bindings` InSpec audit resource to test properties of all, or a filtered group of, GCP project IAM bindings. A `googleprojectiam_bindings` resource block collects GCP project IAM bindings then tests that group. describe googleprojectiam_bindings(project: 'chef-inspec-gcp') do it { should exist } end Use this InSpec resource to enumerate roles then test in-depth using `googleprojectiam_binding`. googleprojectiambindings(project: 'chef-inspec-gcp').iambindingroles.each do |iambinding_role| describe googleprojectiambinding(project: 'chef-inspec-gcp', role: iambinding_role) do it { should exist } its('members') {should include 'user:someuser@domain.com' } end end The following examples show how to use this InSpec audit resource. describe googleprojectiam_bindings(project: 'chef-inspec-gcp') do its('count') { should be <= 100} end describe googleprojectiam_bindings(project: 'chef-inspec-gcp') do its('iambindingroles') { should include "roles/storage.admin" } end describe googleprojectiambindings(project: 'chef-inspec-gcp').where(iambinding_role: "roles/iam.securityReviewer") do it { should_not exist } end This resource supports the following filter criteria: `iambindingrole`. This may be used with `where`, as a block or as a method. `iambindingroles` - an array of googleprojectiam_binding role strings e.g. `["roles/compute.admin", "roles/owner"]` Ensure the is enabled for the project.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.86.md

layout: release date: 2023-04-28 tag: v0.6.86 Add instruction to reinstall Meshery in playground @Revolyssup (#7624) query the userDetails from remoteProvider ```/api/user``` @harkiratsm (#7592) [mesheryctl] docker client init update @Azanul (#7608) Flatten kubeconfig for E2E tests @Revolyssup (#7613) Upgrade minikube version and fix meshconfig in E2E workflow @Revolyssup (#7611) Updated slack and discuss link @DarrenDsouza7273 (#7593) Minor tweak in description of make-link command @Ambareen09 (#7602) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Ambareen09, @Azanul, @DarrenDsouza7273, @MUzairS15, @Revolyssup, @harkiratsm and @leecalcote
Project: KICS (Provisioning / Security & Compliance)
File: release_checklist.md

Check for any `update-queries-docs` pull requests open, review and merge if any Prepare release (run prepare-release action) Use prepare release pull request (`docs: preparing for release`) to bump UBI8 image version label in the and Review and merge prepare-release pull-request Create and push a new version git tag Be sure you configure In the master branch, run `git tag <tagversion>` and `git push -u origin <tagversion>` Test pre-release manually on each platform In , create the release for the target version. Do not forget to select "Create a discussion for this release" and check if it was created. Check if `update-docs-release`, `update-infra-version`, and `release-docker-image` workflow completed with success Check if the image is published in / update hub documentation if changed Push image to Red Hat Update integrations tag: git checkout integrations git checkout -b ${new_branch} git merge ${latest_tag} // update internal/constants/constants.go version to latest git push -u origin HEAD // create PR and merge ${new_branch} with integrations branch !! Warning !! Make sure that branch is being merged with integrations and not master git checkout integrations git tag ${latest_tag}-integrations git push origin ${latest_tag}-integrations
Project: YugabyteDB (App Definition and Development / Database)
File: Bug.md

<!-- IMPORTANT: Please DO NOT publish personal data or confidential information in this issue. Keep in mind that most companies will consider a database model (tables names, columns names and other metadata ) as sensible data. If you want to publish any data in this issue, please add a note stating that you have the right to do so. If secrets were accidentally shared or attached to a support ticket, please notifiy us immediately to ensure this data is redacted and deleted. Conversely, if we suspect that secrets were accidentally submitted to an issue, we will bring this to your attention and take action to remove any sensitive information. Alternatively, if sharing parts ofyour database model is necessary to solve your problem, please consider contracting commercial support and send us an email at <contact@dalibo.com> -->
Project: StarRocks (App Definition and Development / Database)
File: years_sub.md

displayed_sidebar: "English" Subtracts the specified number of years from the specified datetime or date. ```Haskell DATETIME YEARS_SUB(DATETIME date, INT years) ``` `date`: The original date time, of type DATETIME or DATE. `years`: The number of years to subtract. The value can be negative, but date year minus years can't exceed 10000. For example, if the year of date is 2022, then years can't be less than -7979. At the same time, the years cannot exceed the year value of date, for example, if the year value of date is 2022, then years can't be greater than 2022. The return value type is the same as the parameter `date`. Returns NULL if the result year is out of range [0, 9999]. ```Plain Text select years_sub("2022-12-20 15:50:21", 2); +-+ | years_sub('2022-12-20 15:50:21', 2) | +-+ | 2020-12-20 15:50:21 | +-+ ```
Project: ko (App Definition and Development / Application Definition & Image Build)
File: ko_resolve.md

Print the input files with image references resolved to built/pushed image digests. This sub-command finds import path references within the provided files, builds them into Go binaries, containerizes them, publishes them, and prints the resulting yaml. ``` ko resolve -f FILENAME [flags] ``` ``` ko resolve -f config/ ko resolve --preserve-import-paths -f config/ ko resolve --local -f config/ ``` ``` --bare Whether to just use KODOCKERREPO without additional context (may not work properly with --tags). -B, --base-import-paths Whether to use the base path without MD5 hash after KODOCKERREPO (may not work properly with --tags). --disable-optimizations Disable optimizations when building Go code. Useful when you want to interactively debug the created container. -f, --filename strings Filename, directory, or URL to files to use to create the resource -h, --help help for resolve --image-label strings Which labels (key=value) to add to the image. --image-refs string Path to file where a list of the published image references will be written. --insecure-registry Whether to skip TLS verification on the registry -j, --jobs int The maximum number of concurrent builds (default GOMAXPROCS) -L, --local Load into images to local docker daemon. --oci-layout-path string Path to save the OCI image layout of the built images --platform strings Which platform to use when pulling a multi-platform base. Format: all | <os>* -P, --preserve-import-paths Whether to preserve the full import path after KODOCKERREPO. --push Push images to KODOCKERREPO (default true) -R, --recursive Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory. --sbom string The SBOM media type to use (none will disable SBOM synthesis and upload, also supports: spdx, cyclonedx, go.version-m). (default "spdx") --sbom-dir string Path to file where the SBOM will be written. -l, --selector string Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2) --tag-only Include tags but not digests in resolved image references. Useful when digests are not preserved when images are repopulated. -t, --tags strings Which tags to use for the produced image instead of the default 'latest' tag (may not work properly with --base-import-paths or --bare). (default [latest]) --tarball string File to save images tarballs ``` ``` -v, --verbose Enable debug logs ``` - Rapidly iterate with Go, Containers, and Kubernetes.
Project: KICS (Provisioning / Security & Compliance)
File: 4ae8af91-5108-42cb-9471-3bdbe596eac9.md

title: S3 Bucket With All Permissions hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 4ae8af91-5108-42cb-9471-3bdbe596eac9 Query name: S3 Bucket With All Permissions Platform: CloudFormation Severity: <span style="color:#ff0000">Critical</span> Category: Access Control URL: S3 Buckets should not have all permissions, as to prevent leaking private information to the entire internet or allow unauthorized data tampering / deletion. This means the 'Effect' must not be 'Allow' when the 'Action' is '*', for all Principals.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" Resources: SampleBucketPolicy3: Type: 'AWS::S3::BucketPolicy' Properties: Bucket: !Ref DOC-EXAMPLE-BUCKET PolicyDocument: Statement: Action: "*" Effect: Allow Resource: "*" Principal: "*" Condition: StringLike: 'aws:Referer': 'http://www.example.com/*' 'http://example.net/*' ``` ```json title="Positive test num. 2 - json file" hl_lines="9" { "Resources": { "SampleBucketPolicy4": { "Type": "AWS::S3::BucketPolicy", "Properties": { "Bucket": { "Ref": "DOC-EXAMPLE-BUCKET" }, "PolicyDocument": { "Statement": [ { "Action": "*", "Effect": "Allow", "Resource": "*", "Principal": "*", "Condition": { "StringLike": { "aws:Referer": [ "http://www.example.com/*", "http://example.net/*" ] } } } ] } } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: SampleBucketPolicy1: Type: 'AWS::S3::BucketPolicy' Properties: Bucket: !Ref DOC-EXAMPLE-BUCKET PolicyDocument: Statement: Action: 's3:GetObject' Effect: Deny Resource: '*' Principal: '*' Condition: StringLike: 'aws:Referer': 'http://www.example.com/*' 'http://example.net/*' ``` ```json title="Negative test num. 2 - json file" { "Resources": { "SampleBucketPolicy2": { "Type": "AWS::S3::BucketPolicy", "Properties": { "Bucket": { "Ref": "DOC-EXAMPLE-BUCKET" }, "PolicyDocument": { "Statement": [ { "Action": [ "s3:GetObject" ], "Effect": "Deny", "Resource": "*", "Principal": "*", "Condition": { "StringLike": { "aws:Referer": [ "http://www.example.com/*", "http://example.net/*" ] } } } ] } } } } } ```
Project: Distribution (Provisioning / Container Registry)
File: help.md

description: Getting help with the Registry keywords: registry, on-prem, images, tags, repository, distribution, help, 101, TL;DR title: Get help If you need help, or just want to chat about development, you can reach us on the #distribution channel in the CNCF Slack. If you want to report a bug: be sure to first read about . you can then do so on the .
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.14.1.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Certain Pipes tasks fail, after exiting the C++ application | Blocker | . | Srikanth Kakani | Devaraj Das | | | hadoop seems not to support multi-homed installations | Blocker | . | Torsten Curdt | Doug Cutting | | | The counts of currently running maps and reduces isn't maintained correctly when task trackers fail | Major | . | Owen O'Malley | Owen O'Malley |
Project: YugabyteDB (App Definition and Development / Database)
File: create_operator_class,operator_class_as.grammar.md

```output.ebnf createoperatorclass ::= CREATE OPERATOR CLASS operatorclassname [ DEFAULT ] FOR TYPE data_type USING indexmethod AS operatorclass_as [ , ... ] operatorclassas ::= OPERATOR strategynumber operatorname [ ( operator_signature ) ] [ FOR SEARCH ] | FUNCTION support_number [ ( optype [ , ... ] ) ] subprogramname ( subprogram_signature ) | STORAGE storage_type ```
Project: KusionStack (Provisioning / Automation & Configuration)
File: kusion_version.md

Print the Kusion version information for the current context Print the Kusion version information for the current context ``` kusion version [flags] ``` ``` kusion version ``` ``` -h, --help help for version -o, --output string Output format. Only json format is supported for now ``` ``` --profile string Name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex) (default "none") --profile-output string Name of the file to write the profile to (default "profile.pprof") ``` - Kusion is the Platform Orchestrator of Internal Developer Platform
Project: Terrascan (Provisioning / Security & Compliance)
File: CONTRIBUTING.md

--8<-- "CONTRIBUTING.md" ions are welcome, and they are greatly appreciated! You can contribute in many ways: Report bugs at . If you are reporting a bug, please include: Your operating system name and version. Any details about your local setup that might be helpful in troubleshooting. Detailed steps to reproduce the bug. Look through the GitHub issues for bugs. Anything tagged with "bug" and "help wanted" is open to whoever wants to implement it. Look through the GitHub issues for features. Anything tagged with "enhancement" and "help wanted" is open to whoever wants to implement it. Terrascan could always use more documentation, whether as part of the official Terrascan docs, or even on the web in blog posts, articles, videos, and such. Documentation for Terrascan is located in and accessible through . Any PRs with changes in functionality or the CLIs user interface should include a corresponding PR for documentation updates. The best way to send feedback is to file an issue at . If you are proposing a feature: Explain in detail how it would work. Keep the scope as narrow as possible, to make it easier to implement. Remember that this is a volunteer-driven project, and that contributions are welcome :) Ready to contribute? Here's how to set up `terrascan` for local development. Fork the `terrascan` repo on GitHub. Clone your fork locally: ``` $ git clone git@github.com:yournamehere/terrascan.git ``` Create a branch for local development: ``` $ git checkout -b name-of-your-bugfix-or-feature ``` Now you can make your changes locally. When you're done making changes, check that your changes pass linting and tests. The following commands will simulate locally all checks executed as part of Terrascan's CI pipeline: ``` $ make cicd ``` Commit your changes and push your branch to GitHub:: ``` $ git add . $ git commit -m "Your detailed description of your changes." $ git push origin name-of-your-bugfix-or-feature ``` Submit a pull request through the GitHub website. Before you submit a pull request, check that it meets these guidelines: The pull request should include tests. If the pull request adds functionality or policies, the docs should be updated. Make sure all tests pass by running `make cicd`.
Project: StarRocks (App Definition and Development / Database)
File: prepare_deployment_files.md

displayed_sidebar: "English" This topic describes how to prepare StarRocks deployment files. Currently, the binary distribution packages StarRocks provides on support deployments only on x86-based CentOS 7.9. If you want to deploy StarRocks with the ARM architecture CPUs or on Ubuntu 22.04, you need to prepare the deployment files using the StarRocks Docker image. StarRocks binary distribution packages are named in the StarRocks-version.tar.gz format, where version is a number (for example, 2.5.2) that indicates the version information of the binary distribution package. Make sure that you have chosen the correct version of the package. Follow these steps to prepare deployment files for the x86-based CentOS 7.9 platform: Obtain the StarRocks binary distribution package directly from the page or by running the following command in your terminal: ```Bash wget https://releases.starrocks.io/starrocks/StarRocks-<version>.tar.gz ``` Extract the files in the package. ```Bash tar -xzvf StarRocks-<version>.tar.gz ``` The package includes the following directories and files: | Directory/File | Description | | - | -- | | apache_hdfs_broker | The deployment directory of the Broker node. | | fe | The FE deployment directory. | | be | The BE deployment directory. | | LICENSE.txt | The StarRocks license file. | | NOTICE.txt | The StarRocks notice file. | Dispatch the directory fe to all the FE instances and the directory be to all the BE or CN instances for . You must have (17.06.0 or later) installed on your machine. Download a StarRocks Docker image from . You can choose a specific version based on the tag of the image. If you use Ubuntu 22.04: ```Bash docker pull starrocks/artifacts-ubuntu:<image_tag> ``` If you use ARM-based CentOS 7.9: ```Bash docker pull starrocks/artifacts-centos7:<image_tag> ``` Copy the StarRocks deployment files from the Docker image to your host machine by running the following command: If you use Ubuntu 22.04: ```Bash docker run --rm starrocks/artifacts-ubuntu:<image_tag> \ tar -cf - -C /release . | tar -xvf - ``` If you use ARM-based CentOS 7.9: ```Bash docker run --rm starrocks/artifacts-centos7:<image_tag> \ tar -cf - -C /release . | tar -xvf - ``` The deployment files include the following directories: | Directory | Description | | -- | | | be_artifacts | This directory includes the BE or CN deployment directory be, StarRocks license file LICENSE.txt, and StarRocks notice file NOTICE.txt. | | broker_artifacts | This directory includes the Broker deployment directory apache_hdfs_broker. | | fe_artifacts | This directory includes the FE deployment directory fe, StarRocks license file LICENSE.txt, and StarRocks notice file NOTICE.txt. | Dispatch the directory fe to all the FE instances and the directory be to all the BE or CN instances for .
Project: ArangoDB (App Definition and Development / Database)
File: nodiscard.md

+++ title = "`BOOSTOUTCOMENODISCARD`" description = "How to tell the compiler than the return value of a function should not be discarded without examining it." +++ Compiler-specific markup used to tell the compiler than the return value of a function should not be discarded without examining it. Overridable: Define before inclusion. Default: To `[[nodiscard]]` if on C++ 17 or higher, `attribute((warnunusedresult))` if on clang, SAL `Mustinspectresult` if on MSVC, otherwise nothing. Header: `<boost/outcome/config.hpp>`
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_security_policies.md

+++ title = "googlecomputesecurity_policies resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputesecurity_policies" identifier = "inspec/resources/gcp/googlecomputesecuritypolicies.md googlecomputesecuritypolicies resource" parent = "inspec/resources/gcp" +++ A `googlecomputesecurity_policies` is used to test a Google SecurityPolicy resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputesecurity_policies(project: 'chef-gcp-inspec') do its('count') { should be >= 1 } its('names') { should include 'sec-policy' } end ``` Properties that can be accessed from the `googlecomputesecurity_policies` resource: See the resource for more information. `names` : an array of `googlecomputesecurity_policy` name `ids` : an array of `googlecomputesecurity_policy` id `rules` : an array of `googlecomputesecurity_policy` rules 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.