cwielenb/CNCF-Dataset huggingface dataset:
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: CONDUCT.md

Cobra will follow a steady release cadence. Non breaking changes will be released as minor versions quarterly. Patch bug releases are at the discretion of the maintainers. Users can expect security patch fixes to be released within relatively short order of a CVE becoming known. For more information on security patch fixes see the CVE section below. Releases will follow . Users tracking the Master branch should expect unpredictable breaking changes as the project continues to move forward. For stability, it is highly recommended to use a release. We will maintain two major releases in a moving window. The N-1 release will only receive bug fixes and security updates and will be dropped once N+1 is released. Deprecation of Go versions or dependent packages will only occur in major releases. To reduce the change of this taking users by surprise, any large deprecation will be preceded by an announcement in the and an Issue on Github. Maintainers will make every effort to release security patches in the case of a medium to high severity CVE directly impacting the library. The speed in which these patches reach a release is up to the discretion of the maintainers. A low severity CVE may be a lower priority than a high severity one. Cobra maintainers will use GitHub issues and the as the primary means of communication with the community. This is to foster open communication with all users and contributors. Breaking changes are generally allowed in the master branch, as this is the branch used to develop the next release of Cobra. There may be times, however, when master is closed for breaking changes. This is likely to happen as we near the release of a new version. Breaking changes are not allowed in release branches, as these represent minor versions that have already been released. These version have consumers who expect the APIs, behaviors, etc, to remain stable during the lifetime of the patch stream for the minor release. Examples of breaking changes include: Removing or renaming exported constant, variable, type, or function. Updating the version of critical libraries such as `spf13/pflag`, `spf13/viper` etc... Some version updates may be acceptable for picking up bug fixes, but maintainers must exercise caution when reviewing. There may, at times, need to be exceptions where breaking changes are allowed in release branches. These are at the discretion of the project's maintainers, and must be carefully considered before merging. Maintainers will ensure the Cobra test suite utilizes the current supported versions of Golang. Changes to this document and the contents therein are at the discretion of the maintainers. None of the contents of this document are legally binding in any way to the maintainers or the users.
Project: OAuth2 Proxy (Provisioning / Key Management)
File: endpoints.md

id: endpoints title: Endpoints OAuth2 Proxy responds directly to the following endpoints. All other endpoints will be proxied upstream when authenticated. The `/oauth2` prefix can be changed with the `--proxy-prefix` config variable. /robots.txt - returns a 200 OK response that disallows all User-agents from all paths; see for more info /ping - returns a 200 OK response, which is intended for use with health checks /ready - returns a 200 OK response if all the underlying connections (e.g., Redis store) are connected /metrics - Metrics endpoint for Prometheus to scrape, serve on the address specified by `--metrics-address`, disabled by default /oauth2/sign_in - the login page, which also doubles as a sign-out page (it clears cookies) /oauth2/sign_out - this URL is used to clear the session cookie /oauth2/start - a URL that will redirect to start the OAuth cycle /oauth2/callback - the URL used at the end of the OAuth cycle. The oauth app will be configured with this as the callback url. /oauth2/userinfo - the URL is used to return user's email from the session in JSON format. /oauth2/auth - only returns a 202 Accepted response or a 401 Unauthorized response; for use with the /oauth2/static/\* - stylesheets and other dependencies used in the sign_in and error pages To sign the user out, redirect them to `/oauth2/sign_out`. This endpoint only removes oauth2-proxy's own cookies, i.e. the user is still logged in with the authentication provider and may automatically re-login when accessing the application again. You will also need to redirect the user to the authentication provider's sign-out page afterward using the `rd` query parameter, i.e. redirect the user to something like (notice the url-encoding!): ``` /oauth2/signout?rd=https%3A%2F%2Fmy-oidc-provider.example.com%2Fsignout_page ``` Alternatively, include the redirect URL in the `X-Auth-Request-Redirect` header: ``` GET /oauth2/sign_out HTTP/1.1 X-Auth-Request-Redirect: https://my-oidc-provider/signoutpage ... ``` (The "signoutpage" should be the from if your OIDC provider supports Session Management and Discovery.) BEWARE that the domain you want to redirect to (`my-oidc-provider.example.com` in the example) must be added to the configuration option otherwise the redirect will be ignored. Make sure to include the actual domain and port (if needed) and not the URL (e.g "localhost:8081" instead of "http://localhost:8081"). This endpoint returns 202 Accepted response or a 401 Unauthorized response. It can be configured using the following query parameters: `allowed_groups`: comma separated list of allowed groups `allowedemaildomains`: comma separated list of allowed email domains `allowed_emails`: comma separated list of allowed emails
Project: Dragonfly (Provisioning / Container Registry)
File: dfcache_doc.md

% DFCACHE(1) Version v2.1.0 | Frivolous "Dfcache" Documentation dfcache doc generate documents Generate markdown documents for cmd: dfcache. ```shell dfcache doc [flags] ``` ``` -i, --cid string content or cache ID, e.g. sha256 digest of the content --config string the path of configuration file with yaml extension name, default is /etc/dragonfly/dfcache.yaml, it can also be set by env var: DFCACHE_CONFIG --console whether logger output records to the stdout --jaeger string jaeger endpoint url, like: http://localhost:14250/api/traces --logdir string Dfcache log directory --pprof-port int listen port for pprof, 0 represents random port (default -1) --service-name string name of the service for tracer (default "dragonfly-dfcache") -t, --tag string different tags for the same cid will be recognized as different files in P2P network --timeout duration Timeout for this cache operation, 0 is infinite --verbose whether logger use debug level --workhome string Dfcache working directory -h, --help help for doc --path string destination dir of generated markdown documents (default "./") ``` - the P2P cache client of dragonfly
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: device-cgroup-rule.md

Add a rule to the cgroup allowed devices list. The rule is expected to be in the format specified in the Linux kernel documentation : type: `a` (all), `c` (char), or `b` (block); major and minor: either a number, or `*` for all; mode: a composition of `r` (read), `w` (write), and `m` (mknod(2)).
Project: Trivy (Provisioning / Security & Compliance)
File: dart.md

Trivy supports . The following scanners are supported. | Package manager | SBOM | Vulnerability | License | |-| :: | :--: |:-:| | | | | - | The following table provides an outline of the features Trivy offers. | Package manager | File | Transitive dependencies | Dev dependencies | | Position | |-|--|:--:|:-:|::|:--:| | | pubspec.lock | | Included | | - | In order to detect dependencies, Trivy searches for `pubspec.lock`. Trivy marks indirect dependencies, but `pubspec.lock` file doesn't have options to separate root and dev transitive dependencies. So Trivy includes all dependencies in report. To build `dependency tree` Trivy parses . Currently supported default directories and `PUB_CACHE` environment (absolute path only). !!! note Make sure the cache directory contains all the dependencies installed in your application. To download missing dependencies, use `dart pub get` command.
Project: ArangoDB (App Definition and Development / Database)
File: explicit_result_make_error_code_copy_converting_constructor.md

+++ title = "`explicit basicoutcome(const basicresult<A, B, C> &)`" description = "Explicit converting copy constructor from compatible `basicresult`. Available if `predicate::enablemakeerrorcodecompatibleconversion<A, B, void, C>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "explicit-constructors", "converting-constructors"] weight = 341 +++ Explicit converting copy constructor from compatible `basicresult`. Calls {{% api "void onoutcomecopyconstruction(T *, U &&) noexcept" %}} with `this` and the input. Requires: `predicate::enablemakeerrorcodecompatible_conversion<A, B, void, C>` 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: ArangoDB (App Definition and Development / Database)
File: outcome_throw_as_system_error_with_payload_boost_enum.md

+++ title = "`void outcomethrowassystemerrorwithpayload(BoostErrorCodeEnum &&)`" description = "Specialisation of `outcomethrowassystemerrorwithpayload()` for input types where `boost::system::iserrorcodeenum<BoostErrorCodeEnum>` or `boost::system::iserrorconditionenum<BoostErrorCodeEnum>` is true." +++ A specialisation of `outcomethrowassystemerrorwithpayload()` for types where `boost::system::iserrorcodeenum<BoostErrorCodeEnum>` or `boost::system::iserrorconditionenum<BoostErrorCodeEnum>` is true. This executes {{% api "BOOSTOUTCOMETHROWEXCEPTION(expr)" %}} with a `boost::system::systemerror` constructed from the result of the ADL discovered free function `makeerrorcode(BoostErrorCodeEnum)`. Overridable: Argument dependent lookup. Requires: Either `boost::system::iserrorcodeenum<T>` or `boost::system::iserrorconditionenum<T>` to be true for a decayed `BoostErrorCodeEnum`. Namespace: `boost::system` Header: `<boost/outcome/boost_result.hpp>`
Project: StarRocks (App Definition and Development / Database)
File: all-commands.md

displayed_sidebar: "English" This topic lists all the SQL statements supported by StarRocks and categorizes these statements by their functions. - - - - - - - - - - - - - - - Manages users, roles, and privileges. Manages clusters, including FEs, BEs, compute nodes (CN), brokers, resource groups, storage volumes, tables, tablets, replicas, files, variables, plugins, and SQL blacklist.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: view.md

title: "View" <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> See for updates.
Project: Trivy (Provisioning / Security & Compliance)
File: nodejs.md

Trivy supports four types of Node.js package managers: `npm`, `Yarn`, `pnpm` and `Bun`[^1]. The following scanners are supported. | Artifact | SBOM | Vulnerability | License | |-|:-:|:-:|:-:| | npm | | | | | Yarn | | | | | pnpm | | | - | | Bun | | | | The following table provides an outline of the features Trivy offers. | Package manager | File | Transitive dependencies | Dev dependencies | | Position | |::|-|:--:|:--:|::|:--:| | npm | package-lock.json | | | | | | Yarn | yarn.lock | | | | | | pnpm | pnpm-lock.yaml | | Excluded | | - | | Bun | yarn.lock | | | | | In addition, Trivy scans installed packages with `package.json`. | File | Dependency graph | Position | License | |--|:-:|:--:|:-:| | package.json | - | - | | These may be enabled or disabled depending on the target. See for the detail. Trivy parses your files generated by package managers in filesystem/repository scanning. !!! tip Please make sure your lock file is up-to-date after modifying `package.json`. Trivy parses `package-lock.json`. To identify licenses, you need to download dependencies to `node_modules` beforehand. Trivy analyzes `node_modules` for licenses. By default, Trivy doesn't report development dependencies. Use the `--include-dev-deps` flag to include them. Trivy parses `yarn.lock`, which doesn't contain information about development dependencies. Trivy also uses `package.json` file to handle . To exclude devDependencies and allow aliases, `package.json` also needs to be present next to `yarn.lock`. Trivy analyzes `.yarn` (Yarn 2+) or `node_modules` (Yarn Classic) folder next to the yarn.lock file to detect licenses. By default, Trivy doesn't report development dependencies. Use the `--include-dev-deps` flag to include them. Trivy parses `pnpm-lock.yaml`, then finds production dependencies and builds a of dependencies with vulnerabilities. !!! note Trivy currently only supports Lockfile or earlier. Trivy supports scanning `yarn.lock` files generated by . You can use the command `bun install -y` to generate a Yarn-compatible `yarn.lock`. !!! note `bun.lockb` is not supported. Trivy parses the manifest files of installed packages in container image scanning and so on. Trivy searches for `package.json` files under `node_modules` and identifies installed packages. It only extracts package names, versions and licenses for those packages. must be generated
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: quickstart.md

title: Quickstart for Helm-based Operators linkTitle: Quickstart weight: 100 description: A simple set of instructions to set up and run a Helm-based operator. This guide walks through an example of building a simple nginx-operator powered by using tools and libraries provided by the Operator SDK. Go through the . Make sure your user is authorized with `cluster-admin` permissions. An accessible image registry for various operator images (ex. , ) and be logged in to your command line environment. `example.com` is used as the registry Docker Hub namespace in these examples. Replace it with another value if using a different registry or namespace. if the registry is private or uses a custom CA. Create a project directory for your project and initialize the project: ```sh mkdir nginx-operator cd nginx-operator operator-sdk init --domain example.com --plugins helm ``` Create a simple nginx API using Helm's built-in chart boilerplate (from `helm create`): ```sh operator-sdk create api --group demo --version v1alpha1 --kind Nginx ``` Build and push your operator's image: ```sh make docker-build docker-push IMG="example.com/nginx-operator:v0.0.1" ``` Install : ```sh operator-sdk olm install ``` Bundle your operator, then build and push the bundle image (defaults to `example.com/nginx-operator-bundle:v0.0.1`): ```sh make bundle IMG="example.com/nginx-operator:v0.0.1" make bundle-build bundle-push IMG="example.com/nginx-operator:v0.0.1" ``` Run your bundle. If your bundle image is hosted in a registry that is private and/or has a custom CA, these must be complete. ```sh operator-sdk run bundle example.com/nginx-operator-bundle:v0.0.1 ``` Create a sample Nginx custom resource: ```console $ kubectl apply -f config/samples/demov1alpha1nginx.yaml nginx.demo.example.com/nginx-sample created ``` Uninstall the operator: ```sh operator-sdk cleanup nginx-operator ``` Deploy your operator: ```sh make deploy IMG="example.com/nginx-operator:v0.0.1" ``` Create a sample Nginx custom resource: ```console $ kubectl apply -f config/samples/demov1alpha1nginx.yaml nginx.demo.example.com/nginx-sample created ``` Uninstall the operator: ```sh make undeploy ``` Read the for an in-depth walkthrough of building a Helm operator. new terminal tab/window, create a sample Memcached custom resource: ```console $ kubectl apply -f config/samples/cachev1alpha1memcached.yaml memcached.cache.example.com/memcached-sample created ``` Stop the operator by pressing `ctrl+c` in the terminal tab or window the operator is running in Read the for an in-depth walkthrough of building a Go operator.
Project: ArangoDB (App Definition and Development / Database)
File: implicit_failure_error_make_error_code_move_constructor.md

+++ title = "`basicoutcome(failuretype<EC> &&)`" description = "Implicit error-from-failure-type-sugar move constructor. Available if `predicate::enablemakeerrorcodecompatible_conversion<void, EC, void, void>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "implicit-constructors", "tagged-constructors"] weight = 532 +++ Implicit error-from-failure-type-sugar move constructor used to disambiguate the construction of the error type. Calls {{% api "void onoutcomemoveconstruction(T *, U &&) noexcept" %}} with `this` and `failuretype<EC> &&`. Requires: `predicate::enablemakeerrorcodecompatible_conversion<void, EC, void, void>` is true. Complexity: Same as for the `error_type` constructor which accepts `EC`. Constexpr, triviality and noexcept of underlying operations is propagated.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-aux-conf-mgmt-set.md

layout: global title: SET displayTitle: SET 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. The SET command sets a property, returns the value of an existing property or returns all SQLConf properties with value and meaning. To set SQL variables defined with use . ```sql SET SET [ -v ] SET propertykey[ = propertyvalue ] ``` -v* Outputs the key, value and meaning of existing SQLConf properties. property_key* Returns the value of specified property key. property_key=property_value* Sets the value for a given property key. If an old value exists for a given property key, then it gets overridden by the new value. ```sql -- Set a property. SET spark.sql.variable.substitute=false; -- List all SQLConf properties with value and meaning. SET -v; -- List all SQLConf properties with value for current session. SET; -- List the value of specified property key. SET spark.sql.variable.substitute; +--+--+ | key|value| +--+--+ |spark.sql.variable.substitute|false| +--+--+ ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.8.34.md

RabbitMQ `3.8.34` is a maintenance release. All users are recommended to upgrade to this release. RabbitMQ releases are distributed via , , and . This release and . explains what package repositories and tools can be used to provision modern Erlang versions. See the for general documentation on upgrades and for release notes of other releases. If upgrading from a `3.7.x` release, see upgrade and compatibility notes first. If upgrading from a `3.6.x` or older , first upgrade to and then to this version. Any questions about this release, upgrades or RabbitMQ in general are welcome on the and . RabbitMQ Debian package now lists Erlang 25.0 as supported. None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.8.34.tar.xz` instead of the source tarball produced by GitHub.
Project: KICS (Provisioning / Security & Compliance)
File: ccc3100c-0fdd-4a5e-9908-c10107291860.md

title: DNSSEC Using RSASHA1 hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ccc3100c-0fdd-4a5e-9908-c10107291860 Query name: DNSSEC Using RSASHA1 Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: DNSSEC should not use the RSASHA1 algorithm, which means if, within the 'dnssecconfig' block, the 'defaultkey_specs' block exists with the 'algorithm' field is 'rsasha1' which is bad.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="11" resource "googlednsmanaged_zone" "positive1" { name = "example-zone" dnsname = "example-${randomid.rnd.hex}.com." description = "Example DNS zone" labels = { foo = "bar" } dnssec_config { defaultkeyspecs{ algorithm = "rsasha1" } } } ``` ```tf title="Negative test num. 1 - tf file" resource "googlednsmanaged_zone" "negative1" { name = "example-zone" dnsname = "example-${randomid.rnd.hex}.com." description = "Example DNS zone" labels = { foo = "bar" } dnssec_config { defaultkeyspecs{ algorithm = "rsasha256" } } } ```
Project: Hazelcast Jet (App Definition and Development / Streaming & Messaging)
File: docker-enterprise.md

title: Running Enterprise With Docker description: How to use Jet Enterprise features in a Docker environment id: version-4.2-docker-enterprise original_id: docker-enterprise This section provides coverage of usage of Hazelcast Jet Enterprise features inside a Docker environment. For basic Docker usage you should read the first. If you have your license key you can start a Hazelcast Jet Enterprise member by running the following command: ```bash docker run -e JETLICENSEKEY=<your-license-key> hazelcast/hazelcast-jet-enterprise ``` Among other output you should see lines similar to the following in the log: ```text 2020-06-18 13:09:28,833 [ INFO] [main] [c.h.system]: Hazelcast Jet Enterprise 4.1 (20200429 - 8712224) starting at [172.17.0.5]:5701 ... 2020-06-18 13:09:28,834 [ INFO] [main] [c.h.i.i.NodeExtension]: Checking Hazelcast Enterprise license... 2020-06-18 13:09:28,840 [ INFO] [main] [c.h.i.i.NodeExtension]: License{ ..... } ... ```
Project: Meshery (Provisioning / Automation & Configuration)
File: artifact-hub.md

layout: integration title: Artifact Hub subtitle: Collaborative and visual infrastructure as code for Artifact Hub image: /assets/img/integrations/artifact-hub/icons/color/artifact-hub-color.svg permalink: extensibility/integrations/artifact-hub docURL: https://docs.meshery.io/extensibility/integrations/artifact-hub description: integrations-category: App Definition and Development integrations-subcategory: Application Definition & Image Build registrant: Artifact Hub components: featureList: [ "Discover, install and publish packages and configurations.", "Explore content like Helm charts schemas and templates in an interactive way.", "Subscribe to packages new releases and security alerts notifications, via email or webhooks." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: YDB (App Definition and Development / Database)
File: create-user.md

Creates a user with the specified name and password. Syntax: ```yql CREATE USER user_name [option] ``` `user_name`: The name of the user. It may contain lowercase Latin letters and digits. `option`: The password of the user: `PASSWORD 'password'` creates a user with the `password` password. The `ENCRYPTED` option is always enabled. `PASSWORD NULL` creates a user with an empty password.