cwielenb/CNCF-Dataset huggingface dataset:
Project: ClickHouse (App Definition and Development / Database)
File: v23.7.5.30-stable.md

sidebar_position: 1 sidebar_label: 2023 Backported in : The compiler's profile data (`-ftime-trace`) is uploaded to ClickHouse Cloud., the second attempt after . (). Backported in : Preserve environment parameters in `clickhouse start` command. Fixes . (). Not-ready Set (). Fix incorrect normal projection AST format (). Fix loading lazy database during system.table select query (). Fix wrong columns order for queries with parallel FINAL. (). Fix: interpolate expression takes source column instead of same name aliased from select expression. (). Correctly handle totals and extremes with `DelayedSource` (). Fix: sorted distinct with sparse columns (). Fix fuzzer crash in parseDateTime() (). Disable testreversedns_query/test.py (). Disable testhostregexpmultipleptr_records/test.py (). Fix broken `02862sorteddistinctsparsefix` (). Get rid of describe_parameters for the best robot token ().
Project: kube-hunter (Provisioning / Security & Compliance)
File: KHV021.md

vid: KHV021 title: Certificate Includes Email Address categories: [Information Disclosure] severity: low The Kubernetes API Server advertises a public certificate for TLS. This certificate includes an email address, that may provide additional information for an attacker on your organization, or be abused for further email based attacks. Do not include email address in the Kubernetes API server certificate. (You should continue to use certificates to secure the API Server!)
Project: KICS (Provisioning / Security & Compliance)
File: 6e2b1ec1-1eca-4eb7-9d4d-2882680b4811.md

title: Project-wide SSH Keys Are Enabled In VM Instances hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6e2b1ec1-1eca-4eb7-9d4d-2882680b4811 Query name: Project-wide SSH Keys Are Enabled In VM Instances Platform: GoogleDeploymentManager Severity: <span style="color:#ff7213">Medium</span> Category: Secret Management URL: VM Instance should block project-wide SSH keys<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" resources: name: vm type: compute.v1.instance properties: description: my-vm ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="8" resources: name: vm type: compute.v1.instance properties: description: my-vm metadata: fingerprint: fingerprint items: key: my-key value: true key: my-key-2 value: false ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="12" resources: name: vm type: compute.v1.instance properties: description: my-vm metadata: fingerprint: fingerprint items: key: my-key value: true key: block-project-ssh-keys value: false ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: vm type: compute.v1.instance properties: description: my-vm metadata: fingerprint: fingerprint items: key: my-key value: true key: block-project-ssh-keys value: true ```
Project: Artifact Hub (App Definition and Development / Application Definition & Image Build)
File: keda_scalers_repositories.md

KEDA scalers repositories are expected to be hosted in GitHub, GitLab or Bitbucket repos. When adding your repository to Artifact Hub, the url used must follow the following format: `https://github.com/user/repo[/path/to/packages]` `https://gitlab.com/user/repo[/path/to/packages]` `https://bitbucket.org/user/repo[/path/to/packages]` By default the `master` branch is used, but it's possible to specify a different one from the UI. Please NOTE that the repository URL used when adding the repository to Artifact Hub must NOT contain the git hosting platform specific parts, like tree/branch, just the path to your packages like it would show in the filesystem. The path/to/packages provided can contain metadata for one or more packages. Each package version must be on a separate folder, and it's up to you to decide if you want to publish one or multiple versions of your package. The structure of a repository with multiple scalers packages and versions could look something like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 1.0.0 README.md artifacthub-pkg.yml 2.0.0 README.md artifacthub-pkg.yml package2 1.0.0 README.md artifacthub-pkg.yml ``` This structure is flexible, and in some cases it can be greatly simplified. In the case of a single package with a single version available at a time (the publisher doesn't want to make previous ones available, for example), the structure could look like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 README.md artifacthub-pkg.yml ``` In the previous case, even the `package1` directory could be omitted. The reason is that both packages names and versions are read from the `artifacthub-pkg.yml` metadata file, so directories names are not used at all. Each package version needs an `artifacthub-pkg.yml` metadata file. Please see the file for more details. The repository metadata file shown above can be used to setup features like or . This file must be located at `/path/to/packages`. Once you have added your repository, you are all set up. As you add new versions of your scalers packages or even new packages to your git repository, they'll be automatically indexed and listed in Artifact Hub. Scalers source GitHub URL: Repository URL used in Artifact Hub: `https://github.com/kedacore/external-scalers/artifacthub` (please note how the tree/master part is not used)
Project: KICS (Provisioning / Security & Compliance)
File: 56dad03e-e94f-4dd6-93a4-c253a03ff7a0.md

title: Cosmos DB Account Without Tags hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 56dad03e-e94f-4dd6-93a4-c253a03ff7a0 Query name: Cosmos DB Account Without Tags Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Build Process URL: Cosmos DB Account must have a mapping of tags.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "azurermcosmosdbaccount" "positive1" { name = "tfex-cosmos-db-${random_integer.ri.result}" location = azurermresourcegroup.rg.location resourcegroupname = azurermresourcegroup.rg.name offer_type = "Standard" kind = "GlobalDocumentDB" } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermcosmosdbaccount" "negative1" { name = "tfex-cosmos-db-${random_integer.ri.result}" location = azurermresourcegroup.rg.location resourcegroupname = azurermresourcegroup.rg.name offer_type = "Standard" kind = "GlobalDocumentDB" tags = "tag_1" } ```
Project: Presto (App Definition and Development / Database)
File: bug-report.md

name: Open a Bug about: Create a bug report labels: bug assignees: '' <! Provide a general summary of the issue in the Title above --> <! Look through existing open and closed issues to see if someone has reported the issue before --> <! Include as many relevant details about the environment you experienced the bug in --> Presto version used: Storage (HDFS/S3/GCS..): Data source and connector used: Deployment (Cloud or On-prem): link to the complete debug logs: <! Tell us what should happen --> <! Tell us what happens instead of the expected behavior --> <! Not obligatory, but suggest a fix/reason for the bug or a workaround --> <! Provide a link to a live example, or an unambiguous set of steps to --> <! reproduce this bug. Include code to reproduce, if relevant --> <! How has this issue affected you? --> <! Providing context helps us come up with a solution that is most useful in the real world -->
Project: ClickHouse (App Definition and Development / Database)
File: settings-profile.md

slug: /en/sql-reference/statements/create/settings-profile sidebar_position: 43 sidebar_label: SETTINGS PROFILE title: "CREATE SETTINGS PROFILE" Creates that can be assigned to a user or a role. Syntax: ``` sql CREATE SETTINGS PROFILE [IF NOT EXISTS | OR REPLACE] name1 [ON CLUSTER cluster_name1] [, name2 [ON CLUSTER cluster_name2] ...] [IN accessstoragetype] [SETTINGS variable [= value] [MIN [=] minvalue] [MAX [=] maxvalue] [CONST|READONLY|WRITABLE|CHANGEABLEINREADONLY] | INHERIT 'profile_name'] [,...] ``` `ON CLUSTER` clause allows creating settings profiles on a cluster, see . Create a user: ```sql CREATE USER robin IDENTIFIED BY 'password'; ``` Create the `maxmemoryusageprofile` settings profile with value and constraints for the `maxmemory_usage` setting and assign it to user `robin`: ``` sql CREATE SETTINGS PROFILE maxmemoryusageprofile SETTINGS maxmemory_usage = 100000001 MIN 90000000 MAX 110000000 TO robin ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: hooks-dir.md

Each *.json file in the path configures a hook for buildah build containers. For more details on the syntax of the JSON files and the semantics of hook injection. Buildah currently support both the 1.0.0 and 0.1.0 hook schemas, although the 0.1.0 schema is deprecated. This option may be set multiple times; paths from later options have higher precedence. For the annotation conditions, buildah uses any annotations set in the generated OCI configuration. For the bind-mount conditions, only mounts explicitly requested by the caller via --volume are considered. Bind mounts that buildah inserts by default (e.g. /dev/shm) are not considered. If --hooks-dir is unset for root callers, Buildah currently defaults to /usr/share/containers/oci/hooks.d and /etc/containers/oci/hooks.d in order of increasing precedence. Using these defaults is deprecated. Migrate to explicitly setting --hooks-dir.
Project: ArangoDB (App Definition and Development / Database)
File: explicit_make_error_code_move_converting_constructor.md

+++ title = "`explicit basicresult(basicresult<R, S, P> &&)`" description = "Explicit converting move constructor from compatible `basicresult`. Available if `predicate::enablemakeerrorcodecompatibleconversion<R, S, P>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "explicit-constructors", "converting-constructors"] weight = 322 +++ Explicit converting move constructor from compatible `basicresult`. Calls {{% api "void onresultmoveconstruction(T *, U &&) noexcept" %}} with `this` and the input. Requires: `predicate::enablemakeerrorcodecompatible_conversion<R, S, P>` is true. Complexity: Same as for the move 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: secureCodeBox (Provisioning / Security & Compliance)
File: adr_README.md

<!-- SPDX-FileCopyrightText: the secureCodeBox authors SPDX-License-Identifier: Apache-2.0 --> This subdirectory contains all ADRs for the architecture documentation. The ids of these ADRs are within the number range from 0001 to 0999. The 0000 is reserved for the example template. Architectural decisions are, where appropriate, documented with the ADR template from . A template can be found at `adr_0000.md` and . We extend this template with the date when this decision was made. Important key points from the blog of : We will keep a collection of records for "architecturally significant" decisions: those that affect the structure, non-functional characteristics, dependencies, interfaces, or construction techniques. Each record describes a set of forces and a single decision in response to those forces. Note that the decision is the central piece here, so specific forces may appear in multiple ADRs. We will keep ADRs in the project repository under `adr/NNNN.md`. ADRs will be numbered sequentially and monotonically. Numbers will not be reused. If a decision is reversed, we will keep the old one around, but mark it as superseded. (It's still relevant to know that it was the decision, but is no longer the decision.) Please take a look in the ADR template `adr_0000.md` for more information about the internal structure.
Project: ClickHouse (App Definition and Development / Database)
File: v23.9.4.11-stable.md

sidebar_position: 1 sidebar_label: 2023 Fix wrong query result when httpwriteexceptioninoutput_format=1 (). Fix schema cache for fallback JSON->JSONEachRow with changed settings (). Fix a crash during table loading on startup (). Fix segfault in signal handler for Keeper (). Fix buffer overflow in T64 ().
Project: Meshery (Provisioning / Automation & Configuration)
File: multiple-of-the-same-adapter.md

layout: default title: Using Multiple Adapters permalink: installation/multiple-adapters redirect_from: guides/multiple-adapters type: guides category: operating language: en abstract: Meshery is capable of running zero or more adapters. Meshery offers many features without the need for adapters. Adapters are optional components that enhance and extend Meshery's core functionality. Meshery is capable of running zero or more adapters. Meshery offers many features without the need for adapters. Adapters are optional components that enhance and extend Meshery's core functionality. The number of adapters, type of adapters, where they are deployed, how they are named and what port they are exposed on are all configurable deployment options. To modify the default configuration, find `~/.meshery/meshery.yaml` on your system. `~/.meshery/meshery.yaml` is a Docker Compose file. To customize which Meshery Adapters are used in which deployments, customize your contexts in your meshconfig. Recommended: Configure your meshconfig, using `mesheryctl system context` to customize which Meshery Adapters are used in which deployments. Alternative: Alternatively, directly modify the `~/.meshery/meshery.yaml` configuration file, remove the entry(ies) of the adapter(s) you are removing from your deployment. The default configuration of a Meshery deployment includes one instance of each of the Meshery adapters (that have reached a stable version status). You may choose to run multiple instances of the same type of Meshery adapter; e.g. two instances of the Meshery Adapter for NGINX Service Mesh. To do so, you can use either of Meshery's clients or to modify your Meshery deployment: Using `mesheryctl`, modify `~/.meshery/meshery.yaml` to include multiple copies of the given adapter. Using Meshery UI, navigate to the Settings page and enter the host and port of your additional adapter. While installing mesheryctl using bash installation script, we can choose which adapter to be loaded. This is done by passing ADAPTERS environment variable to meshery bash script. For e.g. `curl -L https://meshery.io/install | ADAPTERS=consul PLATFORM=kubernetes bash -` installs mesheryctl and starts Meshery Server in your connected Kubernetes cluster deploying only the Meshery Adapter for Consul and not the rest of Meshery's adapters. <h5>Demo of Meshery managing deployments across multiple Kubernetes clusters:</h5> <iframe class="container" width="560" height="315" src="https://www.youtube.com/embed/yWPu3vq4vEs?start=5041" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> See on YouTube:
Project: YugabyteDB (App Definition and Development / Database)
File: expire.md

title: EXPIRE linkTitle: EXPIRE description: EXPIRE menu: preview: parent: api-yedis weight: 2061 aliases: /preview/api/redis/expire /preview/api/yedis/expire type: docs `EXPIRE key timeout` Set a timeout on key (in seconds). After the timeout has expired, the key will automatically be deleted. Returns integer reply, specifically 1 if the timeout was set and 0 if key does not exist. ```sh $ SET yugakey "Yugabyte" ``` ``` "OK" ``` ```sh $ EXPIRE yugakey 10 ``` ``` (integer) 1 ``` ```sh $ EXPIRE non-existent-key 10 ``` ``` (integer) 0 ``` , , ,
Project: KICS (Provisioning / Security & Compliance)
File: 9aa32890-ac1a-45ee-81ca-5164e2098556.md

title: NET_RAW Capabilities Disabled for PSP hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9aa32890-ac1a-45ee-81ca-5164e2098556 Query name: NET_RAW Capabilities Disabled for PSP Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Containers need to have NET_RAW or All as drop capabilities<br> ```tf title="Positive test num. 1 - tf file" hl_lines="17" resource "kubernetespodsecurity_policy" "example" { metadata { name = "terraform-example" } spec { privileged = false allowprivilegeescalation = false volumes = [ "configMap", "emptyDir", "projected", "secret", "downwardAPI", "persistentVolumeClaim", ] requireddropcapabilities = [ "KILL", "SYS_TIME", ] runasuser { rule = "MustRunAsNonRoot" } se_linux { rule = "RunAsAny" } supplemental_groups { rule = "MustRunAs" range { min = 1 max = 65535 } } fs_group { rule = "MustRunAs" range { min = 1 max = 65535 } } readonlyroot_filesystem = true } } ``` ```tf title="Negative test num. 1 - tf file" resource "kubernetespodsecurity_policy" "example" { metadata { name = "terraform-example" } spec { privileged = false allowprivilegeescalation = false volumes = [ "configMap", "emptyDir", "projected", "secret", "downwardAPI", "persistentVolumeClaim", ] requireddropcapabilities = [ "ALL" ] runasuser { rule = "MustRunAsNonRoot" } se_linux { rule = "RunAsAny" } supplemental_groups { rule = "MustRunAs" range { min = 1 max = 65535 } } fs_group { rule = "MustRunAs" range { min = 1 max = 65535 } } readonlyroot_filesystem = true } } ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_organization.md

+++ title = "google_organization resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "google_organization" identifier = "inspec/resources/gcp/googleorganization.md googleorganization resource" parent = "inspec/resources/gcp" +++ A `google_organization` is used to test a Google Organization resource ```ruby describe google_organization(name: "organizations/123456") do its('name') { should eq "organizations/123456" } its('lifecycle_state') { should cmp 'ACTIVE' } end ``` describe google_organization(name: 'organizations/1234') do its('name') { should eq 'organizations/1234' } end describe googleorganization(displayname: 'google.com') do its('lifecycle_state') { should eq "ACTIVE" } end Properties that can be accessed from the `google_organization` resource: `name` : The resource name of the organization. This is the organization's relative path in the API. Its format is "organizations/[organizationId]". For example, "organizations/1234". `display_name` : A human-readable string that refers to the Organization in the GCP Console UI. This string is set by the server and cannot be changed. The string will be set to the primary domain (for example, "google.com") of the G Suite customer that owns the organization. `lifecycle_state` : The lifecycle state of the folder. Updates to the lifecycleState must be performed via folders.delete and folders.undelete. Possible values: LIFECYCLESTATEUNSPECIFIED ACTIVE DELETE_REQUESTED `creation_time` : Timestamp when the Organization was created. Assigned by the server. `owner` : The entity that owns the Organization `directorycustomerid` : The G Suite customer id used in the Directory API Ensure the is enabled for the current project.
Project: ArangoDB (App Definition and Development / Database)
File: hook_result_copy_construction.md

+++ title = "`void hookresultcopy_construction(T *, U &&) noexcept`" description = "(Until v2.2.0) ADL discovered free function hook invoked by the converting copy constructors of `basic_result`." +++ Removed in Outcome v2.2.0, unless {{% api "BOOSTOUTCOMEENABLELEGACYSUPPORT_FOR" %}} is set to less than `220` to enable emulation. Use {{% api "onresultcopy_construction(T *, U &&) noexcept" %}} instead in new code. One of the constructor hooks for {{% api "basicresult<T, E, NoValuePolicy>" %}}, generally invoked by the converting copy constructors of `basicresult` (NOT the standard copy constructor). See each constructor's documentation to see which specific hook it invokes. Overridable: By Argument Dependent Lookup. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::hooks` Header: `<boost/outcome/basic_result.hpp>`
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: apply-object.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: server-with-pvc namespace: default spec: components: name: express-server type: webservice properties: image: oamdev/hello-world port: 8000 volumes: name: "my-pvc" type: "pvc" mountPath: "/test" claimName: "myclaim" workflow: steps: name: apply-pvc type: apply-object properties: value: apiVersion: v1 kind: PersistentVolumeClaim metadata: name: myclaim namespace: default spec: accessModes: ReadWriteOnce resources: requests: storage: 8Gi storageClassName: standard cluster: <your cluster name> name: apply-server type: apply-component properties: component: express-serve ```
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-provider-reset.md

layout: default title: mesheryctl-system-provider-reset permalink: reference/mesheryctl/system/provider/reset redirect_from: reference/mesheryctl/system/provider/reset/ type: reference display-title: "false" language: en command: system subcommand: provider reset provider to default Reset provider for current context to default (Meshery) <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system provider reset [flags] </div> </pre> Reset provider to default <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system provider reset </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for reset </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -c, --context string (optional) temporarily change the current context. -v, --verbose verbose output -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: PULL_REQUEST_TEMPLATE.md

copilot:all <!-- Briefly describe what this pull request does. We love pull requests that resolve an open KubeVela issue. If yours does, you can uncomment the below line to indicate which issue your PR fixes, for example "Fixes #500": --> Fixes # I have: . updated properly. In a new feature or configuration option, an update to the documentation is necessary. [ ] Run `make reviewable` to ensure this PR is ready for review. [ ] Added `backport release-x.y` labels to auto-backport this PR if necessary. <!-- Before reviewers can be confident in the correctness of this pull request, it needs to tested and shown to be correct. Briefly describe the testing that has already been done or which is planned for this change. --> <!-- Be sure to direct your reviewers' attention to anything that needs special consideration. -->
Project: Trivy (Provisioning / Security & Compliance)
File: php.md

Trivy supports , which is a tool for dependency management in PHP. The following scanners are supported. | Package manager | SBOM | Vulnerability | License | | | :: | :--: | :--: | | Composer | | | | The following table provides an outline of the features Trivy offers. | Package manager | File | Transitive dependencies | Dev dependencies | | Position | |--||:--:|:-:|::|:--:| | Composer | composer.lock | | Excluded | | | In order to detect dependencies, Trivy searches for `composer.lock`. Trivy also supports dependency trees; however, to display an accurate tree, it needs to know whether each package is a direct dependency of the project. Since this information is not included in `composer.lock`, Trivy parses `composer.json`, which should be located next to `composer.lock`. If you want to see the dependency tree, please ensure that `composer.json` is present.