cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 70919c0b-2548-4e6b-8d7a-3d84ab6dabba.md

title: OSS Bucket Versioning Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 70919c0b-2548-4e6b-8d7a-3d84ab6dabba Query name: OSS Bucket Versioning Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Backup URL: OSS Bucket should have versioning enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="6" resource "alicloudossbucket" "bucket-versioning2" { bucket = "bucket-170309-versioning" acl = "private" versioning { status = "Suspended" } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "alicloudossbucket" "bucket-versioning3" { bucket = "bucket-170309-versioning" acl = "private" } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudossbucket" "bucket-versioning1" { bucket = "bucket-170309-versioning" acl = "private" versioning { status = "Enabled" } } ```
Project: Confidential Containers (Provisioning / Security & Compliance)
File: cncf-onboarding.md

name: CNCF onboarding about: CNCF onboarding issue tracker title: "[CNCF]" labels: cncf-onboarding assignees: '' This is the list of all bullet points from the that this issue will track: [ ] Bullet point foo* [ ] Bullet point bar*
Project: Datree (Provisioning / Security & Compliance)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: bug assignees: '' Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Run command '...' Click on '....' See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Desktop (please complete the following information): OS: [e.g. Linux] Datree version (run `datree version`): Version: [e.g. 0.1.443] Client ID (`cat ~/.datree/config.yaml`): client_id: [e.g. C5fiX5Tm4SvxwkcfXVSHu5] Additional context Add any other context about the problem here. If possible, include a YAML file to reproduce the bug.
Project: Vitess (App Definition and Development / Database)
File: versioning.md

Our versioning strategy is based on . A new major release is needed when the public API changes in a backward-incompatible way -- for example, when removing deprecated interfaces. Our public API includes (but is not limited to): The VTGate . The interfaces exposed by the VTGate client library in each language. Care must also be taken when changing the format of any data stored by a live system, such as topology data or Vitess-internal tables (used for sequences, distributed transactions, etc.). Although this data is considered as internal to Vitess, if any change breaks the upgrade path for a live system (for example, requiring that it be shut down and reinitialized from scratch), then it must be considered as a breaking change. A new minor release indicates that functionality has been added or changed in a backward-compatible way. This should be the majority of normal releases. A patch release indicates that only a select set of bugfixes have been cherry-picked onto the associated minor release. The expectation is that upgrading by a patch release should be painless (not requiring any config changes) and safe (isolated from active development on `main`). Pre-release versions should be labeled with a suffix like `-beta2` or `-rc1`.
Project: KICS (Provisioning / Security & Compliance)
File: 68b6a789-82f8-4cfd-85de-e95332fe6a61.md

title: MQ Broker 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: 68b6a789-82f8-4cfd-85de-e95332fe6a61 Query name: MQ Broker Is Publicly Accessible Platform: CloudFormation Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: Check if any MQ Broker is not publicly accessible<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="15" AWSTemplateFormatVersion: "2010-09-09" Description: "Create a basic ActiveMQ broker" Resources: BasicBroker: Type: "AWS::AmazonMQ::Broker" Properties: AutoMinorVersionUpgrade: "false" BrokerName: MyBasicBroker DeploymentMode: SINGLE_INSTANCE EncryptionOptions: UseAwsOwnedKey: true EngineType: ActiveMQ EngineVersion: "5.15.0" HostInstanceType: mq.t2.micro PubliclyAccessible: true Users: ConsoleAccess: "true" Groups: MyGroup Password: Ref: "BrokerPassword" Username: Ref: "BrokerUsername" ``` ```json title="Positive test num. 2 - json file" hl_lines="31" { "AWSTemplateFormatVersion": "2010-09-09", "Description": "Create a basic ActiveMQ broker", "Resources": { "BasicBroker2": { "Type": "AWS::AmazonMQ::Broker", "Properties": { "BrokerName": "MyBasicBroker", "DeploymentMode": "SINGLE_INSTANCE", "EncryptionOptions": { "UseAwsOwnedKey": true }, "EngineType": "ActiveMQ", "EngineVersion": "5.15.0", "HostInstanceType": "mq.t2.micro", "Users": [ { "ConsoleAccess": "true", "Groups": [ "MyGroup" ], "Password": { "Ref": "BrokerPassword" }, "Username": { "Ref": "BrokerUsername" } } ], "AutoMinorVersionUpgrade": "false", "PubliclyAccessible": true } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: "2010-09-09" Description: "Create a basic ActiveMQ broker" Resources: BasicBroker: Type: "AWS::AmazonMQ::Broker" Properties: AutoMinorVersionUpgrade: "false" BrokerName: MyBasicBroker DeploymentMode: SINGLE_INSTANCE EncryptionOptions: UseAwsOwnedKey: true EngineType: ActiveMQ EngineVersion: "5.15.0" HostInstanceType: mq.t2.micro PubliclyAccessible: false Users: ConsoleAccess: "true" Groups: MyGroup Password: Ref: "BrokerPassword" Username: Ref: "BrokerUsername" ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Description": "Create a basic ActiveMQ broker", "Resources": { "BasicBroker2": { "Type": "AWS::AmazonMQ::Broker", "Properties": { "BrokerName": "MyBasicBroker", "DeploymentMode": "SINGLE_INSTANCE", "EncryptionOptions": { "UseAwsOwnedKey": true }, "EngineType": "ActiveMQ", "EngineVersion": "5.15.0", "HostInstanceType": "mq.t2.micro", "Users": [ { "ConsoleAccess": "true", "Groups": [ "MyGroup" ], "Password": { "Ref": "BrokerPassword" }, "Username": { "Ref": "BrokerUsername" } } ], "AutoMinorVersionUpgrade": "false" } } } } ```
Project: Curiefense (Provisioning / Security & Compliance)
File: CONTRIBUTING.md

Hey there fellow open source contributor! Please read the following guidelines below carefully to maximize the chances of your PR being merged. Before starting work on a major feature*, please reach out to us via or . We will make sure no one else is already working on it. Small patches and bug fixes don't need prior communication. One important fact of curiefense is that you don't have to be "a maintainer" to be able to contribute with reviews, triaging, or any other maintenance task. The curiefense community welcomes everyone willing to help with reviews, testing open PRs, and providing feedback of any sort. Please, do join the rest of the team in triaging issues, reviewing PRs, and providing any feedback that would help making the community stronger, and processes easier for everyone. Here you can find some guidelines about Curiefense's triaging process. We will present them in the form of bullet points for the sake of simplicity. All the points presented here are equally important: All issues should either belong to a milestone or be labeled as backlog. Issues without one of these attributes will be considered untriaged. The `backlog` label and the milestone attribute are mutually exclusive. Issues labeled as `backlog` will be reviewed at the beginning of the development cycle (after every release) or during a backlog review meeting. Every issue that is actively being worked on should have, at most, one assignee. Conversely, there should not be anyone assigned to an issue that is not being worked on. Curiefense follows a very simple process that is referred to as the [GitHub Flow](https://guides.github.com/introduction/flow/). The goal for this flow is to provide the least amount of steps and friction to contribute to curiefense. Here is the flow described in bullet points: Fork the repo Create a branch Create your PR At this point, you will see the following happening on your PR: Tests will automatically run for you. Reviewers will be assigned to the PR either automatically or by one of the curiefense maintainers. In order to make interaction simpler, save some time, and don't waste precious CPU cycles, it is important that the following things are checked before reviewers start looking at the PRs: PRs are expected to have 100% test coverage for added code. This can be verified with a coverage build. If your PR cannot have 100% coverage for some reason please clearly explain why when you open it. Your PR title should be descriptive, Examples: `Bump axios from 0.19.2 to 0.21.1 in /curiefense/ui` `Add run-curieconf-client-tests.yml` `Update getting started documentation` ProTip: check out "" Your PR commit message will be used as the commit message when your PR is merged. You should update this field if your PR diverges during review. When all of the tests are passing and all other conditions described herein are satisfied, [a maintainer](https://github.com/curiefense/curiefense/graphs/contributors) will be assigned to review and merge the PR. <br> Adapted from
Project: KubeClarity (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 make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, 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 within all project spaces, and it also applies when an individual is representing the project or its community in public spaces. 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 . All complaints will be reviewed and investigated and will result in a response that is deemed necessary and 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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq
Project: YugabyteDB (App Definition and Development / Database)
File: drop_operator_class.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="875" height="70" viewbox="0 0 875 70"><path class="connector" d="M0 22h15m53 0h10m84 0h10m59 0h30m32 0h10m64 0h20m-141 0q5 0 5 5v8q0 5 5 5h116q5 0 5-5v-8q0-5 5-5m5 0h10m148 0h10m60 0h10m106 0h30m77 0h22m-109 25q0 5 5 5h5m79 0h5q5 0 5-5m-104-25q5 0 5 5v33q0 5 5 5h89q5 0 5-5v-33q0-5 5-5m5 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="53" height="25" rx="7"/><text class="text" x="25" y="22">DROP</text><rect class="literal" x="78" y="5" width="84" height="25" rx="7"/><text class="text" x="88" y="22">OPERATOR</text><rect class="literal" x="172" y="5" width="59" height="25" rx="7"/><text class="text" x="182" y="22">CLASS</text><rect class="literal" x="261" y="5" width="32" height="25" rx="7"/><text class="text" x="271" y="22">IF</text><rect class="literal" x="303" y="5" width="64" height="25" rx="7"/><text class="text" x="313" y="22">EXISTS</text><a xlink:href="../../../syntaxresources/grammardiagrams#operator-class-name"><rect class="rule" x="397" y="5" width="148" height="25"/><text class="text" x="407" y="22">operatorclassname</text></a><rect class="literal" x="555" y="5" width="60" height="25" rx="7"/><text class="text" x="565" y="22">USING</text><a xlink:href="../../../syntaxresources/grammardiagrams#index-method"><rect class="rule" x="625" y="5" width="106" height="25"/><text class="text" x="635" y="22">index_method</text></a><rect class="literal" x="761" y="5" width="77" height="25" rx="7"/><text class="text" x="771" y="22">CASCADE</text><rect class="literal" x="761" y="35" width="79" height="25" rx="7"/><text class="text" x="771" y="52">RESTRICT</text><polygon points="871,29 875,29 875,15 871,15" style="fill:black;stroke-width:0"/></svg>
Project: Apache CarbonData (App Definition and Development / Database)
File: How-to-build-carbondata-notebook-docker-image-by-manual.md

This documentation will describe how to build carbondata notebook docker images. It should already installed docker environment. CarbonData notebook docker images is based on spark notebook images. Downloading latest version of docker images of spark notebook ```shell docker pull jupyter/all-spark-notebook:latest ``` Downloading specify version of docker images of spark notebook ```shell docker pull jupyter/all-spark-notebook:spark-3.4.0 ``` Refer to https://hub.docker.com/r/jupyter/all-spark-notebook/tags ``` docker run -d -p 8888:8888 --restart always jupyter/all-spark-notebook:latest ``` Get container if of spark notebook container. ```shell localhost:carbondata xubo$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 305f1277690c xubo245/all-carbondata-notebook:latest "tini -g -- start-no" 15 minutes ago Up 15 minutes 0.0.0.0:8888->8888/tcp, :::8888->8888/tcp youthful_wright ``` Add carbondata jar to spark jars directory: ``` docker cp apache-carbondata-2.3.0-bin-spark3.1.1-hadoop2.7.2.jar 305f1277690c:/usr/local/spark-3.1.1-bin-hadoop3.2/jars/ ``` The apache-carbondata-2.3.0-bin-spark3.1.1-hadoop2.7.2.jar is from assembly/target/scala-2.12/ directory of carbondata project. You can build jar by maven, For example: ``` mvn -DskipTests -Pspark-3.1 clean package -Pbuild-with-format ``` Save the spark notebook docker images with carbondata jar to carbondata notebook image. ``` docker commit 305f1277690c xubo245/all-carbondata-notebook:latest ``` Please refer to
Project: Chef InSpec (Provisioning / Security & Compliance)
File: azurerm_monitor_log_profiles.md

+++ title = "azurermmonitorlog_profiles resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurermmonitorlog_profiles" identifier = "inspec/resources/azure/azurermmonitorlogprofiles.md azurermmonitorlogprofiles resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azuremonitorlogprofiles" >}} Use the `azurermmonitorlog_profiles` InSpec audit resource to verify that a Log Profile exists. This resource interacts with version `2016-03-01` of the Azure Management API. For more information see the . At the moment, there doesn't appear to be a way to select the version of the Azure API docs. If you notice a newer version being referenced in the official documentation please open an issue or submit a pull request using the updated version. This resource is available in the `inspec-azure` [resource pack](/inspec/glossary/#resource-pack). To use it, add the following to your `inspec.yml` in your top-level profile: depends: name: inspec-azure git: https://github.com/inspec/inspec-azure.git You'll also need to setup your Azure credentials; see the resource pack . An `azurermmonitorlog_profiles` resource block identifies a Log Profile by name. describe azurermmonitorlog_profiles do ... end describe azurermmonitorlog_profiles do its('names') { should include('ExampleProfile') } end `names` The name of the Log Profile its('names') { should include('ExampleProfile') } {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The control will pass if the resource returns a result. Use `should_not` if you expect zero matches. describe azurermmonitorlog_profiles do its('names') { should include('ExampleProfile') } end describe azurermmonitorlog_profiles do its('names') { should_not include('ExampleProfile') } end Your [Service Principal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal) must be setup with a `contributor` role on the subscription you wish to test.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.11.md

layout: release date: 2024-01-17 tag: v0.7.11 Generic Annotation Node @aabidsofi19 (#9974) [chore] fix unwanted warning on save @theBeginner86 (#9977) update: update Maintainer.md @RipulHandoo (#9972) [chore] Fix Failing MeshKit Error Util @theBeginner86 (#9962) [Docs] New make target for non-incremental serving of site @leecalcote (#9945) [Permission] Update permission spreadsheet @Yashsharma1911 (#9948) [bug] Fix Error Message on K8s Manifest Upload @theBeginner86 (#9940) [Relationships] AWS RDS DBCluster to IAM Role @leecalcote (#9666) [chore] fix models @theBeginner86 (#9921) Fix naming convention @sudhanshutech (#9993) Fix horizontal line alignment in registry tree view @Yashsharma1911 (#9989) fixed the dropdown icon bug across modals @captain-Akshay (#9983) [UI] Enhance the Meshery UI registry @Yashsharma1911 (#9939) fix controller version logic @MUzairS15 (#9975) [Env/Workspace] - Remove org selector from create environment and workspace modal @senali-d (#9961) Feat: Import/Export Design as OCI Artifact @theBeginner86 (#9861) [UI] Filter support for Designs and Filters @sudhanshutech (#9918) Fix Id formatter and empty data UX @sudhanshutech (#9933) solved icons cutoff issue @Aniket-76 (#9907) [UI] Fix dark mode issues in error component @Yashsharma1911 (#9924) [UI] Fix dysfunctional `Metrics` tab. @MUzairS15 (#9915) [docs] Enhance Component Docs Updater Script @theBeginner86 (#9934) [DOCS] Fixed broken links @MonalikaPatnaik (#9988) [Docs] Add GitHub link to main navigation menu @leecalcote (#9970) [Docs] Chore: Additional 404 error messages @leecalcote (#9956) [Docs] Redirects for Adapters @leecalcote (#9955) fixed broken link issue in configuration-management.md @prathyushmadhu (#9954) [Docs] Revise integrations on homepage @leecalcote (#9946) fix: meshery.io integrations link @leecalcote (#9944) Feat: Import/Export Design as OCI Artifact @theBeginner86 (#9861) solved issue #9913 @AkashMeheta (#9927) [Docs] Enhanced Integrations list @leecalcote (#9937) [Docs] Add menu toggle. Collapsed by default @leecalcote (#9902) [Doc] Extensibility CASL @Yashsharma1911 (#9898) Fixed many links including the issue #9892 @Conqxeror (#9923) Update deploying-sample-apps.md @chiragbiradar (#9930) [Docs] Categorization and partial restructure @leecalcote (#9920) [Docs] feat: add google tag manager @leecalcote (#9912) [Docs] Restructure proposal @leecalcote (#9887) Thank you to our contributors for making this release possible: @AkashMeheta, @Aniket-76, @Conqxeror, @MUzairS15, @MonalikaPatnaik, @RipulHandoo, @Yashsharma1911, @aabidsofi19, @captain-Akshay, @chiragbiradar, @iArchitSharma, @l5io, @leecalcote, @prathyushmadhu, @senali-d, @sudhanshutech, @theBeginner86, @vishalvivekm and l5io
Project: Glasskube (App Definition and Development / Application Definition & Image Build)
File: telemetry.md

By default, Glasskube collects some client usage data. We use this data to better understand how our users use Glasskube, identify bugs and make Glasskube a better product overall. Glasskube version Type of Operating System (Linux/Windows/Mac) Which Glasskube-clusters the client is interacting with Executed commands (without flags' values), whether they succeeded or not, and how long they took to execute Browser user agent when using the UI Executed operations on the UI (without config values) Glasskube version Kubernetes version Number of nodes Type of cloud provider Which Glasskube packages are installed and in which version, and whether the installation is successful or faulty Browser user agent Visited Page Personal information about you Any other information about cluster resources Any kind of data about what else is running or stored on your machine or your cluster Any sensitive or secret information contained in your cluster Any configured values of the Glasskube packages Specific data about errors, as they could contain sensitive information about your cluster configuration As Glasskube is fully open source, you can find exactly what we track by looking up in our code base. We use to store this kind of information. The data is stored in Posthogs EU cloud. Use the command `glasskube telemetry status` to check whether telemetry is disabled for this cluster or not. Disable telemetry with `glasskube telemetry disable`. You can always opt in again with glasskube telemetry enable. The information about whether telemetry is enabled or not, is stored once per cluster installation.