cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.0-rc.5y.md

layout: release date: 2022-06-17 tag: v0.6.0-rc.5y language: en Fix validation error and whitespacing bug @Revolyssup (#5644) Logout button move @warunicorn19 (#5641) upgrade meshkit @Revolyssup (#5637) [DDE] Fix: dde ws undefined @sudo-NithishKarthik (#5636) [DDE] Fix: Set isLogged to false after logging out @sudo-NithishKarthik (#5635) [DDE] Fix: automatically change state once logged out @sudo-NithishKarthik (#5634) fixed issue with logo before login and added logout button @warunicorn19 (#5630) [Server] Fix error code conflicts @gr455 (#5626) Allow provider to be set via query parameter @sudo-NithishKarthik (#5627) Fix failing save context for incluster @Revolyssup (#5601) [dde] UI Change to adapt to the exposed server version @sudo-NithishKarthik (#5596) fix: Service mesh provisioning @sudo-NithishKarthik (#5595) exposed meshery server version in dde @warunicorn19 (#5591) Fix panic @Revolyssup (#5593) Fix NATS connectivity test @MUzairS15 (#5583) Meshery-Settings: Enable Subscriptions and fix problems with settings page @Abhishek-kumar09 (#5645) [UI]Changed cursor to pointer @Rohith-Raju (#5632) Add operator status query @MUzairS15 (#5633) [UI] Undeploy card view button color update @Chadha93 (#5640) [UI] Support for Undeploy Pattern and Applications @Chadha93 (#5617) Fix problems with context-switching operation from Header @Abhishek-kumar09 (#5625) Fix: Metrics components not showing up in dashboard @Abhishek-kumar09 (#5624) Fix Event Streams in Meshery Notification Center @Abhishek-kumar09 (#5621) lifecycle minor bug fix with no adapter @Abhishek-kumar09 (#5620) Bug fixes @MUzairS15 (#5611) [Fix] Lifecylce Page Fixes @Abhishek-kumar09 (#5614) Bump eslint-plugin-react from 7.29.4 to 7.30.0 in /provider-ui @dependabot (#5580) Improve UI @MUzairS15 (#5602) Bump @babel/eslint-parser from 7.17.0 to 7.18.2 in /ui @dependabot (#5555) Multi context refactor @Revolyssup (#5528) Ci/marioarriaga92/5592 fix cypress v10 legacy config file error @MarioArriaga92 (#5597) [UI] Pattern file bug fixes @Chadha93 (#5587) [UI] Settings button style fix for lifecycle @Chadha93 (#5588) material-ui/core from 4.12.3 to 4.12.4 @Harshit-Dandriyal (#5585) [UI] Undeploy card view button color update @Chadha93 (#5640) [UI] Support for Undeploy Pattern and Applications @Chadha93 (#5617) [UI] Pattern file bug fixes @Chadha93 (#5587) Fix golangci-lint failures @haanhvu (#5612) Bump eslint-plugin-react from 7.29.4 to 7.30.0 in /provider-ui @dependabot (#5580) [Lifecycle] Remove CPX from default config @leecalcote (#5604) Bump @babel/eslint-parser from 7.17.0 to 7.18.2 in /ui @dependabot (#5555) Bump google.golang.org/grpc from 1.46.0 to 1.47.0 @dependabot (#5560) [Doc] Add troubleshooting steps for Service Mesh installation @MUzairS15 (#5616) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @Harshit-Dandriyal, @MUzairS15, @MarioArriaga92, @Revolyssup, @Rohith-Raju, @dependabot, @dependabot[bot], @gr455, @haanhvu, @l5io, @leecalcote, @sudo-NithishKarthik, @warunicorn19 and Nithish
Project: Cadence Workflow (Provisioning / Automation & Configuration)
File: MYSQL_SETUP.md

This document describes how to install MySQL 8.0 locally with Docker. Note: Install the docker on your machine before installing the MySQL. Make sure any MySQL containers are terminated and removed ``` docker ps -a docker kill <containerid> && docker rm <containerid> # remove any MySQL containers. ``` Fetch docker image (version 8.0 is what Travis runs so its what you will want locally) ``` docker pull mysql/mysql-server:8.0 ``` Run docker container (note the port mapping so that 3306 is exposed locally) ``` docker run -p 3306:3306 --name=mysql1 -d mysql/mysql-server:8.0 ``` When docker starts up the root MySQL user will have an auto generated password. You need to get that password to log into the container ``` docker logs mysql1 2>&1 | grep GENERATED ``` Log into the container (when prompted for password use the password gotten from last step). ``` docker exec -it mysql1 mysql -uroot -p ``` Before any SQL operations can be performed you must reset the root user's password (use anything you like in replace of root_password). ``` SET PASSWORD = PASSWORD('root_password'); ``` Now create the user that local MySQL tests will use. Also grant all privileges to user. ``` CREATE USER 'uber'@'%' IDENTIFIED BY 'uber'; GRANT ALL PRIVILEGES ON . TO 'uber'@'%'; ```
Project: Rundeck (Provisioning / Automation & Configuration)
File: CONTRIBUTING.md

If you have a patch or pull request for us, thank you! The more of these guidelines you can follow, the easier (and faster) it is for us to evaluate your code and incorporate it into the development branch. (Borrowing from ): Make sure you can perform a full build and that the tests all pass. (See [Building and Testing]) Please add unit tests to demonstrate that your submission fixes an existing bug, or performs as intended. Rebase your branch on the current state of the `master` branch. Use `git rebase master`. This means you might have to deal with conflicts. Be descriptive in your commit messages: explain the purpose of all changes. You can modify commit messages by doing `git commit --amend` (for the previous change), or `git rebase -i` for earlier changes. Once your branch is cleaned up, please submit the Pull request against the `master` branch. Thanks for your help! A typical workflow: ~~~ {.sh} git checkout master git pull git checkout -b newbranch $EDITOR somefile git commit -m "my change" git checkout master && git pull git checkout - # "-" will checkout previous branch git rebase master git push myfork newbranch ~~~
Project: Meshery (Provisioning / Automation & Configuration)
File: camel-k.md

layout: integration title: Camel K subtitle: Collaborative and visual infrastructure as code for Camel K image: /assets/img/integrations/camel-k/icons/color/camel-k-color.svg permalink: extensibility/integrations/camel-k docURL: https://docs.meshery.io/extensibility/integrations/camel-k description: integrations-category: App Definition and Development integrations-subcategory: Application Definition & Image Build registrant: Artifact Hub components: name: build colorIcon: assets/img/integrations/camel-k/components/build/icons/color/build-color.svg whiteIcon: assets/img/integrations/camel-k/components/build/icons/white/build-white.svg description: name: camel-catalog colorIcon: assets/img/integrations/camel-k/components/camel-catalog/icons/color/camel-catalog-color.svg whiteIcon: assets/img/integrations/camel-k/components/camel-catalog/icons/white/camel-catalog-white.svg description: name: integration-kit colorIcon: assets/img/integrations/camel-k/components/integration-kit/icons/color/integration-kit-color.svg whiteIcon: assets/img/integrations/camel-k/components/integration-kit/icons/white/integration-kit-white.svg description: name: integration-platform colorIcon: assets/img/integrations/camel-k/components/integration-platform/icons/color/integration-platform-color.svg whiteIcon: assets/img/integrations/camel-k/components/integration-platform/icons/white/integration-platform-white.svg description: name: integration colorIcon: assets/img/integrations/camel-k/components/integration/icons/color/integration-color.svg whiteIcon: assets/img/integrations/camel-k/components/integration/icons/white/integration-white.svg description: name: kamelet-binding colorIcon: assets/img/integrations/camel-k/components/kamelet-binding/icons/color/kamelet-binding-color.svg whiteIcon: assets/img/integrations/camel-k/components/kamelet-binding/icons/white/kamelet-binding-white.svg description: name: kamelet colorIcon: assets/img/integrations/camel-k/components/kamelet/icons/color/kamelet-color.svg whiteIcon: assets/img/integrations/camel-k/components/kamelet/icons/white/kamelet-white.svg description: name: pipe colorIcon: assets/img/integrations/camel-k/components/pipe/icons/color/pipe-color.svg whiteIcon: assets/img/integrations/camel-k/components/pipe/icons/white/pipe-white.svg description: featureList: [ "Define routing and mediation rules in a variety of domain-specific languages.", "Enables easier integration with all kinds of transport or messaging models.", "Minimal dependencies for easy embedding in any Java application." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: KICS (Provisioning / Security & Compliance)
File: 7ef7d141-9fbb-4679-a977-fd0883436906.md

title: Cluster Master Authentication Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7ef7d141-9fbb-4679-a977-fd0883436906 Query name: Cluster Master Authentication Disabled Platform: GoogleDeploymentManager Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Kubernetes Engine Clusters must have Master Authentication set to enabled, which means the attribute 'masterAuth' must have the subattributes 'username' and 'password' defined and not empty<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" resources: name: cluster type: container.v1.cluster properties: description: cluster ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="5" resources: name: cluster type: container.v1.cluster properties: masterAuth: clientKey: test ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="5" resources: name: cluster type: container.v1.cluster properties: masterAuth: username: password: ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: cluster type: container.v1.cluster properties: masterAuth: username: test password: test ```
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: API-008-multi-state-store-api-design.md

Accepted This decision record is to support multiple state stores support in Dapr. We agreed on the decision to introduce the breaking change in API to support multi state store with no backward compatibility. With this change , the state API allows the app to target a specific state store by store-name, for example: v1.0/state/storeA/ v1.0/state/storeB/ Earlier this breaking change, the API is v1.0/state/`<key>` We have reviewed multi storage API design for completeness and consistency. New state store API is v1.0/state/`<store-name>`/ If user is using actors and like to persist the state then user must provide actorStateStore: true in the configuration yaml. If the attribute is not specified or multiple actor state stores are configured, Dapr runtime will log warning. The actor API to save the state will fail in both these scenarios where actorStore is not specified or multiple actor stores are specified. It is noted that after this breaking change, actor state store has to be specified unlike earlier where first state store is picked up by default. It is noted that this breaking change will also require a CLI change to generate the state store YAML for redis with actorStateStore. To provide multiple stores, user has to provide separate YAML for each store and giving unique name for the store. It is noted that the param's keyPrefix represents state key prefix, it's value included ${appid} is the microservice appid, ${name} is the CRDs component's unique name, ${none} is non key prefix and the custom key prefix For example, below are the 2 sample yaml files in which redis store is used as actor state store while mongodb store is not used as actor state store. ``` apiVersion: dapr.io/v1alpha1 kind: Component metadata: name: myStore1 # Required. This is the unique name of the store. spec: type: state.redis metadata: name: keyPrefix value: none # Optional. default appid. such as: appid, none, name and custom key prefix name: <KEY> value: <VALUE> name: <KEY> value: <VALUE> name: actorStateStore # Optional. default: false value : true ``` ``` apiVersion: dapr.io/v1alpha1 kind: Component metadata: name: myStore2 # Required. This is the unique name of the store. spec: type: state.mongodb metadata: name: keyPrefix value: none # Optional. default appid. such as: appid, none, name and custom key prefix name: <KEY> value: <VALUE> name: <KEY> value: <VALUE> ``` So with the above example, the state APIs will be : v1.0/state/myStore1/`<key>` and v1.0/state/myStore2/`<key>` With these changes we should meet multiple state stores requirements.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: azurerm_storage_account_blob_containers.md

+++ title = "azurermstorageaccountblobcontainers resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurermstorageaccountblobcontainers" identifier = "inspec/resources/azure/azurermstorageaccountblobcontainers.md azurermstorageaccountblobcontainers resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azurestorageaccountblob_containers" >}} Use the `azurermstorageaccountblobcontainers` InSpec audit resource to test properties and configuration of Blob Containers within an Azure Storage Account. This resource interacts with version `2018-07-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 . This resource first became available in 1.3.0 of the inspec-azure resource pack. An `azurermstorageaccountblobcontainers` block returns all Blob Containers within a given Azure Storage Account. The `resourcegroup` and `storageaccount_name` must be given as parameters. describe azurermstorageaccountblobcontainers(resourcegroup: 'rg', storageaccount_name: 'production') do ... end The following examples show how to use this InSpec audit resource. describe azurermstorageaccountblobcontainers(resourcegroup: 'rg', storageaccount_name: 'sa') do its('names') { should include('myblobcontainer') } end `ids` `names` `etags` Filters the results to include only those containers which match the given name. This is a string value. describe azurermstorageaccountblobcontainers(resourcegroup: 'rg', storageaccount_name: 'sa') do its('names') { should include('myblobcontainer') } end `ids` `names` `etags` Azure resource ID. Blob Container name, e.g. `my-blob-container`. its('names') { should include 'my-blob-container' } The etag of the Resource, e.g. `\"0x8D592D74CC20EBA\"`. {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The control will pass if the filter returns at least one result. Use `should_not` if you expect zero matches. describe azurermstorageaccountblobcontainers do it { should exist } 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: KubeDB by AppsCode (App Definition and Development / Database)
File: concept.md

title: MongoDB Hidden-Node Concept menu: docs_{{ .version }}: identifier: mg-hidden-concept name: Concept parent: mg-hidden weight: 10 menuname: docs{{ .version }} sectionmenuid: guides New to KubeDB? Please start . Hidden node is a member of MongoDB ReplicaSet. It maintains a copy of the primary's data set but is invisible to client applications. Hidden members are good for workloads with different usage patterns from the other members in the replica set. For example, You are using an inMemory Mongodb database server, but in the same time you want your data to be replicated in a persistent storage, in that case, Hidden node is a smart choice. Hidden members must always be priority 0 members and so cannot become primary. The db.hello() method does not display hidden members. Hidden members, however, may vote in elections. <p align="center"> <img alt="hidden-node" src="/docs/images/mongodb/hidden.png" width="500" height="408"> </p> There are some important considerations that should be taken care of by the Database administrators when deploying MongoDB. Hidden members may vote in replica set elections. If you stop a voting hidden member, ensure that the set has an active majority or the primary will step down. Always try to avoid scenarios where hidden-node is deployed on the same host as the primary of the replicaset. As non-voting replica set members (i.e. members[n].votes is 0) cannot contribute to acknowledge write operations with majority write concern, hidden-members have to be voting capable in majority write-concern scenario. using KubeDB. Detail concepts of . Detail concepts of . Want to hack on KubeDB? Check our .
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-qry-select-lateral-subquery.md

layout: global title: LATERAL SUBQUERY displayTitle: LATERAL SUBQUERY 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. `LATERAL SUBQUERY` is a subquery that is preceded by the keyword `LATERAL`. It provides a way to reference columns in the preceding `FROM` clause. Without the `LATERAL` keyword, subqueries can only refer to columns in the outer query, but not in the `FROM` clause. `LATERAL SUBQUERY` makes the complicated queries simpler and more efficient. ```sql [ LATERAL ] primaryrelation [ joinrelation ] ``` primary_relation* Specifies the primary relation. It can be one of the following: Table relation Aliased query Syntax: `( query ) [ [ AS ] alias ]` Aliased relation Syntax: `( relation ) [ [ AS ] alias ]` * join_relation* Specifies a . ```sql CREATE TABLE t1 (c1 INT, c2 INT); INSERT INTO t1 VALUES (0, 1), (1, 2); CREATE TABLE t2 (c1 INT, c2 INT); INSERT INTO t2 VALUES (0, 2), (0, 3); SELECT * FROM t1, LATERAL (SELECT * FROM t2 WHERE t1.c1 = t2.c1); +--+-+--+-+ | t1.c1 | t1.c2 | t2.c1 | t2.c2 | +-+--+--+-+ | 0 | 1 | 0 | 3 | | 0 | 1 | 0 | 2 | +-+--+--+-+ SELECT a, b, c FROM t1, LATERAL (SELECT c1 + c2 AS a), LATERAL (SELECT c1 - c2 AS b), LATERAL (SELECT a * b AS c); +--+-+--+ | a | b | c | +-+--+--+ | 3 | -1 | -3 | | 1 | -1 | -1 | +-+--+--+ ```
Project: StarRocks (App Definition and Development / Database)
File: ALTER_LOAD.md

displayed_sidebar: "English" Changes the priority of a Broker Load job that is in the QUEUEING or LOADING state. This statement is supported since v2.5. NOTE Changing the priority of a Broker Load job that is in the LOADING state does not affect the execution of the job. ```SQL ALTER LOAD FOR <label_name> PROPERTIES ( 'priority'='{LOWEST | LOW | NORMAL | HIGH | HIGHEST}' ) ``` | Parameter | Required | Description | | - | | | | label_name | Yes | The label of the load job. Format: `. | | priority | Yes | The new priority that you want to specify for the load job. Valid values: `LOWEST`, `LOW`, `NORMAL`, `HIGH`, and `HIGHEST`. See . | Suppose that you have a Broker Load job whose label is `test_db.label1` and the job is in the QUEUEING state. If you want to run the job at the soonest, you can run the following command to change the priority of the job to `HIGHEST`: ```SQL ALTER LOAD FOR test_db.label1 PROPERTIES ( 'priority'='HIGHEST' ); ```
Project: external-secrets (Provisioning / Security & Compliance)
File: provider-passworddepot.md

External Secrets Operator integrates with to sync Password Depot to secrets held on the Kubernetes cluster. The API requires a username and password. ```yaml {% include 'password-depot-credentials-secret.yaml' %} ``` Be sure the `passworddepot` provider is listed in the `Kind=SecretStore` and host and database are set. ```yaml {% include 'passworddepot-secret-store.yaml' %} ``` To sync a Password Depot variable to a secret on the Kubernetes cluster, a `Kind=ExternalSecret` is needed. ```yaml {% include 'passworddepot-external-secret.yaml' %} ``` DataFrom can be used to get a variable as a JSON string and attempt to parse it. ```yaml {% include 'passworddepot-external-secret-json.yaml' %} ``` The operator will fetch the project variable and inject it as a `Kind=Secret`. ``` kubectl get secret passworddepot-secret-to-create -o jsonpath='{.data.secretKey}' | base64 -d ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: kernel_parameter.md

+++ title = "kernel_parameter resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "kernel_parameter" identifier = "inspec/resources/os/kernelparameter.md kernelparameter resource" parent = "inspec/resources/os" +++ Use the `kernel_parameter` Chef InSpec audit resource to test kernel parameters on Linux platforms. These parameters are located under `/proc/cmdline`. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `kernel_parameter` resource block declares a parameter and then a value to be tested: describe kernel_parameter('path.to.parameter') do its('value') { should eq 0 } end where `'kernel.parameter'` must specify a kernel parameter, such as `'net.ipv4.conf.all.forwarding'` `{ should eq 0 }` states the value to be tested The following examples show how to use this Chef InSpec audit resource. describe kernel_parameter('net.ipv4.conf.all.forwarding') do its('value') { should eq 1 } end describe kernel_parameter('net.ipv6.conf.all.forwarding') do its('value') { should eq 0 } end describe kernelparameter('net.ipv6.conf.interface.acceptredirects') do its('value') { should cmp 'true' } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: KICS (Provisioning / Security & Compliance)
File: 218413a0-c716-4b94-9e08-0bb70d854709.md

title: Secure Ciphers Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 218413a0-c716-4b94-9e08-0bb70d854709 Query name: Secure Ciphers Disabled Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: Check if secure ciphers aren't used in CloudFront<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="14" name: example community.aws.cloudfront_distribution: state: present caller_reference: unique test distribution ID origins: id: 'my test origin-000111' domain_name: www.example.com origin_path: /production custom_headers: header_name: MyCustomHeaderName header_value: MyCustomHeaderValue viewer_certificate: cloudfrontdefaultcertificate: false minimumprotocolversion: 'SSLv3' ``` ```yaml title="Negative test num. 1 - yaml file" name: example community.aws.cloudfront_distribution: state: present caller_reference: unique test distribution ID origins: id: my test origin-000111 domain_name: www.example.com origin_path: /production custom_headers: header_name: MyCustomHeaderName header_value: MyCustomHeaderValue viewer_certificate: cloudfrontdefaultcertificate: true ```