cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-provider-set.md

layout: default title: mesheryctl-system-provider-set permalink: reference/mesheryctl/system/provider/set redirect_from: reference/mesheryctl/system/provider/set/ type: reference display-title: "false" language: en command: system subcommand: provider set provider Set provider of context in focus. Run `mesheryctl system provider list` to see the available providers. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system provider set [provider] [flags] </div> </pre> Set provider <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system provider set [provider] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -f, --force Force set provider -h, --help help for set </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -c, --context string (optional) temporarily change the current context. -v, --verbose verbose output -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.47.md

layout: release date: 2021-08-16 tag: v0.5.47 Add more eslint rules to enforce strict formatting @sudo-NithishKarthik (#3845) RJSF Styling changes for Meshery extenstions @sudo-NithishKarthik (#3879) [UI] Updates RJSF Styling for Extension Point @Jashpatel1 (#3784) Add SMI Conformance Docs @navendu-pottekkat (#3865) [ImgBot] Optimize images @imgbot (#3878) Add SMI Conformance Docs @navendu-pottekkat (#3865) Thank you to our contributors for making this release possible: @ImgBotApp, @Jashpatel1, @imgbot, @leecalcote, @navendu-pottekkat and @sudo-NithishKarthik
Project: KICS (Provisioning / Security & Compliance)
File: 98d59056-f745-4ef5-8613-32bca8d40b7e.md

title: Neptune Database Cluster Encryption Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 98d59056-f745-4ef5-8613-32bca8d40b7e Query name: Neptune Database Cluster Encryption Disabled Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: Neptune database cluster storage should have encryption enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1 19" resource "awsneptunecluster" "positive1" { cluster_identifier = "neptune-cluster-demo" engine = "neptune" backupretentionperiod = 5 preferredbackupwindow = "07:00-09:00" skipfinalsnapshot = true iamdatabaseauthentication_enabled = true apply_immediately = true } resource "awsneptunecluster" "positive2" { cluster_identifier = "neptune-cluster-demo" engine = "neptune" backupretentionperiod = 5 preferredbackupwindow = "07:00-09:00" skipfinalsnapshot = true iamdatabaseauthentication_enabled = true apply_immediately = true storage_encrypted = false } ``` ```tf title="Negative test num. 1 - tf file" resource "awsneptunecluster" "negative1" { cluster_identifier = "neptune-cluster-demo" engine = "neptune" backupretentionperiod = 5 preferredbackupwindow = "07:00-09:00" skipfinalsnapshot = true iamdatabaseauthentication_enabled = true apply_immediately = true storage_encrypted = true } ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_routers.md

+++ title = "googlecomputerouters resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputerouters" identifier = "inspec/resources/gcp/googlecomputerouters.md googlecomputerouters resource" parent = "inspec/resources/gcp" +++ A `googlecomputerouters` is used to test a Google Router resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputerouters(project: 'chef-gcp-inspec', region: 'europe-west2') do its('names') { should include 'inspec-gcp-router' } end ``` Properties that can be accessed from the `googlecomputerouters` resource: See the resource for more information. `ids` : an array of `googlecomputerouter` id `creation_timestamps` : an array of `googlecomputerouter` creation_timestamp `names` : an array of `googlecomputerouter` name `descriptions` : an array of `googlecomputerouter` description `networks` : an array of `googlecomputerouter` network `bgps` : an array of `googlecomputerouter` bgp `regions` : an array of `googlecomputerouter` region This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: align.md

title: "Align" icon: /images/logos/powered-by/align.png hasLink: "https://www.aligntech.com/" <!-- Licensed 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. -->
Project: FOSSA (Provisioning / Security & Compliance)
File: create-release.md

`fossa release-group create-release` allows you to create a FOSSA release group release. Argument | Required | Description -|-|-- `--config` / `-c` | No | The to your path to your `.fossa.yml`. `--title` / `-t ` | Yes | The name of your FOSSA release group. `--release` / `-r ` | Yes | The name of your release within your FOSSA release group. `--project-locator` | Yes | The FOSSA project locator defines a unique ID that the FOSSA API will use to reference this project. The project locator can be found in the UI on the project `Settings` page listed as the `Project Locator` underneath the `Project Title` setting. Specify multiple options by providing this argument multiple times. `--project-revision` | Yes | The revision associated with your FOSSA project. Project revisions can be found in the UI on the project `Activity` page. Refer to `Revision ID` to retrieve the specific revision you want to use for the project. Specify multiple options by providing this argument multiple times. `--project-branch` | Yes | The name of the FOSSA project branch. Specify multiple options by providing this argument multiple times. NOTE: The arguments listed as `Required` need to be provided through CLI options OR through your `.fossa.yml` configuration. Refer to to set up your `.fossa.yml`. NOTE: CLI options take precedence over the configurations in `.fossa.yml`. NOTE: Project ID values will not work if provided to `releaseGroupProjects.projectLocator`. For more details on the differences between project ID and project locator refer to . ```bash fossa release-group create-release --title example-release-group --release example-release --project-locator custom+1/example --project-revision 1234 --project-branch main --project-locator custom+1/example2 --project-revision 5678 --project-branch main ``` NOTE: `--project-locator` , `--project-revision`, and `--project-branch` must all be specified when providing a releaseGroupProject. Multiple occurrences of these arguements are accepted and are grouped together based on their order. For example, `fossa release-group create-release --title example-release-group --release example-release --project-locator custom+1/example --project-revision 1234 --project-branch main --project-locator custom+1/example2 --project-revision 5678 --project-branch main` has project groupings of (project locator: custom+1/example, project revision: 1234, project branch: main) and (project locator: custom+1/example2, project revision: 5678, project branch: main). Similarly, you can you achieve the same result by running the following command with the given `.fossa.yml` configuration: ```yaml releaseGroup: title: example-release-group release: example-release releaseGroupProjects: projectLocator: custom+1/example projectRevision: 1234 projectBranch: main projectLocator: custom+1/example2 projectRevision: 5678 projectBranch: main ``` ```bash fossa release-group create-release -c path/to/config ```
Project: Glasskube (App Definition and Development / Application Definition & Image Build)
File: package-request.md

name: Package Request about: Suggest a new Glasskube package title: '' labels: needs-triage, packages assignees: '' Package Information Name: Source Code: [if available] Website: [if available] Why we should add this package to our registry Briefly describe what this package does and why it would be useful to install it via Glasskube If you are an author of this project, let us know [ ] I am an author of this project
Project: StarRocks (App Definition and Development / Database)
File: array_sum.md

displayed_sidebar: "English" Sums all the elements in an array. From StarRocks 2.5, array_sum() can take a lambda expression as an argument. However, it cannot work directly with the Lambda expression. It must work on the result converted from . ```Haskell array_sum(array(type)) arraysum(lambdafunction, arr1,arr2...) = arraysum(arraymap(lambda_function, arr1,arr2...)) ``` `array(type)`: the array you want to calculate the sum. Array elements support the following data types: BOOLEAN, TINYINT, SMALLINT, INT, BIGINT, LARGEINT, FLOAT, DOUBLE, and DECIMALV2. `lambdafunction`: the lambda expression used to calculate the target array for arraysum(). Returns a numeric value. ```plain text mysql> select array_sum([11, 11, 12]); +--+ | array_sum([11,11,12]) | +--+ | 34 | +--+ mysql> select array_sum([11.33, 11.11, 12.324]); ++ | array_sum([11.33,11.11,12.324]) | ++ | 34.764 | ++ ``` ```plain text -- Multiply [1,2,3] by [1,2,3] and sum the elements. select arraysum(arraymap(x->x*x,[1,2,3])); ++ | arraysum(arraymap(x -> x * x, [1, 2, 3])) | ++ | 14 | ++ ``` ARRAY_SUM,ARRAY
Project: Druid (App Definition and Development / Database)
File: distinctcount.md

id: distinctcount title: "DistinctCount Aggregator" <!-- ~ 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. --> To use this Apache Druid extension, the `druid-distinctcount` in the extensions load list. Additionally, follow these steps: First, use a single dimension hash-based partition spec to partition data by a single dimension. For example visitor_id. This to make sure all rows with a particular value for that dimension will go into the same segment, or this might over count. Second, use distinctCount to calculate the distinct count, make sure queryGranularity is divided exactly by segmentGranularity or else the result will be wrong. There are some limitations, when used with groupBy, the groupBy keys' numbers should not exceed maxIntermediateRows in every segment. If exceeded the result will be wrong. When used with topN, numValuesPerPass should not be too big. If too big the distinctCount will use a lot of memory and might cause the JVM to go our of memory. Example: ```json { "queryType": "timeseries", "dataSource": "sample_datasource", "granularity": "day", "aggregations": [ { "type": "distinctCount", "name": "uv", "fieldName": "visitor_id" } ], "intervals": [ "2016-03-01T00:00:00.000/2013-03-20T00:00:00.000" ] } ``` ```json { "queryType": "topN", "dataSource": "sample_datasource", "dimension": "sample_dim", "threshold": 5, "metric": "uv", "granularity": "all", "aggregations": [ { "type": "distinctCount", "name": "uv", "fieldName": "visitor_id" } ], "intervals": [ "2016-03-06T00:00:00/2016-03-06T23:59:59" ] } ``` ```json { "queryType": "groupBy", "dataSource": "sample_datasource", "dimensions": ["sample_dim"], "granularity": "all", "aggregations": [ { "type": "distinctCount", "name": "uv", "fieldName": "visitor_id" } ], "intervals": [ "2016-03-06T00:00:00/2016-03-06T23:59:59" ] } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: mimir-distributed.md

layout: integration title: Mimir subtitle: Scale to 1 billion metrics and beyond with Meshery and Grafana Mimir image: /assets/img/integrations/mimir-distributed/icons/color/mimir-distributed-color.svg permalink: extensibility/integrations/mimir-distributed docURL: https://docs.meshery.io/tasks/performance/managing-performance description: integrations-category: Observability and Analysis integrations-subcategory: Observability and Analysis registrant: Artifact Hub components: featureList: [ "Get 100% Prometheus compatible, including remote write, PromQL, and alerting", "High availability through replication", "Advanced multi-tenancy and isolation" ] 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: Meshery (Provisioning / Automation & Configuration)
File: open-policy-agent-(opa).md

layout: integration title: Open Policy Agent (OPA) subtitle: Collaborative and visual infrastructure as code for Open Policy Agent (OPA) image: /assets/img/integrations/open-policy-agent-(opa)/icons/color/open-policy-agent-(opa)-color.svg permalink: extensibility/integrations/open-policy-agent-(opa) docURL: https://docs.meshery.io/extensibility/integrations/open policy agent (opa) description: integrations-category: Security & Compliance integrations-subcategory: Security & Compliance registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] 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: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: restore-data-from-backup-set.md

title: Restore data from backup set description: How to restore data from backup set keywords: [backup and restore, restore, backup set] sidebar_position: 1 sidebar_label: Restore from backup set import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; KubeBlocks supports restoring clusters from backups with the following instructions. View backups. For existing clusters, execute: ```shell kbcli cluster list-backups mysql-cluster ``` If the cluster has been deleted, execute: ```bash kbcli dataprotection list-backups ``` Restore clusters from a specific backup. <Tabs> <TabItem value="kbcli" label="kbcli" default> ```powershell kbcli cluster restore myrestore --backup mybackup > Cluster myrestore created kbcli cluster list myrestore NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME myrestore default apecloud-mysql ac-mysql-8.0.30 Delete Running Oct 30,2023 16:26 UTC+0800 ``` </TabItem> <TabItem value="kubectl" label="kubectl"> You can set the `connectionPassword.annotations` of the restored cluster as that of the original cluster. The password of the original cluster can be accessed by viewing the annotation of `dataprotection.kubeblocks.io/connection-password` in the backup YAML file. ```bash $ kubectl apply -f - <<-'EOF' apiVersion: apps.kubeblocks.io/v1alpha1 kind: Cluster metadata: name: myrestore namespace: default annotations: kubeblocks.io/restore-from-backup: '{"mysql":{"name":"mybackup","namespace":"default","connectionPassword": "Bw1cR15mzfldc9hzGuK4m1BZQOzha6aBb1i9nlvoBdoE9to4"}}' spec: clusterDefinitionRef: apecloud-mysql clusterVersionRef: ac-mysql-8.0.30 terminationPolicy: WipeOut componentSpecs: name: mysql componentDefRef: mysql replicas: 1 volumeClaimTemplates: name: data spec: accessModes: ReadWriteOnce resources: requests: storage: 20Gi EOF ``` </TabItem> </Tabs> Connect to the restored cluster for verification. Once the cluster status is `Running`, run the following command to connect to the cluster for verification: ```bash kbcli cluster connect myrestore ```
Project: Athenz (Provisioning / Key Management)
File: system_view.md

* * * -- Before we go into the details of the authorization flow, it's important to understand the subsystems involved. The authorization (AuthZ) system shown in the figure below consists of several logical subsystems, which we will elaborate on in the following section. ZMS is the source of truth for domains, roles, and policies for centralized authorization. In addition to allowing CRUD operations on the basic entities, ZMS provides an API to replicate the entities, per domain, to ZTS. ZMS supports a centralized call to check if a principal has access to a resource both for internal management system checks, as well as a simple centralized deployment. Because ZMS supports service identities, ZMS can authenticate services. For centralized authorization, ZMS may be the only Athenz subsystem that you need to interact with. ZTS, the authentication token service, is only needed to support decentralized or data plane functionality. In many ways, ZTS is like a local replica of ZMS's data to check a principal's authentication and confirm membership in roles within a domain. The authentication is in the form of a signed ZToken that can be presented to any decentralized service that wants to authorize access efficiently. Multiple ZTS instances can be distributed to different locations as needed to scale for issuing tokens. -- SIA (Service Identity Agent) Provider is part of the container, although likely built with Athenz libraries. As services are authenticated by their private keys, the job of the SIA Provider is to generate a X509 certificate and sign it with the given private key so that the service can present that certificate to ZMS/ZTS as its identity credentials. The corresponding public key must be registered in ZMS so Athenz services can validate the signature. -- Like ZTS, ZPE, the authorization policy engine is only needed to support decentralized authorization. ZPE is the subsystem of Athenz that evaluates policies for a set of roles to yield an allowed or a denied response. ZPE is a library that your service calls and only refers to a local policy cache for your services domain (a small amount of data). Like ZTS and ZPE, ZPU is only needed to support decentralized authorization. The policy updater is the utility that retrieves from ZTS the policy files for provisioned domains on a host, which ZPE uses to evaluate access requests.
Project: BOSH (Provisioning / Automation & Configuration)
File: workstation_setup.md

We include examples using Homebrew here. Replace with your package manager of choice. You have cloned the project to $HOME/workspace/bosh You have installed Ruby `3.0.2` or later If you are not using a version manager that supports fuzzy matching in `.ruby-version` like or , note that you might have to change `.ruby-version` to include full version (e.g. change `3.2` to `3.2.2`). Bring homebrew index up-to-date `brew update` Install mysql (needed by the mysql2 gem) `brew install mysql` Setup & Start mysql (required for running integration tests with mysql) start mysql as root create mysql user: root/password i.e.: `alter user 'root'@'localhost' identified by 'password';` Install postgresql (needed by the pg gem) `brew install postgresql` Setup and Start postgresql (required for running integration tests with postgresql (default)) The server does not use any password, the authentication method should be set to `trust` for all authentication methods in `pg_hba.conf`. start postgres ``` ln -sfv /usr/local/opt/postgresql/*.plist ~/Library/LaunchAgents launchctl load ~/Library/LaunchAgents/homebrew.mxcl.postgresql.plist ``` create postgres user: $USER/\<no-password\> `createuser -U $USER --superuser postgres` create postgres database `createdb -U $USER` increase `max_connections` setting ```sh echo 'ALTER SYSTEM SET max_connections = 250' | psql brew services restart postgresql launchctl stop homebrew.mxcl.postgresql launchctl start homebrew.mxcl.postgresql ``` Get Golang dependencies Install golint `go install golang.org/x/lint/golint` Optional: Install direnv to keep your GOPATH correct when working with the bosh-agent submodule `brew install direnv` `cd <<bosh base dir>>` direnv allow Install Bundler gem `gem install bundler` Install Java 8 For certain components a java runtime is required. Currently java 8 is required, versions 9 and 10 are not supported at the moment. On MacOS you can do something like ```sh brew tap caskroom/versions brew cask install java8 export JAVAHOME=`/usr/libexec/javahome -v 1.8` ``` Bundle BOSH ```bash cd ~/workspace/bosh/src bundle install ``` If ever you hit some linker issues like _ld: library not found for -lssl_ when installing the `mysql2` Gem, try installing it manually with the following linker flags: ```bash gem install mysql2 -v '0.5.3' -- --with-ldflags="-L/usr/local/opt/openssl@1.1/lib" ``` If you ever hit "ld: library not found for -lzstd" when installing the `mysql2` gem, try the : ```bash bundle config --local build.mysql2 "--with-opt-dir="$(brew --prefix zstd)"" bundle ``` Download `bosh-agent` dependency: ``` cd ~/workspace/bosh/src bundle exec rake spec:integration:downloadboshagent ``` If you have trouble bundling, you may have to install pg gem manually by specifying your architecture: ``` (sudo) env ARCHFLAGS="-arch x86_64" gem install pg -v '0.15.1' ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.127.md

layout: release date: 2023-08-18 tag: v0.6.127 [Policies] Evaluation of OPA policies in server. @MUzairS15 (#8416) introduce pagination and search by filter name for filter list command @narharim (#8258) Change comment schema | Fix ImportModal crash in extension @Yashsharma1911 (#8514) [Server] Add server support to share WASM Filters @Chadha93 (#8274) Thank you to our contributors for making this release possible: @Chadha93, @MUzairS15, @Yashsharma1911, @leecalcote and @narharim