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

displayed_sidebar: "English" This function compares two strings. Returns 0 if lhs and rhs compare equal. Return -1 if lhs appears before rhs in lexicographical order. Returns 1 if lhs appears after rhs in lexicographical order. When the argument is NULL, the result is NULL. ```Haskell INT strcmp(VARCHAR lhs, VARCHAR rhs) ``` ```Plain Text mysql> select strcmp("test1", "test1"); +--+ | strcmp('test1', 'test1') | +--+ | 0 | +--+ mysql> select strcmp("test1", "test2"); +--+ | strcmp('test1', 'test2') | +--+ | -1 | +--+ mysql> select strcmp("test2", "test1"); +--+ | strcmp('test2', 'test1') | +--+ | 1 | +--+ mysql> select strcmp("test1", NULL); +--+ | strcmp('test1', NULL) | +--+ | NULL | +--+ ``` STRCMP
Project: Meshery (Provisioning / Automation & Configuration)
File: kyverno-monitor.md

layout: integration title: Kyverno Monitor subtitle: Collaborative and visual infrastructure as code for Kyverno Monitor image: /assets/img/integrations/kyverno-monitor/icons/color/kyverno-monitor-color.svg permalink: extensibility/integrations/kyverno-monitor docURL: https://docs.meshery.io/extensibility/integrations/kyverno-monitor description: integrations-category: Provisioning integrations-subcategory: Security & Compliance registrant: Artifact Hub components: name: kyverno-monitor colorIcon: assets/img/integrations/kyverno-monitor/components/kyverno-monitor/icons/color/kyverno-monitor-color.svg whiteIcon: assets/img/integrations/kyverno-monitor/components/kyverno-monitor/icons/white/kyverno-monitor-white.svg description: featureList: [ "Use Meshery&ldquos GitHub Actions to test policies and validate resources without need for the Kyverno CLI.", "Use Meshery with Kyverno to inspect image metadata and match resources using label selectors and wildcards.", "Report Kyverno policy violations alongside your existing Meshery policy reports. " ] howItWorks: "Block non-conformant resources" howItWorksDetails: "Using MeshMap, apply best practice design templates for admission control over non-conformant resources." language: en list: include type: extensibility category: integrations
Project: OpenYurt (Provisioning / Automation & Configuration)
File: 00_openyurt-glossary.md

This document lists terms for the OpenYurt implementation. | | | | The node that runs on the cloud. The control-plane and other cluster management components are usually running on the CloudNode. The node that is accessible to the edge device. The EdgeNodes are usually located in a sub-optimal network environment. They may be disconnected from the cloud node at any time. Represents a user of the OpenYurt cluster. The CRD represents a pool of edge nodes in the same network region. The CRD defines the way of deploying homogeneous workloads with different versions/configurations by NodePools. Controller Manager for OpenYurt like Kube Controller Manager for K8s, and include nodelifecycle controller at present, more controllers will be added in the future. A reverse proxy and cache response on local disk. When cloud-edge network is normal, forward the requests from edge to cloud, and when cloud-edge network is disconnected, the local cache is returned to edge client. The network tunnel helps CloudNodes to send HTTP requests to EdgeNodes located in an isolated network. The server of the YurtTunnel runs on each CloudNode and redirects HTTP requests to corresponding agents. The agent of the YurtTunnel that runs on each EdgeNode receives requests from the YurtTunnel Server and sends requests to destination hosts. The controller manager includes the NodePool Controller and the UnitedDeployment Controller.
Project: YugabyteDB (App Definition and Development / Database)
File: install-software.md

title: Install YugabyteDB software headerTitle: Install software linkTitle: 2. Install software description: Download and install YugabyteDB software to each node menu: v2.18: identifier: deploy-manual-deployment-install-software parent: deploy-manual-deployment weight: 612 type: docs Installing YugabyteDB involves completing prerequisites and downloading the YugabyteDB package. {{% readfile "/preview/quick-start/include-prerequisites-linux.md" %}} YugabyteDB supports both x86 and ARM (aarch64) CPU architectures. Download packages ending in `x86_64.tar.gz` to run on x86, and packages ending in `aarch64.tar.gz` to run on ARM. The following instructions are for downloading the STS (standard-term support) release of YugabyteDB, which is recommended for production deployments. For other versions, see . Download YugabyteDB as follows: Download the YugabyteDB package using one of the following `wget` commands: ```sh wget https://downloads.yugabyte.com/releases/{{< yb-version version="v2.18">}}/yugabyte-{{< yb-version version="v2.18" format="build">}}-linux-x86_64.tar.gz ``` Or: ```sh wget https://downloads.yugabyte.com/releases/{{< yb-version version="v2.18">}}/yugabyte-{{< yb-version version="v2.18" format="build">}}-el8-aarch64.tar.gz ``` Extract the package and then change directories to the YugabyteDB home. ```sh tar xvfz yugabyte-{{< yb-version version="v2.18" format="build">}}-linux-x86_64.tar.gz && cd yugabyte-{{< yb-version version="v2.18">}}/ ``` Or: ```sh tar xvfz yugabyte-{{< yb-version version="v2.18" format="build">}}-el8-aarch64.tar.gz && cd yugabyte-{{< yb-version version="v2.18">}}/ ``` To configure YugabyteDB, run the following shell script: ```sh ./bin/post_install.sh ```
Project: ORY Hydra (Provisioning / Key Management)
File: TokenPagination.md

Name | Type | Description | Notes | - | - | - PageSize | Pointer to int64 | Items per page This is the number of items per page to return. For details on pagination please head over to the . | [optional] [default to 250] PageToken | Pointer to string | Next Page Token The next page token. For details on pagination please head over to the . | [optional] [default to "1"] `func NewTokenPagination() *TokenPagination` NewTokenPagination instantiates a new TokenPagination object This constructor will assign default values to properties that have it defined, and makes sure properties required by API are set, but the set of arguments will change when the set of required properties is changed `func NewTokenPaginationWithDefaults() *TokenPagination` NewTokenPaginationWithDefaults instantiates a new TokenPagination object This constructor will only assign default values to properties that have it defined, but it doesn't guarantee that properties required by API are set `func (o *TokenPagination) GetPageSize() int64` GetPageSize returns the PageSize field if non-nil, zero value otherwise. `func (o TokenPagination) GetPageSizeOk() (int64, bool)` GetPageSizeOk returns a tuple with the PageSize field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *TokenPagination) SetPageSize(v int64)` SetPageSize sets PageSize field to given value. `func (o *TokenPagination) HasPageSize() bool` HasPageSize returns a boolean if a field has been set. `func (o *TokenPagination) GetPageToken() string` GetPageToken returns the PageToken field if non-nil, zero value otherwise. `func (o TokenPagination) GetPageTokenOk() (string, bool)` GetPageTokenOk returns a tuple with the PageToken field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *TokenPagination) SetPageToken(v string)` SetPageToken sets PageToken field to given value. `func (o *TokenPagination) HasPageToken() bool` HasPageToken returns a boolean if a field has been set.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_dataprotection_list-backup-policy.md

title: kbcli dataprotection list-backup-policy List backup policies ``` kbcli dataprotection list-backup-policy [flags] ``` ``` kbcli cluster list-backup-policy kbcli cluster list-backup-policy mypolicy kbcli cluster list-backup-policy --cluster mycluster ``` ``` -A, --all-namespaces If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace. --cluster string The cluster name -h, --help help for list-backup-policy -o, --output format prints the output in the specified format. Allowed values: table, json, yaml, wide (default table) -l, --selector string Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. --show-labels When printing, show all labels as the last column (default hide labels column) ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Data protection command.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.7.23.md

RabbitMQ `3.7.23` is a maintenance release. RabbitMQ `3.7.x` series is supported . Per the new Erlang version support policy in effect starting with January 2019, this release . Make sure a is used before upgrading. explains what package repositories and tools can be used to provision latest patch versions of Erlang `21.3.x` and `22.x`. When upgrading to this release and upgrading Erlang to 21.x or later at the same time, extra care has to be taken. Since CLI tools from RabbitMQ releases older than 3.7.7 will fail on Erlang 21 or later, RabbitMQ must be upgraded before Erlang. See upgrade and compatibility notes first if upgrading from an earlier release. See the for general documentation on upgrades and for release notes of other releases. Any questions about this release, upgrades or RabbitMQ in general are welcome on the . Throughput improvements ranging from 14 to 60 percent depending on workload. GitHub issue: Throughput improvements. GitHub issue: Throughput improvements. GitHub issue: Clients now can authenticate using an x.509 (TLS) certificate. GitHub issue: Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-server-3.7.23.tar.xz`.
Project: YugabyteDB (App Definition and Development / Database)
File: gke.md

title: Deploy YugabyteDB in Google Cloud Platform with Google Kubernetes Engine (GKE) headerTitle: Google Cloud Platform linkTitle: Google Cloud Platform description: Use Google Kubernetes Engine (GKE) to deploy a YugabyteDB cluster in Google Cloud Platform. menu: v2.18: identifier: deploy-in-gcp-2-gke parent: public-clouds weight: 640 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="../gcp-deployment-manager/" class="nav-link"> <i class="icon-shell"></i> Google Cloud Deployment Manager </a> </li> <li> <a href="../gke/" class="nav-link active"> <i class="fa-regular fa-dharmachakra" aria-hidden="true"></i> Google Kubernetes Engine (GKE) </a> </li> <li > <a href="../terraform/" class="nav-link"> <i class="icon-shell"></i> Terraform </a> </li> </ul> Refer to the instructions in the Kubernetes section.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.2.md

RabbitMQ `3.9.2` is a maintenance release in the `3.9.x` release series. . Please refer to the Upgrading to 3.9 section from if you are upgrading from a version prior to 3.9.0. This release requires at least Erlang 23.2, and supports the latest Erlang 24 version, 24.0.5 at the time of release. has more details on Erlang version requirements for RabbitMQ. Release notes are kept under . Contributors are encouraged to update them together with their changes. This helps with release automation and more consistent release schedule. `rabbitmq-upgrade drain` and `rabbitmq-upgrade revive` now log `warning` and `info` level instead of `alert`. GitHub issue: Multiple Shovels could be started in some cases involving node restarts of failures. GitHub issue: Multiple Federation links could be started in some cases involving node restarts of failures. GitHub issue: Osiris has been To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.2.tar.xz` instead of the source tarball produced by GitHub.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-ddl-usedb.md

layout: global title: USE Database displayTitle: USE Database 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. `USE` statement is used to set the current database. After the current database is set, the unqualified database artifacts such as tables, functions and views that are referenced by SQLs are resolved from the current database. The default database name is 'default'. ```sql USE database_name ``` database_name* Name of the database will be used. If the database does not exist, an exception will be thrown. ```sql -- Use the 'userdb' which exists. USE userdb; -- Use the 'userdb1' which doesn't exist USE userdb1; Error: org.apache.spark.sql.catalyst.analysis.NoSuchDatabaseException: Database 'userdb1' not found; (state=,code=0) ```
Project: KubeCarrier (App Definition and Development / Application Definition & Image Build)
File: CONTRIBUTING.md

Loodse projects are and accept contributions via GitHub pull requests. This document outlines some of the conventions on development workflow, commit message formatting, contact points and other resources to make it easier to get your contribution accepted. By contributing to this project you agree to the Developer Certificate of Origin (DCO). This document was created by the Linux Kernel community and is a simple statement that you, as a contributor, have the legal right to make the contribution. See the file for details. Any copyright notices in this repo should specify the authors as "the KubeCarrier project contributors". To sign your work, just add a line like this at the end of your commit message: ``` Signed-off-by: Joe Example <joe@example.com> ``` This can easily be done with the `--signoff` option to `git commit`. By doing this you state that you can certify the following (from https://developercertificate.org/): The KubeCarrier project currently uses the general Loodse email list and Slack channel: Email: Slack: # on Slack Please avoid emailing maintainers directly. They are very busy and read the mailing lists. Due to their public nature, GitHub and mailing lists are not appropriate places for reporting vulnerabilities. If you suspect you have found a security vulnerability in rkt, please do not file a GitHub issue, but instead email security@loodse.com with the full details, including steps to reproduce the issue. Fork the repository on GitHub Read the for build and test instructions Play with the project, submit bugs, submit patches! This is a rough outline of what a contributor's workflow looks like: Create a topic branch from where you want to base your work (usually master). Make commits of logical units. Make sure your commit messages are in the proper format (see below). Push your changes to a topic branch in your fork of the repository. Make sure the tests pass, and add any new tests as appropriate. Submit a pull request to the original repository. Thanks for your contributions!
Project: Beam (App Definition and Development / Streaming & Messaging)
File: batchelements.md

title: "BatchElements" <!-- 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. --> {{< localstorage language language-py >}} {{< button-pydoc path="apache_beam.transforms.stat" class="BatchElements" >}} {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHON_BatchElements" show="batchelements" >}} {{< /playground >}} batches elements by key
Project: external-secrets (Provisioning / Security & Compliance)
File: oracle-vault.md

External Secrets Operator integrates with to sync secret on the Oracle Vault to secrets held on the Kubernetes cluster. Specify the authenticating principal with `principalType`, using `UserPrincipal`, `InstancePrincipal`, or `Workload` as values. If `principalType` or `auth` are not set, the operator defaults to instance principal for authentication. For user principal, userOCID, tenancyOCID, fingerprint and private key are required. The fingerprint and key file should be supplied in the secret with the rest being provided in the secret store. See url for what region you you are accessing. Select tenancy in the top right to see your user OCID as shown below. Select your user in the top right to see your user OCID as shown below. Create a secret containing your private key and fingerprint: ```yaml {% include 'oracle-credentials-secret.yaml' %} ``` Your fingerprint will be attatched to your API key, once it has been generated. Found on the same page as the user OCID. Once you click "Add API Key" you will be shown the following, where you can download the RSA key in the necessary PEM format for API requests. This will automatically generate a fingerprint. Be sure the `oracle` provider is listed in the `Kind=SecretStore`. ```yaml {% include 'oracle-secret-store.yaml' %} ``` NOTE: In case of a `ClusterSecretStore`, Be sure to provide `namespace` in `privatekey` and `fingerprint` with the namespaces where the secrets reside. To create a kubernetes secret from the Oracle Cloud Interface secret a`Kind=ExternalSecret` is needed. ```yaml {% include 'oracle-external-secret.yaml' %} ``` The operator will fetch the project variable and inject it as a `Kind=Secret`. ``` kubectl get secret oracle-secret-to-create -o jsonpath='{.data.dev-secret-test}' | base64 -d ``` When using , the compartment OCID and encryption key OCID must be specified in the Oracle SecretStore. You can find your compartment and encrpytion key OCIDs in the OCI console. If by tag or regex, only the compartment OCID must be specified. ```yaml {% include 'oracle-secret-store-pushsecret.yaml' %} ```
Project: YugabyteDB (App Definition and Development / Database)
File: shared-responsibility.md

title: Shared responsibility model linkTitle: Shared responsibility model description: Explore the the security shared responsiblity model of the YugabyteDB Managed database. menu: preview_yugabyte-cloud: parent: cloud-security identifier: shared-responsibility weight: 20 type: docs YugabyteDB Managed security and compliance is a shared responsibility between public cloud providers, Yugabyte, and YugabyteDB Managed customers. Under the shared responsibility model, there is a division of responsibility for the security aspects of YugabyteDB Managed, which includes but is not limited to network controls, data classification, application controls, identity and access management, and more. The responsibilities for each workload and feature depend on where the workload is hosted - Software as a Service (SaaS), Platform as a Service (PaaS), Infrastructure as a Service (IaaS), or on-premises in your own data center. You are responsible for reviewing YugabyteDB Managed security capabilities and features in accordance with your compliance and regulatory requirements to determine whether your data can be stored in YugabyteDB Managed. You are also responsible for the security, protection, and backup of your data as far as this is possible in the shared responsibility model, as well as for configuring YugabyteDB Managed security and product features to the extent that Yugabyte makes it possible. Yugabyte leverages public cloud provider PaaS and SaaS offerings to deliver the YugabyteDB Managed service. Under the shared responsibility model, the public cloud providers are responsible for providing and protecting the infrastructure (the hardware, software, networking, and facilities) that runs the cloud services Yugabyte provides in YugabyteDB Managed. Configuration related to infrastructure managed and operated by the public cloud providers is generally not available for Yugabyte customers to audit or modify in YugabyteDB Managed. Yugabyte implements the technical and organizational security measures as described in the .
Project: YugabyteDB (App Definition and Development / Database)
File: type_money.md

title: Money data types [YSQL] headerTitle: Money data types linkTitle: Money description: The MONEY data type represents currency with a fixed precision for fraction. menu: v2.18: identifier: api-ysql-datatypes-money parent: api-ysql-datatypes type: docs The `MONEY` data type represents currency with a fixed precision for fraction. Data type | Description | Min | Max | -|-|--|--| MONEY | 8 bytes | -92233720368547758.08 | +92233720368547758.07 | ```ebnf type_specification ::= MONEY ``` To avoid precision loss, `MONEY` value can be cast to `NUMERIC` type before applying calculations.