cwielenb/CNCF-Dataset huggingface dataset:
Project: YugabyteDB (App Definition and Development / Database)
File: commvault.md

title: Commvault linkTitle: Commvault description: Use Commvault to back up and restore your YugabyteDB database. menu: preview_integrations: identifier: commvault parent: integrations-platforms weight: 571 type: docs Commvault is a data protection and data management platform that provides an agent-based solution to support the following operations in : Data protection for YugabyteDB universes in AWS and Azure. Backup and restore of YSQL and YCQL databases. Job monitoring and manageability from the Commvault . To use Commvault with YugabyteDB, you need to configure YBA on the Commvault Command Center. For more information, refer to in the Commvault documentation.
Project: KICS (Provisioning / Security & Compliance)
File: 28a757fc-3d8f-424a-90c0-4233363b2711.md

title: PostgreSQL Misconfigured Log Messages Flag hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 28a757fc-3d8f-424a-90c0-4233363b2711 Query name: PostgreSQL Misconfigured Log Messages Flag Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: PostgreSQL database 'logminmessages' flag isn't set to a valid value<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" name: sql_instance google.cloud.gcpsqlinstance: auth_kind: serviceaccount databaseversion: SQLSERVER13_1 name: "{{ resource_name }}-2" project: test_project region: us-central1 serviceaccountfile: /tmp/auth.pem settings: database_flags: name: logminmessages value: debug6 tier: db-n1-standard-1 state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: sql_instance google.cloud.gcpsqlinstance: auth_kind: serviceaccount databaseversion: SQLSERVER13_1 name: '{{ resource_name }}-2' project: test_project region: us-central1 serviceaccountfile: /tmp/auth.pem settings: database_flags: name: logminmessages value: log tier: db-n1-standard-1 state: present ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: beam-starter-projects.md

title: "Beam starter projects" date: 2022-11-03 9:00:00 -0700 categories: blog authors: davidcavazos <!-- 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. --> We're happy to announce that we're providing new Beam starter projects! Setting up and configuring a new project can be time consuming, and varies in different languages. We hope this will make it easier for you to get started in creating new Apache Beam projects and pipelines. <!--more--> All the starter projects come in their own GitHub repository, so you can simply clone a repo and you're ready to go. Each project comes with a README with how to use it, a simple "Hello World" pipeline, and a test for the pipeline. The GitHub repositories come pre-configured with GitHub Actions to automatically run tests when pull requests are opened or modified, and Dependabot is enabled to make sure all the dependencies are up to date. This all comes out of the box, so you can start playing with your Beam pipeline without a hassle. For example, here's how to get started with Java: ``` git clone https://github.com/apache/beam-starter-java cd beam-starter-java curl -s "https://get.sdkman.io" | bash sdk install java 11.0.12-tem sdk install gradle gradle run gradle test ``` And here's how to get started with Python: ``` git clone https://github.com/apache/beam-starter-python cd beam-starter-python python -m venv env source env/bin/activate pip install -r requirements.txt python main.py python -m unittest ``` Here are the starter projects; you can choose your favorite language: Includes both Gradle and Maven configurations. Includes a setup.py file to allow multiple files in your pipeline. Includes how to register different types of functions for ParDo. Adapted to idiomatic Kotlin Coming soon! We have updated the to use the new starter project, and we're working on updating the Python and Go quickstarts as well. We hope you find this useful. Feedback and contributions are always welcome! So feel free to create a GitHub issue, or open a Pull Request to any of the starter project repositories.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.44.md

layout: release date: 2023-01-16 tag: v0.6.44 language: en Fix wrong gRPC address in Pattern Engine @Revolyssup (#6900) Bump github.com/containerd/containerd from 1.6.6 to 1.6.12 in /scripts/component_generation @dependabot (#6894) Bump helm.sh/helm/v3 from 3.8.2 to 3.10.3 in /scripts/component_generation @dependabot (#6882) Update .nvmrc @leecalcote (#6884) improve `mesheryctl login` debug msg @ayushthe1 (#6891) Edit args parameter in restart @alphaX86 (#6892) Bump lint-staged from 12.5.0 to 13.1.0 in /ui @dependabot (#6827) Data table checkbox color change @Swarno-Coder (#6623) fix: add margin to chip @Udit-takkar (#6890) Fast Track Next.js @acald-creator (#6880) Bump lint-staged from 12.5.0 to 13.1.0 in /ui @dependabot (#6827) Bump github.com/containerd/containerd from 1.6.6 to 1.6.12 @dependabot (#6887) Bump helm.sh/helm/v3 from 3.9.4 to 3.10.3 @dependabot (#6883) Fast Track Next.js @acald-creator (#6880) [CI] Upgrade workflows to Node 18 @leecalcote (#6881) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Revolyssup, @Swarno-Coder, @Udit-takkar, @acald-creator, @alphaX86, @ayushthe1, @dependabot, @dependabot[bot], @l5io, @leecalcote, @rakshitgondwal and l5io
Project: Meshery (Provisioning / Automation & Configuration)
File: aws-node-termination-handler-2.md

layout: integration title: AWS Node Termination Handler subtitle: Collaborative and visual infrastructure as code for AWS Node Termination Handler image: /assets/img/integrations/aws-node-termination-handler-2/icons/color/aws-node-termination-handler-2-color.svg permalink: extensibility/integrations/aws-node-termination-handler-2 docURL: https://docs.meshery.io/extensibility/integrations/aws-node-termination-handler-2 description: integrations-category: Provisioning integrations-subcategory: Automation & Configuration registrant: Artifact Hub components: name: terminator colorIcon: assets/img/integrations/aws-node-termination-handler-2/components/terminator/icons/color/terminator-color.svg whiteIcon: assets/img/integrations/aws-node-termination-handler-2/components/terminator/icons/white/terminator-white.svg description: featureList: [ "Keep revision history and audit trail of all configuration changes", "Use MeshMap&lsquo;s visual designer to explore your App Mesh configuration", "Deploy Meshery on your EKS clusters for App Mesh management" ] 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: YugabyteDB (App Definition and Development / Database)
File: yba_auth.md

Authenticate yba cli Authenticate the yba cli through this command by providing the host and API Token. If non-interactive mode is set, provide the host and API Token using flags. Default for host is "http://localhost:9000" ``` yba auth [flags] ``` ``` yba auth -f -H <host> -a <api-token> ``` ``` -f, --force [Optional] Bypass the prompt for non-interactive usage. Provide the host (--host/-H) and API token (--apiToken/-a) using flags -h, --help help for auth ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - yba - Command line tools to manage your YugabyteDB Anywhere (Self-managed Database-as-a-Service) resources.
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v1.4.2.md

Sidecar-injector.dapr.io was blocking Pod admissions if sidecar could not be injected (https://github.com/dapr/dapr/issues/3709) When creating a new Pod where `sidecar-injector.dapr.io` cannot inject the Dapr sidecar, an error is thrown and the Pod cannot be created. This issue was surfaced in #3709 and #3699, although 1.4.1 fixes the issue in #3699 by allowing the Dapr sidecar to be injected. For example, deploying with Tekton CICD would display the following error with this bug. ``` lastTransitionTime: '2021-09-24T07:48:19Z' message: >- failed to create task run pod "function-sample-builder-cgmn8-buildrun-nfkb8-nlbjs": admission webhook "sidecar-injector.dapr.io" denied the request: service account 'system:serviceaccount:tekton-pipelines:tekton-pipelines-controller' not on the list of allowed controller accounts. Maybe invalid TaskSpec reason: CouldntGetTask status: 'False' type: Succeeded ```
Project: KICS (Provisioning / Security & Compliance)
File: 9ef08939-ea40-489c-8851-667870b2ef50.md

title: ROS Stack Notifications Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9ef08939-ea40-489c-8851-667870b2ef50 Query name: ROS Stack Notifications Disabled Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: The ROS Stack Notifications should be defined and populated to receive stack related events<br> ```tf title="Positive test num. 1 - tf file" hl_lines="3" resource "alicloudrosstack" "example" { stack_name = "tf-testaccstack" notification_urls = [] template_body = <<EOF { "ROSTemplateFormatVersion": "2015-09-01" } EOF stackpolicybody = <<EOF { "Statement": [{ "Action": "Update:Delete", "Resource": "*", "Effect": "Allow", "Principal": "*" }] } EOF } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "alicloudrosstack" "example" { stack_name = "tf-testaccstack" template_body = <<EOF { "ROSTemplateFormatVersion": "2015-09-01" } EOF stackpolicybody = <<EOF { "Statement": [{ "Action": "Update:Delete", "Resource": "*", "Effect": "Allow", "Principal": "*" }] } EOF } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudrosstack" "example" { stack_name = "tf-testaccstack" notification_urls = ["oss://ros/stack-notification/demo"] template_body = <<EOF { "ROSTemplateFormatVersion": "2015-09-01" } EOF stackpolicybody = <<EOF { "Statement": [{ "Action": "Update:Delete", "Resource": "*", "Effect": "Allow", "Principal": "*" }] } EOF } ```
Project: CloudNativePG (App Definition and Development / Database)
File: wal_archiving.md

WAL archiving is the process that feeds a in CloudNativePG. !!! Important CloudNativePG currently only supports WAL archives on object stores. Such WAL archives serve for both object store backups and volume snapshot backups. The WAL archive is defined in the `.spec.backup.barmanObjectStore` stanza of a `Cluster` resource. Please proceed with the same instructions you find in the to set up the WAL archive. !!! Info Please refer to in the API reference for a full list of options. If required, you can choose to compress WAL files as soon as they are uploaded and/or encrypt them: ```yaml apiVersion: postgresql.cnpg.io/v1 kind: Cluster [...] spec: backup: barmanObjectStore: [...] wal: compression: gzip encryption: AES256 ``` You can configure the encryption directly in your bucket, and the operator will use it unless you override it in the cluster configuration. PostgreSQL implements a sequential archiving scheme, where the `archive_command` will be executed sequentially for every WAL segment to be archived. !!! Important By default, CloudNativePG sets `archive_timeout` to `5min`, ensuring that WAL files, even in case of low workloads, are closed and archived at least every 5 minutes, providing a deterministic time-based value for your Recovery Point Objective (RPO). Even though you change the value of the , our experience suggests that the default value set by the operator is suitable for most use cases. When the bandwidth between the PostgreSQL instance and the object store allows archiving more than one WAL file in parallel, you can use the parallel WAL archiving feature of the instance manager like in the following example: ```yaml apiVersion: postgresql.cnpg.io/v1 kind: Cluster [...] spec: backup: barmanObjectStore: [...] wal: compression: gzip maxParallel: 8 encryption: AES256 ``` In the previous example, the instance manager optimizes the WAL archiving process by archiving in parallel at most eight ready WALs, including the one requested by PostgreSQL. When PostgreSQL will request the archiving of a WAL that has already been archived by the instance manager as an optimization, that archival request will be just dismissed with a positive status.
Project: ClickHouse (App Definition and Development / Database)
File: v22.9.4.32-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : - Choose correct aggregation method for LowCardinality with BigInt. (). Backported in : Update cctz to the latest master, update tzdb to 2020e. (). Backported in : Update tzdata to 2022e to support the new timezone changes. Palestine transitions are now Saturdays at 02:00. Simplify three Ukraine zones into one. Jordan and Syria switch from +02/+03 with DST to year-round +03. (https://data.iana.org/time-zones/tzdb/NEWS). This closes . (). Backported in : Fixed "Part ... intersects part ..." error that might happen in extremely rare cases if replica was restarted just after detaching some part as broken. (). Backported in : Don't allow to create or alter merge tree tables with virtual column name rowexists, which is reserved for lightweight delete. Fixed . (). Backported in : Fix reusing of files > 4GB from base backup. (). Backported in : Fix a bug with projections and the `aggregatefunctionsnullforempty` setting. This bug is very rare and appears only if you enable the `aggregatefunctionsnullforempty` setting in the server's config. This closes . (). Backported in : `ALTER UPDATE` of attached part (with columns different from table schema) could create an invalid `columns.txt` metadata on disk. Reading from such part could fail with errors or return invalid data. Fixes . (). Backported in : Setting `additionaltablefilters` were not applied to `Distributed` storage. Fixes . (). Backported in : This reverts which introduced a regression in date/time functions. (). Backported in : Fix buffer overflow in the processing of Decimal data types. This closes . (). Backported in : This closes . (). Add a warning message to release.py script, require release type (). Revert ().
Project: Harbor (Provisioning / Container Registry)
File: 7-12-Endpoints-endpoints-add.md

Test 7-12 Endpoints endpoints add ======= To verify admin user can add an endpoint User guide This test requires at least two Harbor instance is running and available. Login UI as admin user. In `Administration->Registries` page, add an endpoint with valid URL(HTTP), username and password, click test connection to test connection and save the endpoint. In `Administration->Registries` page, add an endpoint with invalid URL(HTTP), username or password, click test connection to test connection and save the endpoint. In `Administration->Registries` page, add an endpoint with valid URL(HTTPS with self-signed certificate), username and password, select the `Verify Remote Cert` checkbox and click test connection to test connection and save the endpoint. In `Administration->Registries` page, add an endpoint with valid URL(HTTPS with self-signed certificate), username and password, uncheck the `Verify Remote Cert` checkbox and click test connection to test connection and save the endpoint. In step2 if endpoint is alive,test connection will successful, endpoint will add success. In step3 test connection will fail, endpoint will add success. In step4 test connection will fail, endpoint will add success. In step5 if endpoint is alive,test connection will successful, endpoint will add success. None
Project: Druid (App Definition and Development / Database)
File: licensing.md

title: License layout: simple_page canonical: 'https://druid.apache.org/licensing' <!-- 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. --> Edit this page in the repo. To see your changes, navigate to them from the .
Project: StarRocks (App Definition and Development / Database)
File: last_query_id.md

displayed_sidebar: "English" Obtains the ID of the most recently executed query in the current session. ```Haskell VARCHAR lastqueryid(); ``` None Returns a value of the VARCHAR type. ```Plain Text mysql> select lastqueryid(); +--+ | lastqueryid() | +--+ | 7c1d8d68-bbec-11ec-af65-00163e1e238f | +--+ 1 row in set (0.00 sec) ``` LASTQUERYID
Project: Apache Hadoop (App Definition and Development / Database)
File: Concepts.md

<! 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. See accompanying LICENSE file. --> This document describes some key concepts and features that makes YARN as a first-class platform in order to natively support long running services on YARN. A container orchestration framework is implemented to help deploying services on YARN. In a nutshell, the framework is an ApplicationMaster that requests containers from ResourceManager based on service definition provided by the user and launch the containers across the cluster adhering to placement policies. It also does all the heavy lifting work such as resolving the service definition and configurations, managing component life cycles such as automatically restarting failed containers, monitoring components' healthiness and readiness, ensuring dependency start order across components, flexing up/down components, upgrading components etc. The end goal of the framework is to make sure the service is up and running as the state that user desired. In addition, it leverages a lot of features in YARN core to accomplish scheduling constraints, such as affinity and anti-affinity scheduling, log aggregation for services, automatically restart a container if it fails, and do in-place upgrade of a container. A restful API server is developed to allow users to deploy/manage their services on YARN via a simple JSON spec. This avoids users from dealing with the low-level APIs, writing complex code to bring their services onto YARN. The REST layer acts as a unified REST based entry for creation and lifecycle management of YARN services. Services here can range from simple single-component apps to the most complex, multi-component applications needing special orchestration needs. Please refer to this for detailed API documentations. The API-server is stateless, which means users can simply spin up multiple instances, and have a load balancer fronting them to support HA, distribute the load etc. A DNS server is implemented to enable discovering services on YARN via the standard mechanism: DNS lookup. The framework posts container information such as hostname and ip into the . And the DNS server essentially exposes the information in YARN service registry by translating them into DNS records such as A record and SRV record. Clients can then discover the IPs of containers via standard DNS lookup. The previous read mechanisms of YARN Service Registry were limited to a registry specific (java) API and a REST interface and are difficult to wireup existing clients and services. The DNS based service discovery eliminates this gap. Please refer to this for more details.
Project: Pulsar (App Definition and Development / Streaming & Messaging)
File: pip-277.md

After configuring the geo-replication on Pulsar clusters, the `clusters list` API will return multiple clusters, including the local Pulsar cluster and remote clusters like ``` bin/pulsar-admin clusters list us-west us-east us-cent ``` But in this return, you can't distinguish the local and the remote cluster. When you need to remove the geo-replication configuration, it will be hard to decide which cluster should be removed on replicated tenants and namespaces unless you record the cluster information. Add `--current` option to the cluster list cmd and mark the current cluster with `(*)` ``` bin/pulsar-admin clusters list --current us-west(*) us-east us-cent ``` Add `--current` option to the cluster list cmd ``` @Parameter(names = { "-c", "--current" }, description = "Print the current cluster with (*)", required = false) private boolean current = false; ``` ``` void run() throws PulsarAdminException { java.util.List<String> clusters = getAdmin().clusters().getClusters(); String clusterName = getAdmin().brokers().getRuntimeConfigurations().get("clusterName"); List<String> result = clusters.stream().map(c ->c.equals(clusterName) ? (current ? c + "(*)" : c) : c).collect(Collectors.toList()); print(result); } ``` <!-- Updated afterwards --> Mailing List discussion thread: https://lists.apache.org/thread/800r6ld5wg7bttbywmk38m1qx12hs6nl Mailing List voting thread: https://lists.apache.org/thread/rqn3rd3c4hj11o3b12ygopmztj2yy7pv
Project: ArangoDB (App Definition and Development / Database)
File: outcome_operator_in.md

+++ title = "`std::istream &operator>>(std::istream &, basic_outcome<T, EC, EP, NoValuePolicy> &)`" description = "Deserialises a `basic_outcome` from a `std::istream`." +++ Deserialises a `basic_outcome` from a `std::istream`. Serialisation format is: ``` <unsigned int flags><space><valuetype if set and not void><errortype if set and not void><exception_type if set and not void> ``` Overridable: Not overridable. Requires: That `operator>>` is a valid expression for `std::istream` and `T`, `EC` and `EP`. Namespace: `BOOSTOUTCOMEV2_NAMESPACE` Header: `<boost/outcome/iostream_support.hpp>` (must be explicitly included manually).