cwielenb/CNCF-Dataset huggingface dataset:
Project: CloudNativePG (App Definition and Development / Database)
File: v1.23.md

History of user-visible changes in the 1.23 minor release of CloudNativePG. For a complete list of changes, please refer to the on the release branch in GitHub. Release date: Apr 29, 2024 Fixes: Corrects the reconciliation of `PodMonitor` resources, which was failing due to a regression (#4286) Release date: Apr 24, 2024 !!! Important "Important changes to Community Supported Versions" We've updated our support policy to streamline our focus on one supported minor release at a time, rather than two. Additionally, we've extended the supplementary support period for the previous minor release to 3 months. Features: PostgreSQL Image Catalogs: Introduced `ClusterImageCatalog` and `ImageCatalog` CRDs to manage operand container images based on PostgreSQL major version. This is facilitated through the `Cluster`'s `.spec.imageCatalogRef stanza`. This feature provides an alternative to the imageName option and will eventually replace it as the default method to define operand container images. User-Defined Replication Slots: Enhanced the synchronization of physical replication slots to cover user-defined replication slots on the primary, via the newly introduced stanza `replicationSlots.synchronizeReplicas`. Configuration of Pod Disruption Budgets (PDB): Introduced the `.spec.enablePDB` field to disable PDBs on the primary instance, allowing proper eviction of the pod during maintenance operations. This is particularly useful for single-instance deployments. This feature is intended to replace the node maintenance window feature. Enhancements: Users now have the capability to transition an existing cluster into replica mode, simplifying cross-datacenter switchover operations (#4261) Users can now customize the connection pooler service, including its type, labels, and annotations (#3384) Users can now configure the `walloghints` PostgreSQL parameter (#4218) (#4218) Fully Qualified Domain Names (FQDN) in URIs for automatically generated secrets (#4095) Cleanup of instance Pods not owned by the Cluster during Cluster restore (#4141) Command output of the plugins `status` command to show the status of PDBs (#4319) Error detection when invoking `barman-cloud-wal-restore` in `recovery` bootstrap (#4101) Fixes: Ensured that before a switchover, the elected replica is in streaming replication (#4288) Correctly handle parsing errors of instances' LSN when sorting them (#4283) Recreate the primary Pod if there are no healthy standbys available to promote (#4132) Cleanup `PGDATA` in case of failure of the restore job (#4151) Reload certificates on configuration update (#3705) `cnpg` plugin for `kubectl`: Improve the arguments handling of `destroy`, `fencing`, and `promote` plugin commands (#4280) Correctly handle the percentage of the backup progress in `cnpg status` (#4131) Gracefully handle databases with no sequences in `sync-sequences` command (#4346) Changes: Operator images are now based on `gcr.io/distroless/static-debian12:nonroot` (#4201) The Grafana dashboard now resides at https://github.com/cloudnative-pg/grafana-dashboards (#4154)
Project: NebulaGraph (App Definition and Development / Database)
File: Coding_Style_Guide.md

Currently we use clang-format to format the code. We recommend you to configure the clang-format according to the IDE / editor you use. The following link is how to configure vim / emacs / vscode to use clang-format. Vim https://github.com/rhysd/vim-clang-format Emacs https://github.com/llvm-mirror/clang/blob/master/tools/clang-format/clang-format.el VS Code https://code.visualstudio.com/docs/cpp/cpp-ide#_code-formatting
Project: Grafeas (Provisioning / Security & Compliance)
File: code-of-conduct.md

At Google, we recognize and celebrate the creativity and collaboration of open source contributors and the diversity of skills, experiences, cultures, and opinions they bring to the projects and communities they participate in. Every one of Google's open source projects and communities are inclusive environments, based on treating all individuals respectfully, regardless of gender identity and expression, sexual orientation, disabilities, neurodiversity, physical appearance, body size, ethnicity, nationality, race, age, religion, or other protected category. We value diverse opinions, but we value respectful behavior more. Respectful behavior includes: Being considerate, kind, constructive, and helpful. Not engaging in demeaning, discriminatory, harassing, hateful, sexualized, or physically threatening behavior, speech, and imagery. Not engaging in unwanted physical contact. Some Google open source projects may adopt their own specific codes of conduct, which may have additional detailed expectations for participants. We do not believe that all conflict is bad; healthy debate and disagreement often yield positive results. However, it is never okay to be disrespectful or to engage in behavior that violates the projects code of conduct. If you see someone violating the code of conduct, you are encouraged to address the behavior directly with those involved. Many issues can be resolved quickly and easily, and this gives people more control over the outcome of their dispute. If you are unable to resolve the matter for any reason, or if the behavior is threatening or harassing, report it. We are dedicated to providing an environment where participants feel welcome and safe. Reports should be directed to wmd@google.com, the Project Steward for Grafeas. It is the Project Stewards duty to receive and address reported violations of the code of conduct. The steward will then work with a committee consisting of representatives from the Open Source Programs Office and the Google Open Source Strategy team. We will investigate every complaint, but you may not receive a direct response. We will use our discretion in determining when and how to follow up on reported incidents, which may range from not taking action to permanent expulsion from the project and project-sponsored spaces. We will notify the accused of the report and provide them an opportunity to discuss it before any action is taken. In potentially harmful situations, such as ongoing harassment or threats to anyone's safety, we may take action without notice. We will do our utmost to keep the identity of the reporter anonymous. This enforcement policy has been adopted from .
Project: Apache Hadoop (App Definition and Development / Database)
File: README.md

<!-- 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. --> The YARN UI is an Ember based web-app that provides visualization of the applications running on the Apache Hadoop YARN framework. You can point the UI to custom locations by setting the environment variables in `src/main/webapp/config/configs.env`. In order to make the UI running on Ember server (started by `yarn start`) work with independently running ResourceManager, you need to enable CORS by setting `hadoop.http.cross-origin.enabled` to true and adding `org.apache.hadoop.security.HttpCrossOriginFilterInitializer` to `hadoop.http.filter.initializers` in core-site.xml of the ResourceManager. All the following commands must be run inside `src/main/webapp`. You will need the following things properly installed on your computer. Install v1.21.1 Install v1.8.8 Install all dependencies by running `yarn install` & `bower install` `yarn start` Visit your app at . `yarn run build` (production) Files would be stored in "dist/" Warning: Do not edit the _package.json_ or _bower.json_ files manually. This could make them out-of-sync with the respective lock or shrinkwrap files. YARN UI has replaced NPM with Yarn package manager. And hence Yarn would be used to manage dependencies defined in package.json. Please use the Yarn and Bower command-line tools to add new dependencies. And the tool version must be same as those defined in Prerequisites section. Once any dependency is added: If it's in package.json. Make sure that the respective, and only those changes are reflected in yarn.lock file. If it's in bower.json. Make sure that the respective, and only those changes are reflected in bower-shrinkwrap.json file. Commands to add using CLI tools: Yarn: yarn add [package-name] Bower: bower install --save [package-name] Use ember-cli blueprint generator - added `yarn-ui` profile to pom.xml leveraging which automatically installs Node.js and Yarn locally under target/webapp directory. After building yarn-ui by `mvn package -Pyarn-ui`, you can reuse the locally installed Node.js and Yarn instead of manually installing them. ``` $ mvn package -Pyarn-ui $ export PATH=$PWD/target/webapp/node:$PATH $ export YARNJS=$PWD/target/webapp/node/yarn/dist/bin/yarn.js $ cd src/main/webapp/ $ node $YARNJS install $ node node_modules/.bin/bower install $ node $YARNJS start ```
Project: KICS (Provisioning / Security & Compliance)
File: 6a68bebe-c021-492e-8ddb-55b0567fb768.md

title: Security Context Deny Admission Control Plugin Not Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6a68bebe-c021-492e-8ddb-55b0567fb768 Query name: Security Context Deny Admission Control Plugin Not Set Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: When using kube-apiserver command, the '--enable-admission-plugins' flag should have 'SecurityContextDeny' plugin and the plugin should be correctly configured in AdmissionControl Config file when 'PodSecurityPolicy' plugin is not set<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--enable-admission-plugins=AlwaysAdmit"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--enable-admission-plugins=SecurityContextDeny", "--admission-control-config-file=path/to/plugin/config/file.yaml"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver","--enable-admission-plugins=SecurityContextDeny", "--admission-control-config-file=path/to/plugin/config/file.yaml"] args: [] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 3 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver","--enable-admission-plugins=PodSecurityPolicy", "--admission-control-config-file=path/to/plugin/config/file.yaml"] args: [] restartPolicy: OnFailure ```
Project: Open Application Model (App Definition and Development / Application Definition & Image Build)
File: SPEC.md

This is Open Application Model documentation version v0.3.0. Learn more about versioning . 1. 1. 1. 1. | | Category | API Version | | :-: | :--: | :-: | | ComponentDefiniton | core | v1beta1 | | WorkloadDefiniton | core | v1beta1 | | TraitDefinition | core | v1beta1 | | Application Scope | core | v1beta1 | | Application | core | v1beta1 | For the model objects, Open Application Model adopts . Releases of the model are versioned according to and described in . Implementations of the model are required to specify which version they implement. Changes to the API objects in this model follows and defined in Kubernetes API resource convention. It doesn't couple with release version of the model. Changes to the change process (e.g. governance model, review/approve process etc) itself are not currently versioned but may be independently versioned in the future.
Project: YugabyteDB (App Definition and Development / Database)
File: yba_storage-config_nfs_create.md

Create an NFS YugabyteDB Anywhere storage configuration Create an NFS storage configuration in YugabyteDB Anywhere ``` yba storage-config nfs create [flags] ``` ``` --backup-location string [Required] The complete backup location including. -h, --help help for create ``` ``` -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") -n, --name string [Optional] The name of the storage configuration for the operation. Required for create, delete, describe, update. -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) ``` - Manage a YugabyteDB Anywhere NFS storage configuration
Project: SPIRE (Provisioning / Key Management)
File: auditlog.md

SPIRE Server can be configured to emit audit logs through the configuration. Audit logs are sent to the same output as regular logs. Each entry contains fields related with the provided request to each endpoint. It also contains audit log specific fields that provide additional information. | Key | Description | Values | |-|-|| | type | Constant value that is used to identify that the current entry is an audit log. | audit | | request_id | A uuid that identifies the current call. It is useful for batch operations that can emit multiple audit logs, one per each operation that is done. | | | status | Indicates if the call was successful or not. | [error, success] | | status_code | In case of an error, contains the gRPC status code. | | | status_message | In case of an error, contains the error returned to the caller. | | The following fields are provided to identify the caller. _NOTE:_ In order to enable audit log in Kubernetes for calls done on UDS endpoints, `hostPID: true` is required in the SPIRE Server node. | Key | Description | |-|--| | caller_uid | Caller user ID. | | caller_gid | Caller group ID. | | caller_path | Caller binary file path. | | Key | Description | |-|-| | caller_addr | Caller IP address. | | caller_id | SPIFFE ID extracted from the X.509 certificate presented by the caller. |
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: fix-12347.en.md

Always render valid messages for egress MQTT data bridge from the data fetched by Rule SQL, even if the data is incomplete and placeholders used in the bridge configuration are missing. Previously, some messages were rendered as invalid and were discarded by the MQTT egress data bridge. Render undefined variables as empty strings in `payload` and `topic` templates of the MQTT egress data bridge. Previously, undefined variables were rendered as `undefined` strings.
Project: KICS (Provisioning / Security & Compliance)
File: a81573f9-3691-4d83-88a0-7d4af63e17a3.md

title: Azure App Service Client Certificate Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a81573f9-3691-4d83-88a0-7d4af63e17a3 Query name: Azure App Service Client Certificate Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Azure App Service client certificate should be enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "azurermappservice" "positive1" { name = "example-app-service" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name appserviceplanid = azurermappserviceplan.example.id site_config { dotnetframeworkversion = "v4.0" scm_type = "LocalGit" } app_settings = { SOME_KEY = "some-value" } connection_string { name = "Database" type = "SQLServer" value = "Server=some-server.mydomain.com;Integrated Security=SSPI" } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="16" resource "azurermappservice" "positive2" { name = "example-app-service" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name appserviceplanid = azurermappserviceplan.example.id site_config { dotnetframeworkversion = "v4.0" scm_type = "LocalGit" } app_settings = { SOME_KEY = "some-value" } clientcertenabled = false connection_string { name = "Database" type = "SQLServer" value = "Server=some-server.mydomain.com;Integrated Security=SSPI" } } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermappservice" "negative" { name = "example-app-service" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name appserviceplanid = azurermappserviceplan.example.id site_config { dotnetframeworkversion = "v4.0" scm_type = "LocalGit" } app_settings = { SOME_KEY = "some-value" } clientcertenabled = true connection_string { name = "Database" type = "SQLServer" value = "Server=some-server.mydomain.com;Integrated Security=SSPI" } } ```
Project: StarRocks (App Definition and Development / Database)
File: superset_support.md

displayed_sidebar: "English" is a modern data exploration and visualization platform. It uses to query data. Although can be used, it does not support `largeint`. So we developed . Python 3.x mysqlclient (pip install mysqlclient) Notice: If `mysqlclient` is not installed, an exception will be thrown: ```plain text No module named 'MySQLdb' ``` Since `dialect` does not contribute to `SQLAlchemy`, it needs to be installed from the source code. If you install `superset` with Docker, install `sqlalchemy-starrocks` with `root`. Install from ```shell pip install . ``` Uninstall ```shell pip uninstall sqlalchemy-starrocks ``` To connect to StarRocks with SQLAlchemy, the following URL pattern can be used: ```shell starrocks://<username>:<password>@<host>:<port>/<database>[?charset=utf8] ``` It is recommended to use python 3.x to connect to the StarRocks database, eg: ```python from sqlalchemy import create_engine import pandas as pd conn = createengine('starrocks://root:@x.x.x.x:9030/supersetdb?charset=utf8') sql = """select * from xxx""" df = pd.read_sql(sql, conn) ``` In superset, use `Other` database, and set url as: ```shell starrocks://root:@x.x.x.x:9030/superset_db?charset=utf8 ```
Project: YDB (App Definition and Development / Database)
File: options_cloud_additional.md

When using authentication modes that involve token rotation along with regularly re-requesting them from IAM (Refresh Token and Service Account Key), a special parameter can be set to indicate where the IAM service is located: `--iam-endpoint <URL>` : Sets the URL of the IAM service to request new tokens in authentication modes with token rotation. The default value is `"iam.api.cloud.yandex.net"`.
Project: StarRocks (App Definition and Development / Database)
File: array_join.md

displayed_sidebar: "English" Concatenates the elements of an array into a string. ```Haskell arrayjoin(array, sep[, nullreplace_str]) ``` `array`: the array whose elements you want to concatenate. Only the ARRAY data type is supported. `sep`: the delimiter that is used to separate the concatenated array elements. Only the VARCHAR data type is supported. `nullreplacestr`: the string that is used to substitute `NULL` values. Only the VARCHAR data type is supported. Returns a value of the VARCHAR data type. The value of the `array` parameter must be a one-dimensional array. The `array` parameter does not support DECIMAL values. If you set the `sep` parameter to `NULL`, the return value is `NULL`. If you do not specify the `nullreplacestr` parameter, `NULL` values are discarded. If you set the `nullreplacestr` parameter to `NULL`, the return value is `NULL`. Example 1: Concatenate the elements of an array. In this example, the `NULL` value in the array is discarded, and the concatenated array elements are separated by underscores (`_`). ```plaintext mysql> select arrayjoin([1, 3, 5, null], ''); +-+ | arrayjoin([1,3,5,NULL], '') | +-+ | 135 | +-+ ``` Example 2: Concatenate the elements of an array. In this example, the `NULL` value in the array is substituted with `NULL` strings, and the concatenated array elements are separated by underscores (`_`). ```plaintext mysql> select arrayjoin([1, 3, 5, null], '', 'NULL'); ++ | arrayjoin([1,3,5,NULL], '', 'NULL') | ++ | 135_NULL | ++ ```
Project: ArangoDB (App Definition and Development / Database)
File: implicit_value_converting_constructor.md

+++ title = "`basic_result(R &&)`" description = "Implicit `valuetype` constructor. Available if `predicate::enablevalueconvertingconstructor<R>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "implicit-constructors", "converting-constructors"] weight = 180 +++ Implicit `valuetype` constructor. Calls {{% api "void onresult_construction(T *, U &&) noexcept" %}} with `this` and `R`. Requires: `predicate::enablevalueconverting_constructor<R>` is true. Complexity: Same as for `value_type`'s copy or move constructor. Constexpr, triviality and noexcept of underlying operations is propagated.
Project: ShardingSphere (App Definition and Development / Database)
File: drop-sharding-table-reference-rule.en.md

+++ title = "DROP SHARDING TABLE REFERENCE RULE" weight = 14 +++ The `DROP SHARDING TABLE REFERENCE RULE` syntax is used to drop specified sharding table reference rule. {{< tabs >}} {{% tab name="Grammar" %}} ```sql DropShardingTableReferenceRule ::= 'DROP' 'SHARDING' 'TABLE' 'REFERENCE' 'RULE' ifExists? ruleName (',' ruleName)* ifExists ::= 'IF' 'EXISTS' ruleName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} `ifExists` clause is used for avoid `Sharding reference rule not exists` error. Drop a specified sharding table reference rule ```sql DROP SHARDING TABLE REFERENCE RULE ref_0; ``` Drop multiple sharding table reference rules ```sql DROP SHARDING TABLE REFERENCE RULE ref0, ref1; ``` Drop sharding table reference rule with `ifExists` clause ```sql DROP SHARDING TABLE REFERENCE RULE IF EXISTS ref_0; ``` `DROP`, `SHARDING`, `TABLE`, `REFERENCE`, `RULE`