cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: f42dfe7e-787d-4478-a75e-a5f3d8a2269e.md

title: Operation Using Implicit Flow hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: f42dfe7e-787d-4478-a75e-a5f3d8a2269e Query name: Operation Using Implicit Flow Platform: OpenAPI Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Operation Object should not use implicit flow<br> ```json title="Positive test num. 1 - json file" hl_lines="22" { "swagger": "2.0", "info": { "title": "Simple API overview", "version": "1.0.0" }, "schemes": [ "https" ], "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "security": [ { "oAuth2AuthCodeNeg2": [] } ] } } }, "securityDefinitions": { "oAuth2AuthCodeNeg2": { "type": "oauth2", "description": "For more information, see https://api.my.company.com/docs/oauth", "flow": "implicit", "authorizationUrl": "https://api.my.company.com/oauth/authorize", "scopes": { "write:api": "modify apis in your account", "read:api": "read your apis" } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="16" swagger: "2.0" info: title: Simple API overview version: 1.0.0 schemes: https paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response security: oAuth2AuthCodeNeg2: [] securityDefinitions: oAuth2AuthCodeNeg2: type: oauth2 description: For more information, see https://api.my.company.com/docs/oauth flow: implicit authorizationUrl: https://api.my.company.com/oauth/authorize scopes: write:api: modify apis in your account read:api: read your apis ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API overview", "version": "1.0.0" }, "schemes": [ "https" ], "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "security": [ { "oAuth2AuthCodeNeg2": [ "write", "read" ] } ] } } }, "securityDefinitions": { "oAuth2AuthCodeNeg2": { "type": "oauth2", "description": "For more information, see https://api.my.company.com/docs/oauth", "flow": "accessCode", "authorizationUrl": "https://api.my.company.com/oauth/authorize", "tokenUrl": "https://api.my.company.com/oauth/token", "scopes": { "write:api": "modify apis in your account", "read:api": "read your apis" } } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: "2.0" info: title: Simple API overview version: 1.0.0 schemes: https paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response security: oAuth2AuthCodeNeg2: write read securityDefinitions: oAuth2AuthCodeNeg2: type: oauth2 description: For more information, see https://api.my.company.com/docs/oauth flow: accessCode authorizationUrl: https://api.my.company.com/oauth/authorize tokenUrl: https://api.my.company.com/oauth/token scopes: write:api: modify apis in your account read:api: read your apis ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: fuzzy_mode_convert_table.md

| json type \ dest type | bool | int | uint | float |string| | | | | |--|--| | number | positive => true <br/> negative => true <br/> zero => false| 23.2 => 23 <br/> -32.1 => -32| 12.1 => 12 <br/> -12.1 => 0|as normal|same as origin| | string | empty string => false <br/> string "0" => false <br/> other strings => true | "123.32" => 123 <br/> "-123.4" => -123 <br/> "123.23xxxw" => 123 <br/> "abcde12" => 0 <br/> "-32.1" => -32| 13.2 => 13 <br/> -1.1 => 0 |12.1 => 12.1 <br/> -12.3 => -12.3<br/> 12.4xxa => 12.4 <br/> +1.1e2 =>110 |same as origin| | bool | true => true <br/> false => false| true => 1 <br/> false => 0 | true => 1 <br/> false => 0 |true => 1 <br/>false => 0|true => "true" <br/> false => "false"| | object | true | 0 | 0 |0|originnal json| | array | empty array => false <br/> nonempty array => true| [] => 0 <br/> [1,2] => 1 | [] => 0 <br/> [1,2] => 1 |[] => 0<br/>[1,2] => 1|original json|
Project: EDB (App Definition and Development / Database)
File: backup_recovery.md

Until CloudNativePG 1.20, this page used to contain both the backup and recovery phases of a PostgreSQL cluster. The reason was that CloudNativePG supported only backup and recovery object stores. Version 1.21 introduces support for the Kubernetes `VolumeSnapshot` API, providing more possibilities for the end user. As a result, and are now in two separate sections.
Project: EDB (App Definition and Development / Database)
File: use_cases.md

CloudNativePG has been designed to work with applications that reside in the same Kubernetes cluster, for a full cloud native experience. However, it might happen that, while the database can be hosted inside a Kubernetes cluster, applications cannot be containerized at the same time and need to run in a traditional environment such as a VM. In a typical situation, the application and the database run in the same namespace inside a Kubernetes cluster. The application, normally stateless, is managed as a standard `Deployment`, with multiple replicas spread over different Kubernetes node, and internally exposed through a `ClusterIP` service. The service is exposed externally to the end user through an `Ingress` and the provider's load balancer facility, via HTTPS. The application uses the backend PostgreSQL database to keep track of the state in a reliable and persistent way. The application refers to the read-write service exposed by the `Cluster` resource defined by CloudNativePG, which points to the current primary instance, through a TLS connection. The `Cluster` resource embeds the logic of single primary and multiple standby architecture, hiding the complexity of managing a high availability cluster in Postgres. Another possible use case is to manage your PostgreSQL database inside Kubernetes, while having your applications outside of it (for example in a virtualized environment). In this case, PostgreSQL is represented by an IP address (or host name) and a TCP port, corresponding to the defined Ingress resource in Kubernetes. The application can still benefit from a TLS connection to PostgreSQL.
Project: ArangoDB (App Definition and Development / Database)
File: explicit_copy_converting_constructor.md

+++ title = "`explicit basicresult(const basicresult<R, S, P> &)`" description = "Explicit converting copy constructor from compatible `basicresult`. Available if `predicate::enablecompatible_conversion<R, S, P>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "explicit-constructors", "converting-constructors"] weight = 310 +++ Explicit converting copy constructor from compatible `basicresult`. Calls {{% api "void onresultcopyconstruction(T *, U &&) noexcept" %}} with `this` and the input. Requires: `predicate::enablecompatibleconversion<R, S, P>` is true. Complexity: Same as for the copy constructors of the underlying types. Constexpr, triviality and noexcept of underlying operations is propagated. Guarantees: If an exception is thrown during the operation, the object is left in a partially completed state, as per the normal rules for the same operation on a `struct`.
Project: SuperEdge (Provisioning / Automation & Configuration)
File: CHANGELOG-0.3.md

- - Edgeadm supported creating native Kubernetes cluster with pre-installed SuperEdge components(, ), or . Edgeadm supported adding new nodes to edge Kubernetes cluster(, ). Enhanced edge autonomy by detecting failing nodes within the offline regions, so as to avoid routing traffic to abnormal nodes(, ) Supported Golang 1.16(, ). Fixed a bug that caused kubectl cp failing to disconnect after copying(, ). Added quickstart guide to create edge Kubernetes cluster using Edgeadm.
Project: MongoDB (App Definition and Development / Database)
File: test_commands.md

All test commands are denoted with the `.testOnly()` modifier to the `MONGOREGISTERCOMMAND` invocation. For example: ```c++ MONGOREGISTERCOMMAND(EchoCommand).testOnly(); ``` To be able to run these commands, the server must be started with the `enableTestCommands=1` server parameter (e.g. `--setParameter enableTestCommands=1`). Resmoke.py often sets this server parameter for testing. Some often-used commands that are test-only: As a very rough estimate, about 10% of all server commands are test-only. These additional commands will appear in `db.runCommand({listCommands: 1})` when the server has test commands enabled. A few pointers to relevant code that sets this up:
Project: Kapitan (Provisioning / Automation & Configuration)
File: kap_4_standalone_executable.md

Create a portable (i.e. static) kapitan binary for users. This executable will be made available for each release on Github. The target/tested platform is Debian 9 (possibly Windows to be supported in the future). Criteria: speed of the resulting binary size of the resulting binary portability of the binary (single-file executable or has an accompanying folder) cross-platform actively maintained supports Python 3.6, 3.7 Author: @yoshi-1224 (tentative first-choice) (Alternative) (also part of GSoC 2019. It might soon support ).
Project: Siddhi (App Definition and Development / Streaming & Messaging)
File: index.md

Siddhi Core Libraries ===================== ](https://wso2.org/jenkins/view/wso2-dependencies/job/siddhi/job/siddhi) ](https://github.com/siddhi-io/siddhi/releases) ](https://github.com/siddhi-io/siddhi/releases) ](https://github.com/siddhi-io/siddhi/commits/master) ](https://github.com/siddhi-io/siddhi/commits/master) ](https://codecov.io/gh/siddhi-io/siddhi) ](https://bestpractices.coreinfrastructure.org/projects/2974) ](https://opensource.org/licenses/Apache-2.0) <a target="blank" href="https://siddhi.io/">Siddhi</a> is a cloud native **Streaming** and **Complex Event Processing_ engine that understands Streaming SQL queries in order to capture events from diverse data sources, process them, detect complex conditions, and publish output to various endpoints in real time. Siddhi Core Libraries contains the essential core libraries need for Siddhi execution such as , , , and . Siddhi can run as an embedded Java and Python library, as a micro service on bare metal, VM, and Docker and natively in Kubernetes. Siddhi provides web-based graphical and textual tooling for development. For information on <a target="blank" href="https://siddhi.io/">Siddhi</a> and it's features refer <a target="blank" href="https://siddhi.io/redirect/docs.html">Siddhi Documentation</a>. Download Siddhi Core Libraries; Versions 5.x and above with group id `io.siddhi.` from <a target="_blank" href="https://mvnrepository.com/artifact/io.siddhi/">here</a>. Versions 4.x and lower with group id `org.wso2.siddhi.` from <a target="_blank" href="https://mvnrepository.com/artifact/org.wso2.siddhi/">here</a>. Download Siddhi tooling and runtime distributions <a target="_blank" href="https://siddhi.io/redirect/download.html">here</a>. Get started with Siddhi in a few minutes by following the <a target="_blank" href="https://siddhi.io/redirect/quick-start.html">Siddhi Quick Start Guide</a>. For more information on using Siddhi refer <a target="_blank" href="https://siddhi.io/redirect/docs.html">Siddhi Documentation</a>. Latest API Docs is <a target="_blank" href="https://siddhi-io.github.io/siddhi/api/5.1.30">5.1.30</a>. You can reachout through Slack channel, Google mail group and etc. Please refer the community contribution for more information.
Project: YugabyteDB (App Definition and Development / Database)
File: yba_storage-config_s3_create.md

Create an S3 YugabyteDB Anywhere storage configuration Create an S3 storage configuration in YugabyteDB Anywhere ``` yba storage-config s3 create [flags] ``` ``` --backup-location string [Required] The complete backup location including "s3://". --access-key-id string S3 Access Key ID. Required for non IAM role based storage configurations. Can also be set using environment variable AWSACCESSKEY_ID. --secret-access-key string S3 Secret Access Key. Required for non IAM role based storage configurations. Can also be set using environment variable AWSSECRETACCESS_KEY. --use-iam-instance-profile [Optional] Use IAM Role from the YugabyteDB Anywhere Host. Configuration creation will fail on insufficient permissions on the host. (default false) -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 S3 storage configuration
Project: ClickHouse (App Definition and Development / Database)
File: v22.11.6.44-stable.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Fixed performance of short `SELECT` queries that read from tables with large number of`Array`/`Map`/`Nested` columns. (). Backported in : Fix too big memory usage for vertical merges on non-remote disk. Respect `maxinsertdelayedstreamsforparallelwrite` for the remote disk. (). Backported in : Fix zookeeper downloading, update the version, and optimize the image size. (). Backported in : Remove the dependency on the `adduser` tool from the packages, because we don't use it. This fixes . (). Backported in : Get rid of unnecessary build for standalone clickhouse-keeper. (). Backported in : Some time ago the ccache compression was changed to `zst`, but `gz` archives are downloaded by default. It fixes it by prioritizing zst archive. (). Backported in : Fixed bug with non-parsable default value for EPHEMERAL column in table metadata. (). Backported in : A couple of seg faults have been reported around `c-ares`. All of the recent stack traces observed fail on inserting into `std::unodered_set<>`. I believe I have found the root cause of this, it seems to be unprocessed queries. Prior to this PR, CH calls `poll` to wait on the file descriptors in the `c-ares` channel. According to the , a negative return value means an error has ocurred. Because of this, we would abort the execution and return failure. The problem is that `poll` will also return a negative value if a system interrupt occurs. A system interrupt does not mean the processing has failed or ended, but we would abort it anyways because we were checking for negative values. Once the execution is aborted, the whole stack is destroyed, which includes the `std::unordered_set<std::string>` passed to the `void ` parameter of the c-ares callback. Once c-ares completed the request, the callback would be invoked and would access an invalid memory address causing a segfault. (). Backported in : Fix reading of non existing nested columns with multiple level in compact parts. (). Backported in : Fix possible `LOGICAL_ERROR` in asynchronous inserts with invalid data sent in format `VALUES`. (). Backported in : Fix an invalid processing of constant `LowCardinality` argument in function `arrayMap`. This bug could lead to a segfault in release, and logical error `Bad cast` in debug build. (). Another attempt to fix automerge, or at least to have debug footprint (). Add check for running workflows to merge_pr.py (). Get rid of progress timestamps in release publishing (). Add necessary dependency for sanitizers (). Add helping logging to auto-merge script (). Fix write buffer destruction order for vertical merge. (). Get rid of legacy DocsReleaseChecks ().
Project: ArangoDB (App Definition and Development / Database)
File: try_operation_extract_value.md

+++ title = "`decltype(auto) tryoperationextract_value(X)`" description = "Default implementation of `tryoperationextractvalue(X)` ADL customisation point for `BOOSTOUTCOME_TRY`." +++ This default implementation returns whatever the `.assume_value()` or `.value()` member functions return, preferentially choosing the former where both are available. Requires: That the expression `std::declval<T>().assume_value()` and/or `std::declval<T>().value()` is a valid expression. Namespace: `BOOSTOUTCOMEV2_NAMESPACE` Header: `<boost/outcome/try.hpp>`
Project: sigstore (Provisioning / Security & Compliance)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at <maintainers@sigstore.dev>. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at
Project: KICS (Provisioning / Security & Compliance)
File: 9f34885e-c08f-4d13-a7d1-cf190c5bd268.md

title: Redis Not Compliant hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9f34885e-c08f-4d13-a7d1-cf190c5bd268 Query name: Redis Not Compliant Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: Check if the redis version is compliant with the necessary AWS PCI DSS requirements<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="6" name: Basic example community.aws.elasticache: name: "test-please-delete" state: present engine: memcached cacheengineversion: 1.4.14 node_type: cache.m1.small num_nodes: 1 ``` ```yaml title="Negative test num. 1 - yaml file" name: Basic example community.aws.elasticache: name: test-please-delete state: present engine: memcached cacheengineversion: 5.1.10 node_type: cache.m1.small num_nodes: 1 ```
Project: Kapitan (Provisioning / Automation & Configuration)
File: kapitan_lint.md

Perform a checkup on your inventory or refs. !!! example "" ```shell ./kapitan lint ``` ??? example "click to expand output" ```shell Running yamllint on all inventory files... .yamllint not found. Using default values File ./inventory/classes/components/echo-server.yml has the following issues: 95:29: forbidden implicit octal value "0550" (octal-values) File ./inventory/classes/terraform/gcp/services.yml has the following issues: 15:11: duplication of key "enablecomputeservice" in mapping (key-duplicates) Total yamllint issues found: 2 Checking for orphan classes in inventory... No usage found for the following 6 classes: {'components.argoproj.cd.argocd-server-oidc', 'components.helm.cert-manager-helm', 'components.rabbitmq-operator.rabbitmq-configuration', 'components.rabbitmq-operator.rabbitmq-operator', 'features.gkms-demo', 'projects.localhost.kubernetes.katacoda'} ```
Project: StarRocks (App Definition and Development / Database)
File: query_external_data.md

displayed_sidebar: "English" This topic guides you through querying data from external data sources by using external catalogs. External catalogs are created based on external data sources. For information about supported types of external catalogs, see . Connect your StarRocks cluster. If you use the MySQL client to connect the StarRocks cluster, you go to `default_catalog` by default after connecting. If you use JDBC to connect the StarRocks cluster, you can go directly to the destination database in the default catalog by specifying `defaultcatalog.dbname` when connecting. (Optional) Execute the following statement to view all the catalogs and find the external catalog you have created. See to check the output of this statement. ```SQL SHOW CATALOGS; ``` (Optional) Execute the following statement to view all the databases in the external catalog. See to check the output of this statement. ```SQL SHOW DATABASES FROM catalog_name; ``` (Optional) Execute the following statement to go to the destination database in the external catalog. ```SQL USE catalogname.dbname; ``` Query external data. For more usages of the SELECT statement, see . ```SQL SELECT * FROM table_name; ``` If you do not specify the external catalog and database in the preceding steps, you can directly specify them in a select query. ```SQL SELECT * FROM catalogname.dbname.table_name; ``` If you already created a Hive catalog named `hive1` and want to use `hive1` to query data from `hivedb.hivetable` of an Apache Hive cluster, you can perform one of the following operations: ```SQL USE hive1.hive_db; SELECT * FROM hive_table limit 1; ``` Or ```SQL SELECT * FROM hive1.hivedb.hivetable limit 1; ``` To query data from your StarRocks cluster, see .