cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeCarrier (App Definition and Development / Application Definition & Image Build)
File: code-of-conduct.md

As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities. We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality. Examples of unacceptable behavior by participants include: The use of sexualized language or imagery Personal attacks Trolling or insulting/derogatory comments Public or private harassment Publishing other's private information, such as physical or electronic addresses, without explicit permission Other unethical or unprofessional conduct. 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. By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project. Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team. This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Loodse Conduct Committee via coc@loodse.com. This Code of Conduct is adapted from the and , version 1.2.0.
Project: KICS (Provisioning / Security & Compliance)
File: bbf6b3df-4b65-4f87-82cc-da9f30f8c033.md

title: VM Not Attached To Network hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: bbf6b3df-4b65-4f87-82cc-da9f30f8c033 Query name: VM Not Attached To Network Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: No Network Security Group is attached to the Virtual Machine<br> ```tf title="Positive test num. 1 - tf file" hl_lines="5" resource "azurermvirtualmachine" "positive1" { name = "${var.prefix}-vm" location = azurermresourcegroup.main.location resourcegroupname = azurermresourcegroup.main.name networkinterfaceids = [] vmsize = "StandardDS1_v2" osprofilelinux_config { disablepasswordauthentication = false } } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermnetworkinterface" "negative1" { name = "${var.prefix}-nic" location = azurermresourcegroup.main.location resourcegroupname = azurermresourcegroup.main.name ip_configuration { name = "testconfiguration1" subnetid = azurermsubnet.internal.id privateipaddress_allocation = "Dynamic" } } resource "azurermvirtualmachine" "negative2" { name = "${var.prefix}-vm" location = azurermresourcegroup.main.location resourcegroupname = azurermresourcegroup.main.name networkinterfaceids = [azurermnetworkinterface.main.id] vmsize = "StandardDS1_v2" osprofilelinux_config { disablepasswordauthentication = false } } ```
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.2.6.4.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Blocker | Should not upload partial logs for MR jobs or other "short-running' applications* Applications which made use of the LogAggregationContext in their application will need to revisit this code in order to make sure that their logs continue to get rolled out. | Critical | RPC client does not time out by default* This fix includes public method interface change. A follow-up JIRA issue for this incompatibility for branch-2.7 is HADOOP-13579.
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: hello.md

A guidebook is a markdown file, written with a bit of care so that it can be automatically processed into a wizard experience. What you are seeing here on the right is the wizard that was automatically generated from the markdown source on the left. Try editing the source! Look for examples of supported syntax. :rocket: === "Option A" Description for ${choice}. ```shell echo You chose ${choice} ``` === "Option B" Description for ${choice}. ```shell echo You chose ${choice} ```
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: information-flow-ansible-operator.md

title: Information Flow for Operator SDK Ansible-based Operators linkTitle: Information Flow weight: 20 Gets the primary resource based on NamespacedName this uses the cache from controller runtime. Determines if the resource is deleted based on the existence of a finalizer and a metadata.DeletionTimeStamp. If deleted and not one of our finalizers we exit with no error. If finalizer is needed, but is not on the object, and is not deleted then add it and continue. Marks the status of the CR as running if it is managing the status and continues Creates the proxys kubeconfig. Calls out Runner using the runner package. Watches for events to come back across the results channel. Logs the events Keeps track of failure messages as well as the StatusEvent, which is the ending event that the Ansible sends to mark the playbook/role is completed. If a finalizer exists and the resource was deleted then remove the finalizer and update the object and continue. Update the status of the resource to mark that the run has completed Create the socket that ansible will communicate over Translate object.Spec -> ansible vars (camelCase -> camel_case) and adds them as parameters for the ansible-runner directory. Create the directory on disk for ansible runner. or update the files on disk if they already exist. Run the ansible runner command in a go routine, when this exits close the channel for the socket. Every request to the k8s api goes through the proxy. The owner reference is injected into the object that is being created in the same namespace as the CR. The operator-sdk annotations are injected into the object that is being created outside of namepsace of the CR. The proxy then adds dependent watches for the correct controller if we have not started watching the type already. On a GET, we attempt to use the informer cache to get the resource. This will also attempt to re-add dependent watches if we find a type with an owner reference. Ansible is run and has its own process. Ansible-runner-http package allows runner to set us ansible events as ansible is being run. ansible runner uses the socket and the controller is watching the events as they come through the channel.
Project: Checkov (Provisioning / Security & Compliance)
File: outputs_issue.md

name: Outputs Issue about: Create an issue regarding checkov's output (addition or fix) title: '' labels: 'outputs' assignees: '' Describe the issue If regarding an existing output (json, junit-xml etc.) please note what is the current state and what is the expected state. For new outputs - please describe the use case to add it. Additional context Add any other context about the problem here.
Project: Matano (Provisioning / Security & Compliance)
File: CODE_OF_CONDUCT.md

Our values guide us in our day-to-day interactions and decision-making. Our open source projects are no exception. Trust, respect, collaboration and transparency are core values we believe should live and breathe within our projects. Our community welcomes participants from around the world with different experiences, unique perspectives, and great ideas to share. To that end, we have a few ground rules that we ask people to adhere to. This code applies equally to founders, mentors and those seeking help and guidance. Be friendly and patient. Be welcoming. Be considerate. Be respectful. Be careful in the words that you choose. Maintainers have the right and responsibility to remove contributions that are not aligned to this Code of Conduct, or to ban any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. If you believe someone is violating the code of conduct, we ask that you report it by emailing conduct@matano.dev. This Code of Conduct is adapted from the and the .
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: cpuset-cpus.md

CPUs in which to allow execution. Can be specified as a comma-separated list (e.g. 0,1), as a range (e.g. 0-3), or any combination thereof (e.g. 0-3,7,11-15). On some systems, changing the resource limits may not be allowed for non-root users. For more details, see https://github.com/containers/podman/blob/main/troubleshooting.md#26-running-containers-with-resource-limits-fails-with-a-permissions-error This option is not supported on cgroups V1 rootless systems.
Project: ShardingSphere (App Definition and Development / Database)
File: graduate.en.md

+++ title = "Congratulations on graduation of Apache ShardingSphere as a Top-Level Project!" weight = 11 chapter = true +++ Apache Software Foundation (ASF), The most popular open-source software foundation, announced Apache ShardingSphere as a Top-Level Project (TLP) on Wakefield, MA, 16th April 2020. ShardingSphere entered into the Apache incubator since 10th November 2018. With the help of mentors and the whole community, The Apache board approved its graduation proposal with 10 +1 votes successfully, which ends up its 17 months incubator and promotes it as TLP. As the first project graduating from Incubator in 2020, this cheering news was published subsequently on Apache official blog with the support of Sally Khudairi, Vice President Marketing & Publicity of ASF. Apache ShardingSphere was born in dangdang.com, grew up fastly in JD.com, and now becomes a famous Apache distributed database middleware ecosystem. The evolvement from a light JDBC driver into an ecosystem presents the efforts and enthusiasm of the whole community in the past 17 months. Special thanks for the guidance from IPMCs, mentors. Many thanks for contributions from 120+ committers all over the world. What's more, we are glad to see the community still move actively during the coronavirus outbreak.
Project: YugabyteDB (App Definition and Development / Database)
File: containment-operators.md

title: "@> and <@ (containment operators) [JSON]" headerTitle: "@> and <@ (containment operators)" linkTitle: "@> and <@ (containment)" description: Test whether one jsonb value contains another jsonb value using the JSON containment operators (@> and <@). menu: v2.18: identifier: containment-operators parent: json-functions-operators weight: 16 type: docs Purpose: the `@>` operator tests if the left-hand JSON value contains the right-hand JSON value. The `<@` operator tests if the right-hand JSON value contains the left-hand JSON value. Signatures: ``` input values: jsonb @> jsonb return value: boolean ``` and: ``` input values: jsonb <@ jsonb return value: boolean ``` Notes: Each of these operators requires that the inputs are presented as `jsonb` values. There are no `json` overloads. ```plpgsql do $body$ declare j_left constant jsonb := '{"a": 1, "b": 2}'; j_right constant jsonb := '{"b" :2}'; begin assert (jleft @> jright) and (jright <@ jleft), 'unexpected'; end; $body$; ```
Project: YDB (App Definition and Development / Database)
File: yql-query-overview.md

You can use the following {{ ydb-short-name }} CLI commands to run YQL queries: : Runs YQL queries and scripts with streaming enabled (without limiting the amount of returned data). : Runs YQL queries and scripts, limiting the amount of data returned. You can also use this command to view the query execution plan and the response metadata. : Runs with a given level of transaction isolation and a standard retry policy. : Switches the console to interactive mode and executes YQL queries and scripts. Commands .
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.1.5.md

layout: release date: 2019-09-20 tag: v0.1.5 language: en What's new? Changelog UX Improvements `mesheryctl start` now waits for meshery application containers to be up before launching the user's browser. `mesheryctl stop` now shows command progress akin to the experience when using `meshery` bash script.
Project: ORY Hydra (Provisioning / Key Management)
File: JsonPatch.md

Name | Type | Description | Notes | - | - | - From | Pointer to string | This field is used together with operation \&quot;move\&quot; and uses JSON Pointer notation. Learn more . | [optional] Op | string | The operation to be performed. One of \&quot;add\&quot;, \&quot;remove\&quot;, \&quot;replace\&quot;, \&quot;move\&quot;, \&quot;copy\&quot;, or \&quot;test\&quot;. | Path | string | The path to the target path. Uses JSON pointer notation. Learn more . | Value | Pointer to interface{} | The value to be used within the operations. Learn more . | [optional] `func NewJsonPatch(op string, path string, ) *JsonPatch` NewJsonPatch instantiates a new JsonPatch object This constructor will assign default values to properties that have it defined, and makes sure properties required by API are set, but the set of arguments will change when the set of required properties is changed `func NewJsonPatchWithDefaults() *JsonPatch` NewJsonPatchWithDefaults instantiates a new JsonPatch object This constructor will only assign default values to properties that have it defined, but it doesn't guarantee that properties required by API are set `func (o *JsonPatch) GetFrom() string` GetFrom returns the From field if non-nil, zero value otherwise. `func (o JsonPatch) GetFromOk() (string, bool)` GetFromOk returns a tuple with the From field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *JsonPatch) SetFrom(v string)` SetFrom sets From field to given value. `func (o *JsonPatch) HasFrom() bool` HasFrom returns a boolean if a field has been set. `func (o *JsonPatch) GetOp() string` GetOp returns the Op field if non-nil, zero value otherwise. `func (o JsonPatch) GetOpOk() (string, bool)` GetOpOk returns a tuple with the Op field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *JsonPatch) SetOp(v string)` SetOp sets Op field to given value. `func (o *JsonPatch) GetPath() string` GetPath returns the Path field if non-nil, zero value otherwise. `func (o JsonPatch) GetPathOk() (string, bool)` GetPathOk returns a tuple with the Path field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *JsonPatch) SetPath(v string)` SetPath sets Path field to given value. `func (o *JsonPatch) GetValue() interface{}` GetValue returns the Value field if non-nil, zero value otherwise. `func (o JsonPatch) GetValueOk() (interface{}, bool)` GetValueOk returns a tuple with the Value field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *JsonPatch) SetValue(v interface{})` SetValue sets Value field to given value. `func (o *JsonPatch) HasValue() bool` HasValue returns a boolean if a field has been set. `func (o *JsonPatch) SetValueNil(b bool)` SetValueNil sets the value for Value to be an explicit nil `func (o *JsonPatch) UnsetValue()` UnsetValue ensures that no value is present for Value, not even an explicit nil
Project: KICS (Provisioning / Security & Compliance)
File: 1bcdf9f0-b1aa-40a4-b8c6-cd7785836843.md

title: API Gateway API Protocol Not HTTPS hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 1bcdf9f0-b1aa-40a4-b8c6-cd7785836843 Query name: API Gateway API Protocol Not HTTPS Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: API Gateway API protocol should be set to HTTPS<br> ```tf title="Positive test num. 1 - tf file" hl_lines="14" resource "alicloudapigateway_group" "apiGroup" { name = "ApiGatewayGroup" description = "description of the api group" } resource "alicloudapigateway_api" "apiGatewayApi" { name = alicloudapigateway_group.apiGroup.name groupid = alicloudapigatewaygroup.apiGroup.id description = "your description" auth_type = "APP" forcenoncecheck = false request_config { protocol = "HTTP" method = "GET" path = "/test/path1" mode = "MAPPING" } service_type = "HTTP" httpserviceconfig { address = "http://apigateway-backend.alicloudapi.com:8080" method = "GET" path = "/web/cloudapi" timeout = 12 aone_name = "cloudapi-openapi" } request_parameters { name = "aaa" type = "STRING" required = "OPTIONAL" in = "QUERY" in_service = "QUERY" name_service = "testparams" } stage_names = [ "RELEASE", "TEST", ] } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="21 14" resource "alicloudapigateway_group" "apiGroup" { name = "ApiGatewayGroup" description = "description of the api group" } resource "alicloudapigateway_api" "apiGatewayApi" { name = alicloudapigateway_group.apiGroup.name groupid = alicloudapigatewaygroup.apiGroup.id description = "your description" auth_type = "APP" forcenoncecheck = false request_config { protocol = "HTTP" method = "GET" path = "/test/path1" mode = "MAPPING" } request_config { protocol = "HTTP" method = "GET" path = "/test/path2" mode = "MAPPING" } service_type = "HTTP" httpserviceconfig { address = "http://apigateway-backend.alicloudapi.com:8080" method = "GET" path = "/web/cloudapi" timeout = 12 aone_name = "cloudapi-openapi" } request_parameters { name = "aaa" type = "STRING" required = "OPTIONAL" in = "QUERY" in_service = "QUERY" name_service = "testparams" } stage_names = [ "RELEASE", "TEST", ] } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudapigateway_group" "apiGroup" { name = "ApiGatewayGroup" description = "description of the api group" } resource "alicloudapigateway_api" "apiGatewayApi" { name = alicloudapigateway_group.apiGroup.name groupid = alicloudapigatewaygroup.apiGroup.id description = "your description" auth_type = "APP" forcenoncecheck = false request_config { protocol = "HTTPS" method = "GET" path = "/test/path1" mode = "MAPPING" } service_type = "HTTP" httpserviceconfig { address = "https://apigateway-backend.alicloudapi.com:8080" method = "GET" path = "/web/cloudapi" timeout = 12 aone_name = "cloudapi-openapi" } request_parameters { name = "aaa" type = "STRING" required = "OPTIONAL" in = "QUERY" in_service = "QUERY" name_service = "testparams" } stage_names = [ "RELEASE", "TEST", ] } ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.12.12.md

RabbitMQ `3.12.12` is a maintenance release in the `3.12.x` . This release on June 1st, 2024. Please refer to the upgrade section from the if upgrading from a version prior to 3.12.0. This release requires Erlang 25 and supports Erlang versions up to `26.2.x`. has more details on Erlang version requirements for RabbitMQ. As of 3.12.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Users upgrading from 3.11.x (or older releases) on Erlang 25 to 3.12.x on Erlang 26 (both RabbitMQ and Erlang are upgraded at the same time) must consult the first. Release notes can be found on GitHub at . Environments with a lot of quorum queues could experience a large Erlang process build-up. The build-up was temporary but with a sufficiently large number of quorum queues it could last until the next round of periodic operations, making it permanent and depriving the node of CPU resources. GitHub issue: RabbitMQ core failed to propagate more authentication and authorization context, for example, MQTT client ID in case of MQTT connections, to authN and authZ backends. This was not intentional. GitHub issue: Nodes now takes more precaution about persisting feature flag state (specifically the effects of in-flight changes) during node shutdown. GitHub issue: Simplified some type specs. Contributed by @ariel-anieli. GitHub issue: One returned error value did not match the specification. GitHub issue: Recovering connections from QoS 0 consumers (subscribers) could fail if they were previously connected to a failed node. GitHub issue: Since (shipped in `3.12.11`), some CLI commands in certain scenarios could fail to accept input via standard output. GitHub issues: , Updated some type specs. Contributed by @ariel-anieli. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.12.12.tar.xz` instead of the source tarball produced by GitHub.
Project: Polaris (Provisioning / Security & Compliance)
File: dashboard.md

meta: name: description content: "Fairwinds Polaris | Ways to run Polaris | The Polaris dashboard can be installed on a cluster using kubectl or Helm" Want to see Polaris results for all your clusters in a single dashboard? Check out The Polaris dashboard can be installed on a cluster using kubectl or Helm. It can also be run locally, connecting to your cluster using the credentials stored in your `KUBECONFIG`. The dashboard is a good way to understand what workloads inside your cluster or Infrastructure as Code don't conform to best practices. ```bash helm repo add fairwinds-stable https://charts.fairwinds.com/stable helm upgrade --install polaris fairwinds-stable/polaris --namespace polaris --create-namespace kubectl port-forward --namespace polaris svc/polaris-dashboard 8080:80 ``` You'll need a valid `KUBECONFIG` set up for the dashboard to connect to your cluster. Binary releases can be dowloaded from the or can be installed with : ```bash brew tap reactiveops/tap brew install reactiveops/tap/polaris polaris dashboard --port 8080 ``` You can also point the dashboard to the local filesystem, instead of a live cluster: ```bash polaris dashboard --port 8080 --audit-path=./deploy/ ``` ``` docker run -d -p8080:8080 -v ~/.kube/config:/opt/app/config:ro quay.io/fairwinds/polaris:1.2 polaris dashboard --kubeconfig /opt/app/config ``` The Polaris dashboard is a way to get a simple visual overview of the current state of your Kubernetes workloads as well as a roadmap for what can be improved. The dashboard provides a cluster wide overview as well as breaking out results by category, namespace, and workload. <p align="center"> <img src="/img/dashboard-screenshot.png" alt="Polaris Dashboard" width="550"/> </p> Our default standards in Polaris are rather high, so dont be surprised if your score is lower than you might expect. A key goal for Polaris was to set a high standard and aim for great configuration by default. If the defaults weve included are too strict, its easy to adjust the configuration as part of the deployment configuration to better suit your workloads.
Project: ClickHouse (App Definition and Development / Database)
File: settings_profiles.md

slug: /en/operations/system-tables/settings_profiles Contains properties of configured setting profiles. Columns: `name` () Setting profile name. `id` () Setting profile ID. `storage` () Path to the storage of setting profiles. Configured in the `accesscontrolpath` parameter. `numelements` () Number of elements for this profile in the `system.settingsprofile_elements` table. `applytoall` () Shows that the settings profile set for all roles and/or users. `applytolist` (()) List of the roles and/or users to which the setting profile is applied. `applytoexcept` (()) The setting profile is applied to all roles and/or users excepting of the listed ones.
Project: Kyverno (Provisioning / Security & Compliance)
File: CONTRIBUTORS.md

Contributors are those who have made enough contributions to the project as defined in the . In order to add yourself as a contributor, open a PR with your information added to the table. | Maintainer | GitHub ID | |--|--| | Ved Ratan | | | Chandan DK | | | Swastik Gour | | | Amit Kumar | | | Khaled Emara | | | Anushka Mittal | | | Sanskar Gurdasani | | | D N Siva Sathyaseelan | | | Mohamed Asif S | | | Suruchi Kumari | | | Shubham Singh | |