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

Authenticate yba cli using email and password Connect to YugabyteDB Anywhere host machine using email and password. If non-interactive mode is set, provide the host, email and password using flags. Default for host is "http://localhost:9000" ``` yba login [flags] ``` ``` yba login -f -e <email> -p <password> -H <host> ``` ``` -e, --email string [Optional] Email or username for the user. Required for non-interactive usage. -p, --password string [Optional] Password for the user. Required for non-interactive usage. Use single quotes ('') to provide values with special characters. -f, --force [Optional] Bypass the prompt for non-interactive usage. -h, --help help for login ``` ``` -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: Lagoon (App Definition and Development / Application Definition & Image Build)
File: lagoon-cli.md

Check on how to install for your operating system. For macOS and Linux, you can use Homebrew: `brew tap uselagoon/lagoon-cli` `brew install lagoon` The CLI needs to know how to communicate with Lagoon, so run the following command: ```bash title="Lagoon config" lagoon config add \ --graphql https://YOUR-API-URL/graphql \ --ui https://YOUR-UI-URL \ --hostname YOUR.SSH.IP \ --lagoon YOUR-LAGOON-NAME \ --port 22 ``` Access Lagoon by authenticating with your SSH key. In the Lagoon UI (the URL is in `values.yml` if you forget), go to Settings. Add your public SSH key. You need to set the default Lagoon to your Lagoon so that it doesnt try to use the amazee.io defaults: ```bash title="Lagoon config" lagoon config default --lagoon <YOUR-LAGOON-NAME> ``` Now run `lagoon login`. Lagoon talks to SSH and authenticates against your public/private key pair, and gets a token for your username. Verify via `lagoon whoami` that you are logged in. !!! Info We dont generally recommend using the Lagoon Admin role, but youll need to create an admin account at first to get started. Ideally, youll immediately create another account to work from which is not an admin.
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_create_rule.md

title: CREATE RULE statement [YSQL] headerTitle: CREATE RULE linkTitle: CREATE RULE description: Use the CREATE RULE statement to create a rule. menu: v2.18: identifier: ddlcreaterule parent: statements type: docs Use the `CREATE RULE` statement to create a rule. {{%ebnf%}} create_rule, rule_event, command {{%/ebnf%}} See the semantics of each option in the . Basic example. ```plpgsql yugabyte=# CREATE TABLE t1(a int4, b int4); yugabyte=# CREATE TABLE t2(a int4, b int4); yugabyte=# CREATE RULE t1tot2 AS ON INSERT TO t1 DO INSTEAD INSERT INTO t2 VALUES (new.a, new.b); yugabyte=# INSERT INTO t1 VALUES (3, 4); yugabyte=# SELECT * FROM t1; ``` ``` a | b (0 rows) ``` ```plpgsql yugabyte=# SELECT * FROM t2; ``` ``` a | b 3 | 4 (1 row) ```
Project: secureCodeBox (Provisioning / Security & Compliance)
File: chart.yaml.md

title: Chart.yaml sidebar_position: 1 The `Chart.yaml` is a basic description of your scanner helm chart and will look something like the following: ```yaml apiVersion: v2 name: new-scanner description: A Helm chart for Kubernetes type: application version: 0.1.0 appVersion: 1.16.0 ``` The `apiVersion` sets the used Chart API version of Helm. You won't have to change this field. The `name` field should be set to the name of the scanner. You won't have to change this field. Please change the `description` field to explain the basic purpose of your scanner. For WPScan the `description` would be: ```yaml description: A Helm chart for the WordPress security scanner that integrates with the secureCodeBox. ``` The fields for `version` will be set automatically by our release process. The `appVersion` should be set to the Version of the scanner. If the scanner does not use versions please use `latest`. Please set both values: ```yaml version: latest appVersion: latest ``` The `kubeVersion` references the version of kubernetes that is required to run your Helm Chart. Please add `kubeVersion` with the value `">=v1.11.0-0"` ```yaml kubeVersion: ">=v1.11.0-0" ``` The `keywords` field makes it possible to specify a list of keywords about this project. For the WPScan `keywords` would look the following: ```yaml keywords: security wpscan wordpress scanner secureCodeBox ``` The `home` field should be set to the home page of the project. For WPScan this would be: ```yaml home: https://www.securecodebox.io/docs/scanners/WPScan ``` The `icon` field should be set to the URL to a SVG or PNG (if existing). For WPScan `icon` would look the following: ```yaml icon: https://www.securecodebox.io/img/integrationIcons/WPScan.svg ``` The `sources` field should be set the the URL of the secureCodeBox repository: ```yaml sources: https://github.com/secureCodeBox/secureCodeBox ``` The `maintainers` field should contain the following values: ```yaml maintainers: name: iteratec GmbH email: secureCodeBox@iteratec.com ```
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: CHANGELOG-v2023.02.28.md

title: Changelog | KubeDB description: Changelog menu: docs_{{.version}}: identifier: changelog-kubedb-v2023.02.28 name: Changelog-v2023.02.28 parent: welcome weight: 20230228 product_name: kubedb menuname: docs{{.version}} sectionmenuid: welcome url: /docs/{{.version}}/welcome/changelog-v2023.02.28/ aliases: /docs/{{.version}}/CHANGELOG-v2023.02.28/ Add WsrepSSTMethod Field in MariaDB API (#1012) Update `setDefaults()` for pgbouncer (#1022) Add separate Security Config Directory constant for Opensearch V2 (#1021) Update TLS Defaulting for ProxySQL & PgBouncer (#1020) Fix `GetPersistentSecrets()` function (#1018) Add postgres streaming and standby mode in horizontal scaling (#1017) Prepare for release v0.17.0 (#136) Prepare for release v0.32.0 (#698) Prepare for release v0.8.0 (#64) Add support for opensearch-dashboards 2.x (#63) Prepare for release v0.32.0 (#629) Use separate securityConfig Volume mount path for Opensearch V2 (#627) Prepare for release v2023.02.28 (#601) Update MariaDB initContainer Image with 0.5.0 (#600) Add `SecurityContext` & remove `initContainer` from `pgbouncerVersion.spec` (#596) Add Support for OpenSearch v2.0.1 & v2.5.0 (#599) Update postgres init conatiner and rbac for pvc (#592) Update crds for kubedb/apimachinery@b334a5eb (#591) Prepare for release v0.3.0 (#15) Prepare for release v0.16.0 (#200) Add Dynamic `wsrepsstmethod` Selection Code (#193) Update sidekick dependency (#199) Prepare for release v0.12.0 (#73) Prepare for release v0.25.0 (#385) Prepare for release v0.25.0 (#535) Prepare for release v0.25.0 (#522) Prepare for release v0.10.0 (#71) Prepare for release v0.19.0 (#419) Fix ProxySQL reconfigure tls issues (#418) Add PEM encoded output in certificate based on cert-manager feature-gate (#417) Support Acme protocol issued certs for PgBouncer & ProxySQL (#415) Add support for stand Alone to HA postgres (#409) Prepare for release v0.19.0 (#300) Prepare for release v0.5.0 (#30) Prepare for release v0.16.0 (#113) Prepare for release v0.19.0 (#266) Acme TLS support (#262) Fix ownerReference for auth secret (#263) Prepare for release v0.32.0 (#629) Refactor Reconciler to address Standalone to High Availability (#625) Prepare for release v0.32.0 (#39) Prepare for release v0.19.0 (#283) Support Acme Protocol Issued Certs (eg LE) (#282) Prepare for release v0.25.0 (#450) Prepare for release v0.11.0 (#63) Prepare for release v0.19.0 (#225) Prepare for release v0.8.0 (#65) Prepare for release v0.17.0 (#217) Add MySQL tests (#198) Prepare for release v0.8.0 (#68) Prepare for release v0.8.0 (#52)
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.4.23.md

layout: release date: 2020-11-19 tag: v0.4.23 Add redirectErrorToConsole method to let mesh sync call fail silently @utkarsh-pro (#1949) Utkarsh pro/meshery/kubernetes service scan @utkarsh-pro (#1928) fix: golangci-lint failures @kushthedude (#1945) All releases between v0.4.22 and v0.4.4 added @ezioishan (#1943) [UI] External Link Icon @Sudhish2101 (#1913) Update mui-datatables to 3.7.1 @ramrodo (#1925) Rename name column to "control plane pods" and add tooltip with fullname @utkarsh-pro (#1924) Proposal for replacing kubescan with new implementation @utkarsh-pro (#1923) Fix eslint error for "TemplateLiteral" and fix package-lock.json for billboard.js @ramrodo (#1921) Bump eslint from 7.6.0 to 7.13.0 in /ui @dependabot-preview (#1935) Bump react-jss from 10.4.0 to 10.5.0 in /ui @dependabot-preview (#1941) Bump jss from 10.4.0 to 10.5.0 in /provider-ui @dependabot-preview (#1930) Bump cypress from 5.5.0 to 5.6.0 in /provider-ui @dependabot-preview (#1931)
Project: ArangoDB (App Definition and Development / Database)
File: equality_basic_outcome.md

+++ title = "`bool operator==(const basic_outcome<A, B, C, D> &) const`" description = "Returns true if this outcome compares equal to the other outcome. Constexpr and noexcept propagating." categories = ["comparisons"] weight = 801 +++ Returns true if this outcome compares equal to the other outcome. Comparison is done using `operator==` on `valuetype` or `errortype` and/or `exception_type` if the currently chosen state is the same for both outcomes, otherwise false is returned. Requires: `operator==` must be a valid expression between `valuetype` and `A`, and between `errortype` and `B`, and between `exceptiontype` and `C`. If `valuetype` is `void`, then so must be `A`; similarly for `errortype` and `B`; similarly for `exceptiontype` and `C`. Complexity: Whatever the underlying `operator==` have. Constexpr and noexcept of underlying operations is propagated. Guarantees: None.
Project: StarRocks (App Definition and Development / Database)
File: sin.md

displayed_sidebar: "English" Returns the sine of `x`, where `x` is in radians. ```Haskell SIN(x); ``` `x`: supports the DOUBLE data type. Returns a value of the DOUBLE data type. ```Plain mysql> select sin(3.14); +--+ | sin(3.14) | +--+ | 0.0015926529164868282 | +--+ 1 row in set (0.21 sec) ```
Project: ClickHouse (App Definition and Development / Database)
File: v23.4.4.16-stable.md

sidebar_position: 1 sidebar_label: 2023 Fix crash when Pool::Entry::disconnect() is called (). Fix iceberg V2 optional metadata parsing (). Fix subtly broken copy-on-write of ColumnLowCardinality dictionary (). Generate safe IVs (). Don't mark a part as broken on `Poco::TimeoutException` (). Fix a versions' tweak for tagged commits, improve version_helper (). Sqlancer has changed master to main ().
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref.md

layout: global title: SQL Reference redirect_from: /sql-reference displayTitle: SQL Reference 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. Spark SQL is Apache Spark's module for working with structured data. This guide is a reference for Structured Query Language (SQL) and includes syntax, semantics, keywords, and examples for common SQL usage. It contains information for the following topics: * * * * * * * * *
Project: YugabyteDB (App Definition and Development / Database)
File: amazon-aurora.md

title: Compare Amazon Aurora with YugabyteDB headerTitle: Amazon Aurora linkTitle: Amazon Aurora description: Compare Amazon Aurora with YugabyteDB. aliases: /comparisons/amazon-aurora/ menu: preview_faq: parent: comparisons identifier: comparisons-aurora weight: 1073 type: docs Generally available since 2015, Amazon Aurora is built on a proprietary distributed storage engine that automatically replicates 6 copies of data across 3 availability zones for high availability. From an API standpoint, Aurora is wire compatible with both PostgreSQL and MySQL. As described in , Aurora uses a quorum write approach based on 6 replicas. This allows for significantly better availability and durability than traditional master-slave replication. By default, Aurora runs in a single-master configuration where only a single node can process write requests and all other nodes are read replicas. If the writer node becomes unavailable, a failover mechanism promotes one of the read-only nodes to be the new writer. configuration is a recent addition to Aurora MySQL (not yet available on Aurora PostgreSQL) for scaling writes that involves a second writer node. However, because all of the data is now present in both the nodes, concurrent writes to the same data on the two nodes can lead to that the application has to handle. A long list of include the inability to scale beyond the original two writer nodes as well as lack of geo-distributed writes across multiple regions. Geo-distributed deployments in Aurora essentially involve a single primary region for handling writes and multiple other regions as read replicas. So globally-consistent multi-region deployments are not possible in Aurora. Aurora is Amazon's proprietary database that does not allow users to build cloud-neutral applications and run on cloud-neutral orchestration technologies like Kubernetes. The following posts cover some more details around how YugabyteDB differs from Amazon Aurora.
Project: Carvel (App Definition and Development / Application Definition & Image Build)
File: README_Lex.md

The following is a sample class and Lambda function that receives Amazon Lex event data as input, writes some of the record data to CloudWatch Logs, and responds back to Lex. (Note that anything written to stdout or stderr will be logged as CloudWatch Logs events.) ```go import ( "context" "fmt" "github.com/aws/aws-lambda-go/events" ) func Handler(ctx context.Context, event events.LexEvent) (*lex.LexResponse, error) { fmt.Printf("Received an input from Amazon Lex. Current Intent: %s", event.CurrentIntent.Name) messageContent := "Hello from AWS Lambda!" return &LexResponse{ SessionAttributes: event.SessionAttributes, DialogAction: events.LexDialogAction{ Type: "Close", Message: map[string]string{ "content": messageContent, "contentType": "PlainText", }, FulfillmentState: "Fulfilled", }, }, nil } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.37.md

layout: release date: 2022-12-22 tag: v0.6.37 language: en Change meshmodel relationships structure @Revolyssup (#6768) Fix panic @Revolyssup (#6766) Fix panic in main.go @Revolyssup (#6765) [Playground] Remove container registry @leecalcote (#6767) Thank you to our contributors for making this release possible: @Revolyssup and @leecalcote
Project: Trivy (Provisioning / Security & Compliance)
File: rhel.md

Trivy supports the following scanners for OS packages. | Scanner | Supported | | :--: | :-: | | SBOM | | | Vulnerability | | | License | | Please see for supported versions. The table below outlines the features offered by Trivy. | Feature | Supported | | :-: | :-: | | Unfixed vulnerabilities | | | | | Trivy detects packages that have been installed through package managers such as `dnf` and `yum`. Red Hat offers its own security advisories, and these are utilized when scanning Red Hat Enterprise Linux (RHEL) for vulnerabilities. See . When looking at fixed versions, it's crucial to consider the patches supplied by Red Hat. For example, for CVE-2023-0464, the fixed version for RHEL 9 is listed as `3.0.7-16.el9_2` in . This patch is provided in [RHSA-2023:3722]. Note that this is different from the upstream fixed version, which is `3.0.9`, `3.1.1`, and so on. Typically, only the upstream information gets listed on [NVD], so it's important not to get confused. Trivy calculates the severity of a vulnerability based on the 'Impact' metric provided by Red Hat. If the impact is not provided or defined yet by Red Hat, the severity from the NVD is taken into account. Using CVE-2023-0464 as an example, while it is rated as "HIGH" in NVD, Red Hat has marked its 'Impact' as . As a result, Trivy will display it as "Low". The table below is the mapping of Red Hat's impact to Trivy's severity levels. | Red Hat | Trivy | | :-: | :: | | Low | Low | | Moderate | Medium | | Important | High | | Critical | Critical | Trivy supports the following [vulnerability statuses] for RHEL. | Status | Supported | | :--: | :-: | | Fixed | | | Affected | | | Under Investigation | | | Will Not Fix | | | Fix Deferred | | | End of Life | | When a vulnerability status is listed as "End of Life", it means a vulnerability with the impact level assigned to this CVE is no longer covered by its current support lifecycle phase. The product has been identified to contain the impacted component, but analysis to determine whether it is affected or not by this vulnerability was not performed. Red Hat advises that the product should be assumed to be affected. Therefore, Trivy detects vulnerabilities with this status as "End of Life". On the other hand, for those marked "Under Investigation," the impact is unclear as they are still being examined, so Trivy does not detect them. Once the investigation is completed, the status should be updated. !!! abstract Vulnerabilities with a status of "End of Life", where the presence or absence of impact is unclear, are detected by Trivy. However, those with a status of "Under Investigation" are not detected. Trivy identifies licenses by examining the metadata of RPM packages.
Project: ShardingSphere (App Definition and Development / Database)
File: drop-broadcast-table-rule.en.md

+++ title = "DROP BROADCAST TABLE RULE" weight = 2 +++ The `DROP BROADCAST TABLE RULE` syntax is used to drop broadcast table rule for specified broadcast tables {{< tabs >}} {{% tab name="Grammar" %}} ```sql DropBroadcastTableRule ::= 'DROP' 'BROADCAST' 'TABLE' 'RULE' ifExists? tableName (',' tableName)* ifExists ::= 'IF' 'EXISTS' tableName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} `tableName` can use the table of existing broadcast rules; `ifExists` clause is used for avoid `Broadcast rule not exists` error. Drop broadcast table rule for specified broadcast table ```sql DROP BROADCAST TABLE RULE tprovince, tcity; ``` Drop broadcast table rule with `ifExists` clause ``` DROP BROADCAST TABLE RULE IF EXISTS tprovince, tcity; ``` `DROP`, `BROADCAST`, `TABLE`, `RULE`
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v0.11.3.md

Note: this hotfix is only required for the applications which uses Dapr actor building block. Actor load tests were run to evaluate the performance and relibility. The test discovered that cause memory leaks: Frequent reconnections to placement service when app http endpoint is unresponsive intermitently under high load scneario Memory increases from http middleware when recording request metric No RSS(Resident Set Size) memory size reclaim in Kubernetes even after actors are deactivated Regarding RSS memory size issue (bug) - Daprd stores the activated actors in a and deletes actors when these actors are deactivated. Therefore, RSS memory for Darpd containers will be increased when actor is activated, but the memory will not be decreased even after the actors are deactivated. Users will therefore still see the same amount of RSS memory usage because Go uses to free memory in linux. The memory is reclaimed only when it hits memory limit. We recommend that users consider setting `dapr.io/sidecar-memory-limit` and `dapr.io/sidecar-memory-request` to limit the size of Dapr sidecar memory usage. Please refer to to understand the memory usage of Go application. Improve actor service health check relibility to avoid unexpected placement disconnection(https://github.com/dapr/dapr/pull/2292). Do not track Actor ID for actor pending lock count metric(https://github.com/dapr/dapr/pull/2295)
Project: YugabyteDB (App Definition and Development / Database)
File: reassign_owned,role_specification.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="585" height="65" viewbox="0 0 585 65"><path class="connector" d="M0 52h15m83 0h10m67 0h10m35 0h30m-5 0q-5 0-5-5v-20q0-5 5-5h54m24 0h54q5 0 5 5v20q0 5-5 5m-5 0h30m36 0h10m122 0h15"/><polygon points="0,59 5,52 0,45" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="35" width="83" height="25" rx="7"/><text class="text" x="25" y="52">REASSIGN</text><rect class="literal" x="108" y="35" width="67" height="25" rx="7"/><text class="text" x="118" y="52">OWNED</text><rect class="literal" x="185" y="35" width="35" height="25" rx="7"/><text class="text" x="195" y="52">BY</text><rect class="literal" x="299" y="5" width="24" height="25" rx="7"/><text class="text" x="309" y="22">,</text><a xlink:href="#role-specification"><rect class="rule" x="250" y="35" width="122" height="25"/><text class="text" x="260" y="52">rolespecification</text></a><rect class="literal" x="402" y="35" width="36" height="25" rx="7"/><text class="text" x="412" y="52">TO</text><a xlink:href="#role-specification"><rect class="rule" x="448" y="35" width="122" height="25"/><text class="text" x="458" y="52">rolespecification</text></a><polygon points="581,59 585,59 585,45 581,45" style="fill:black;stroke-width:0"/></svg> <svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="188" height="95" viewbox="0 0 188 95"><path class="connector" d="M0 22h35m84 0h54m-148 25q0 5 5 5h5m118 0h5q5 0 5-5m-143-25q5 0 5 5v50q0 5 5 5h5m116 0h7q5 0 5-5v-50q0-5 5-5m5 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><a xlink:href="../../../syntaxresources/grammardiagrams#role-name"><rect class="rule" x="35" y="5" width="84" height="25"/><text class="text" x="45" y="22">rolename</text></a><rect class="literal" x="35" y="35" width="118" height="25" rx="7"/><text class="text" x="45" y="52">CURRENTUSER</text><rect class="literal" x="35" y="65" width="116" height="25" rx="7"/><text class="text" x="45" y="82">SESSION_USER</text><polygon points="184,29 188,29 188,15 184,15" style="fill:black;stroke-width:0"/></svg>
Project: StarRocks (App Definition and Development / Database)
File: UNINSTALL_PLUGIN.md

displayed_sidebar: "English" This statement is used to uninstall a plugin. :::tip This operation requires the SYSTEM-level PLUGIN privilege. You can follow the instructions in to grant this privilege. ::: ```SQL UNINSTALL PLUGIN <plugin_name> ``` plugin_name can be viewed through SHOW PLUGINS command Only non-builtin plugins can be uninstalled. Uninstall a plugin: ```SQL UNINSTALL PLUGIN auditdemo; ```