cwielenb/CNCF-Dataset huggingface dataset:
Project: Trivy-Operator (Provisioning / Security & Compliance)
File: configaudit-report.md

An instance of the ConfigAuditReport represents the checks performed by configuration auditing tools, such as , against the configuration of a Kubernetes object. Example of checks are that a given container image is configured to run as non-root user or that a container has resource requests and limits set. Checks might relate to Kubernetes workloads and other namespaced Kubernetes objects such as Services, ConfigMaps, Roles, and RoleBindings. Each report is owned by the underlying Kubernetes object and is stored in the same namespace, following the `<workload-kind>-<workload-name>` naming convention. The following listing shows a sample ConfigAuditReport associated with the ReplicaSet named `nginx-6d4cf56db6` in the `default` namespace. ```yaml apiVersion: aquasecurity.github.io/v1alpha1 kind: ConfigAuditReport metadata: name: replicaset-nginx-6d4cf56db6 namespace: default labels: trivy-operator.resource.kind: ReplicaSet trivy-operator.resource.name: nginx-6d4cf56db6 trivy-operator.resource.namespace: default plugin-config-hash: 7f65d98b75 resource-spec-hash: 7cb64cb677 uid: d5cf8847-c96d-4534-beb9-514a34230302 ownerReferences: apiVersion: apps/v1 blockOwnerDeletion: false controller: true kind: ReplicaSet name: nginx-6d4cf56db6 uid: aa345200-cf24-443a-8f11-ddb438ff8659 report: updateTimestamp: '2021-05-20T12:38:10Z' scanner: name: Trivy vendor: Aqua Security version: '0.20.1' summary: criticalCount: 2 highCount: 0 lowCount: 9 mediumCount: 0 checks: category: Security checkID: hostPIDSet messages: Host PID is not configured severity: CRITICAL success: true category: Security checkID: hostIPCSet messages: Host IPC is not configured severity: CRITICAL success: true category: Security checkID: hostNetworkSet messages: Host network is not configured severity: LOW success: true category: Security checkID: notReadOnlyRootFilesystem messages: Filesystem should be read only scope: type: Container value: nginx severity: LOW success: false category: Security checkID: privilegeEscalationAllowed messages: Privilege escalation should not be allowed scope: type: Container value: nginx severity: CRITICAL success: false ``` Third party Kubernetes configuration checkers, linters, and sanitizers that are compliant with the ConfigAuditReport schema can be integrated with trivy-operator. !!! note The challenge with onboarding third party configuration checkers is that they tend to have different interfaces to perform scans and vary in output formats for a relatively common goal, which is inspecting deployment descriptors for known configuration pitfalls.
Project: FOSSA (Provisioning / Security & Compliance)
File: add-projects.md

`fossa release-group add-projects` allows you to add FOSSA projects to a FOSSA release group. Argument | Required | Description -|-|-- `--config` / `-c` | No | The to your path to your `.fossa.yml`. `--title` / `-t ` | Yes | The name of your FOSSA release group. `--release` / `-r ` | Yes | The name of your release within your FOSSA release group. `--project-locator` | Yes | The FOSSA project locator defines a unique ID that the FOSSA API will use to reference this project. The project locator can be found in the UI on the project `Settings` page listed as the `Project Locator` underneath the `Project Title` setting. Specify multiple options by providing this argument multiple times. `--project-revision` | Yes | The revision associated with your FOSSA project. Project revisions can be found in the UI on the project `Activity` page. Refer to `Revision ID` to retrieve the specific revision you want to use for the project. Specify multiple options by providing this argument multiple times. `--project-branch` | Yes | The name of the FOSSA project branch. Specify multiple options by providing this argument multiple times. NOTE: The arguments listed as `Required` need to be provided through CLI options OR through your `.fossa.yml` configuration. Refer to to set up your `.fossa.yml`. NOTE: CLI options take precedence over the configurations in `.fossa.yml`. NOTE: Project ID values will not work if provided to `releaseGroupProjects.projectLocator`. For more details on the differences between project ID and project locator refer to . ```bash fossa release-group add-projects --title example-release-group --release example-release --project-locator custom+1/example --project-revision 1234 --project-branch main --project-locator custom+1/example2 --project-revision 5678 --project-branch main ``` NOTE: `--project-locator` , `--project-revision`, and `--project-branch` must all be specified when providing a releaseGroupProject. Multiple occurrences of these arguements are accepted and are grouped together based on their order. For example, `fossa release-group add-projects --title example-release-group --release example-release --project-locator custom+1/example --project-revision 1234 --project-branch main --project-locator custom+1/example2 --project-revision 5678 --project-branch main` has project groupings of (project locator: custom+1/example, project revision: 1234, project branch: main) and (project locator: custom+1/example2, project revision: 5678, project branch: main). Similarly, you can you achieve the same result by running the following command with the given `.fossa.yml` configuration: ```yaml releaseGroup: title: example-release-group release: example-release releaseGroupProjects: projectLocator: custom+1/example projectRevision: 1234 projectBranch: main projectLocator: custom+1/example2 projectRevision: 5678 projectBranch: main ``` ```bash fossa release-group add-projects -c path/to/config ```
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_remove_sync.md

title: "Command - devspace remove sync" sidebar_label: devspace remove sync Remove sync paths from the devspace ``` devspace remove sync [flags] ``` ``` Remove sync paths from the devspace How to use: devspace remove sync --local=app devspace remove sync --container=/app devspace remove sync --label-selector=release=test devspace remove sync --all ``` ``` --all Remove all configured sync paths --container string Absolute container path to remove -h, --help help for sync --label-selector string Comma separated key=value selector list (e.g. release=test) --local string Relative local path to remove ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile string The devspace profile to use (if there is any) --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```
Project: Parsec (Provisioning / Security & Compliance)
File: SECURITY.md

Security is of paramount importance to the Parsec project. We do all we can to identify and fix issues, however some problems might slip through the cracks. Any efforts towards responsible disclosure of security problems are greatly appreciated and your contributions will be acknowledged. Currently only the most recent version of the Parsec service is eligible for patching. This could change in the future. | Version | Supported | ||--| | 0.7.0 and higher | | | 0.6.0 and lower | | All security vulnerabilities affecting the Parsec service - including those reported using the steps highlighted below, those discovered during routine testing, and those found in our dependency tree either through `cargo-audit` or otherwise - will receive [security advisories](https://github.com/parallaxsecond/parsec/security/advisories) in a timely manner. The advisories should include sufficient information about the cause, effect, and possible mitigations for the vulnerability. If any information is missing, or you would like to raise a question about the advisories, please open an issue in . Efforts to mitigate for the reported vulnerabilities will be tracked using Github issues linked to the corresponding advisories. To report a vulnerability, please send an email to . We will reply to acknowledge your report and we'll strive to keep you in the loop as we try to reach a resolution.
Project: ShardingSphere (App Definition and Development / Database)
File: sql-translator.en.md

+++ title = "SQL Translator" weight = 9 +++ The SQL translator YAML configuration is readable and easy to use. The YAML files allow you to separate the code from the configuration, and easily modify the configuration file as needed. ```yaml sqlTranslator: type: # SQL translator type useOriginalSQLWhenTranslatingFailed: # Whether use original SQL when translating failed ``` Set SQL translator type. Set useOriginalSQLWhenTranslatingFailed to decide whether use original SQL when translating failed. ```yaml sqlTranslator: type: Native useOriginalSQLWhenTranslatingFailed: true ```
Project: YugabyteDB (App Definition and Development / Database)
File: rule-3.md

title: Rule 3 (for string intended to specify the UTC offset) [YSQL] headerTitle: Rule 3 linkTitle: 3 'set timezone' string not resolved in ~abbrevs.abbrev description: Substantiates the rule that a string that's intended to identify a UTC offset is never resolved in pgtimezoneabbrevs.abbrev as the argument of 'set timezone' but is resolved there as the argument of 'timezone()' and within a 'text' literal for a 'timestamptz' value. [YSQL] menu: v2.18: identifier: rule-3 parent: name-res-rules weight: 30 type: docs {{< tip title="" >}} A string that's intended to identify a UTC offset is never resolved in pgtimezoneabbrevs.abbrev as the argument of set timezone but is resolved there as the argument of at time zone (and, equivalently, in timezone()) and as the argument of maketimestamptz() (and equivalently within a text literal for a timestamptz_ value). {{< /tip >}} You can discover, with ad hoc queries. that the string AZOT occurs uniquely in pgtimezonenames.abbrev. Use the function to confirm it thus: ```plpgsql with c as (select occurrences('AZOT') as r) select (c.r).names_name ::text as "~names.name", (c.r).names_abbrev ::text as "~names.abbrev", (c.r).abbrevs_abbrev ::text as "~abbrevs.abbrev" from c; ``` This is the result: ```output ~names.name | ~names.abbrev | ~abbrevs.abbrev -++-- false | false | true ``` This means that the string AZOT can be used as a probe, using the function _: ```plpgsql select x from legalscopesforsyntaxcontext('AZOT'); ``` This is the result: ```output AZOT: namesname: false / namesabbrev: false / abbrevs_abbrev: true set timezone = 'AZOT'; > invalidparametervalue select timezone('AZOT', '2021-06-07 12:00:00'); > OK select '2021-06-07 12:00:00 AZOT'::timestamptz; > OK ``` You can copy-and-paste the offending expression and use it as the argument of a select to see the error occurring "live". This outcome supports the formulation of the rule that this page addresses.
Project: external-secrets (Provisioning / Security & Compliance)
File: templating-v1.md

!!! warning Templating Engine v1 is deprecated and will be removed in the future. Please migrate to engine v2 and take a look at our for changes. With External Secrets Operator you can transform the data from the external secret provider before it is stored as `Kind=Secret`. You can do this with the `Spec.Target.Template`. Each data value is interpreted as a . Please note that referencing a non-existing key in the template will raise an error, instead of being suppressed. You can use templates to inject your secrets into a configuration file that you mount into your pod: ``` yaml {% include 'multiline-template-v1-external-secret.yaml' %} ``` You can also use pre-defined functions to extract data from your secrets. Here: extract key/cert from a pkcs12 archive and store it as PEM. ``` yaml {% include 'pkcs12-template-v1-external-secret.yaml' %} ``` You do not have to define your templates inline in an ExternalSecret but you can pull `ConfigMaps` or other Secrets that contain a template. Consider the following example: ``` yaml {% include 'template-v1-from-secret.yaml' %} ``` We provide a bunch of convenience functions that help you transform your secrets. A secret value is a `[]byte`. | Function | Description | Input | Output | | -- | -- | -- | - | | pkcs12key | extracts the private key from a pkcs12 archive | `[]byte` | `[]byte` | | pkcs12keyPass | extracts the private key from a pkcs12 archive using the provided password | password `string`, data `[]byte` | `[]byte` | | pkcs12cert | extracts the certificate from a pkcs12 archive | `[]byte` | `[]byte` | | pkcs12certPass | extracts the certificate from a pkcs12 archive using the provided password | password `string`, data `[]byte` | `[]byte` | | pemPrivateKey | PEM encodes the provided bytes as private key | `[]byte` | `string` | | pemCertificate | PEM encodes the provided bytes as certificate | `[]byte` | `string` | | jwkPublicKeyPem | takes an json-serialized JWK as `) for details | `[]byte` | `string` | | jwkPrivateKeyPem | takes an json-serialized JWK as `) for details | `[]byte` | `string` | | base64decode | decodes the provided bytes as base64 | `[]byte` | `[]byte` | | base64encode | encodes the provided bytes as base64 | `[]byte` | `[]byte` | | fromJSON | parses the bytes as JSON so you can access individual properties | `[]byte` | `any` | | toJSON | encodes the provided object as json string | `any` | `string` | | toString | converts bytes to string | `[]byte` | `string` | | toBytes | converts string to bytes | `string` | `[]byte` | | upper | converts all characters to their upper case | `string` | `string` | | lower | converts all character to their lower case | `string` | `string` |
Project: StarRocks (App Definition and Development / Database)
File: SHOW_TABLE_STATUS.md

displayed_sidebar: "English" This statement is used to view some of the information in Table. :::tip This operation does not require privileges. ::: ```sql SHOW TABLE STATUS [FROM db] [LIKE "pattern"] ``` Note This statement is mainly compatible with MySQL syntax. At present, it only shows a few information, such as Comment. View all the information of tables under the current database. ```SQL SHOW TABLE STATUS; ``` View all the information of tables whose names contain example and who are under specified databases. ```SQL SHOW TABLE STATUS FROM db LIKE "%example%"; ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.11-patch.1.md

layout: release date: 2024-01-17 tag: v0.7.11-patch.1 [MeshModel Category] Database category icon added @ritiksaxena124 (#10006) Thank you to our contributors for making this release possible: @leecalcote and @ritiksaxena124
Project: Stolon (App Definition and Development / Database)
File: commands_invocation.md

There are 4 commands provided by stolon: every command has different options and when called without any option or with `--help` they'll show an help with a description for every subcommand and option. Please take also a look at the various examples to see how the commands' options are used. An option can be specified in the command line or as an environment variables. Environment variables are prefixed with a string related to the command and take the name of the options but are UPPERCASE and any dashes are replaced by underscores. For example for the `stolon-keeper` `--data-dir` command line option the equivalent environment variable is `STKEEPERDATADIR` | Command | Environment variable prefix | |--|--| | stolon-keeper | STKEEPER | | stolon-sentinel | STSENTINEL | | stolon-proxy | STPROXY | | stolonctl | STOLONCTL |
Project: YugabyteDB (App Definition and Development / Database)
File: echo.md

title: ECHO linkTitle: ECHO description: ECHO menu: preview: parent: api-yedis weight: 2050 aliases: /preview/api/redis/echo /preview/api/yedis/del type: docs `ECHO message` This command outputs the given `message`. Returns the message. ```sh $ ECHO "Yuga Yuga" ``` ```output "Yuga Yuga" ```
Project: ArangoDB (App Definition and Development / Database)
File: operator_bool.md

+++ title = "`explicit operator bool() const noexcept`" description = "Returns true if a value is present. Constexpr, never throws." categories = ["observers"] weight = 590 +++ Returns true if a value is present. Constexpr where possible. Alias for {{% api "bool has_value() const noexcept" %}}. Requires: Always available. Complexity: Constant time. Guarantees: Never throws an exception.
Project: CockroachDB (App Definition and Development / Database)
File: bug_report.md

name: 'Bug or crash report' title: '' about: 'Report unexpected behavior to help us improve' labels: 'C-bug' assignees: '' Describe the problem Please describe the issue you observed, and any steps we can take to reproduce it: To Reproduce What did you do? Describe in your own words. If possible, provide steps to reproduce the behavior: Set up CockroachDB cluster ... Send SQL ... / CLI command ... Look at UI / log file / client app ... See error Expected behavior A clear and concise description of what you expected to happen. Additional data / screenshots If the problem is SQL-related, include a copy of the SQL query and the schema of the supporting tables. If a node in your cluster encountered a fatal error, supply the contents of the log directories (at minimum of the affected node(s), but preferably all nodes). Note that log files can contain confidential information. Please continue creating this issue, but contact support@cockroachlabs.com to submit the log files in private. If applicable, add screenshots to help explain your problem. Environment: CockroachDB version [e.g. 2.0.x] Server OS: [e.g. Linux/Distrib] Client app [e.g. `cockroach sql`, JDBC, ...] Additional context What was the impact? Add any other context about the problem here.
Project: YDB (App Definition and Development / Database)
File: find.md

Finding the position of a substring in a string. Required arguments: Source string; The substring being searched for. Optional arguments: A position in bytes to start the search with (an integer or `NULL` by default that means "from the beginning of the source string"). Returns the first substring position found or `NULL` (meaning that the desired substring hasn't been found starting from the specified position). Examples ```yql SELECT FIND("abcdefg_abcdefg", "abc"); -- 0 ``` ```yql SELECT FIND("abcdefg_abcdefg", "abc", 1); -- 8 ``` ```yql SELECT FIND("abcdefg_abcdefg", "abc", 9); -- null ``` Reverse finding the position of a substring in a string, from the end to the beginning. Required arguments: Source string; The substring being searched for. Optional arguments: A position in bytes to start the search with (an integer or `NULL` by default, meaning "from the end of the source string"). Returns the first substring position found or `NULL` (meaning that the desired substring hasn't been found starting from the specified position). Examples ```yql SELECT RFIND("abcdefg_abcdefg", "bcd"); -- 9 ``` ```yql SELECT RFIND("abcdefg_abcdefg", "bcd", 8); -- 1 ``` ```yql SELECT RFIND("abcdefg_abcdefg", "bcd", 0); -- null ```
Project: YugabyteDB (App Definition and Development / Database)
File: flushall.md

title: FLUSHALL linkTitle: FLUSHALL description: FLUSHALL menu: preview: parent: api-yedis weight: 2064 aliases: /preview/api/redis/flushall /preview/api/yedis/flushall type: docs `FLUSHALL` This command deletes all keys from all databases. This functionality can be disabled by setting the yb-tserver `--yedisenableflush` flag to `false`. Returns status string. ```sh $ SET yuga1 "America" ``` ``` "OK" ``` ```sh $ SET yuga2 "Africa" ``` ``` "OK" ``` ```sh $ GET yuga1 ``` ``` "America" ``` ```sh $ GET yuga2 ``` ``` "Africa" ``` ```sh $ FLUSHALL ``` ``` "OK" ``` ```sh $ GET yuga1 ``` ``` (null) ``` ```sh $ GET yuga2 ``` ``` (null) ``` ,
Project: KICS (Provisioning / Security & Compliance)
File: 95588189-1abd-4df1-9588-b0a5034f9e87.md

title: Missing App Armor Config hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 95588189-1abd-4df1-9588-b0a5034f9e87 Query name: Missing App Armor Config Platform: Pulumi Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Containers should be configured with AppArmor for any application to reduce its potential attack<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8 25 42" name: yaml-example description: Create a Pod with auto-naming runtime: yaml resources: pod: type: kubernetes:core/v1:Pod properties: metadata: annotations: spec: containers: image: nginx:1.14.2 name: nginx ports: containerPort: 80 type: kubernetes:core/v1:Pod name: yaml-example description: Create a Pod with auto-naming runtime: yaml resources: pod: type: kubernetes:core/v1:Pod properties: metadata: spec: containers: image: nginx:1.14.2 name: nginx ports: containerPort: 80 type: kubernetes:core/v1:Pod name: yaml-example description: Create a Pod with auto-naming runtime: yaml resources: pod: type: kubernetes:core/v1:Pod properties: metadata: annotations: container.notapparmor.security.beta.kubernetes.io: localhost/k8s-apparmor-example-allow-write spec: containers: image: nginx:1.14.2 name: nginx ports: containerPort: 80 type: kubernetes:core/v1:Pod ``` ```yaml title="Negative test num. 1 - yaml file" name: yaml-example description: Create a Pod with auto-naming runtime: yaml resources: pod: type: kubernetes:core/v1:Pod properties: metadata: annotations: container.apparmor.security.beta.kubernetes.io: localhost/k8s-apparmor-example-allow-write container.apparmor.security.beta.kubernetes.io2: localhost/k8s-apparmor-example-allow-write spec: containers: image: nginx:1.14.2 name: nginx ports: containerPort: 80 type: kubernetes:core/v1:Pod ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: upstart_service.md

+++ title = "upstart_service resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "upstart_service" identifier = "inspec/resources/os/upstartservice.md upstartservice resource" parent = "inspec/resources/os" +++ Use the `upstart_service` Chef InSpec audit resource to test a service using Upstart. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. An `upstart_service` resource block declares the name of a service and then one (or more) matchers to test the state of the service: describe upstartservice('servicename') do it { should be_installed } it { should be_enabled } it { should be_running } end where `('service_name')` must specify a service name `beinstalled`, `beenabled`, and `be_running` are valid matchers for this resource; all matchers available to the `service` resource may be used The path to the service manager's control may be specified for situations where the path isn't available in the current `PATH`. For example: describe upstartservice('servicename', '/path/to/control') do it { should be_enabled } it { should be_installed } it { should be_running } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The `be_enabled` matcher tests if the named service is enabled: it { should be_enabled } The `be_installed` matcher tests if the named service is installed: it { should be_installed } The `be_running` matcher tests if the named service is running: it { should be_running }
Project: YugabyteDB (App Definition and Development / Database)
File: psubscribe.md

title: PSUBSCRIBE linkTitle: PSUBSCRIBE description: PSUBSCRIBE menu: preview: parent: api-yedis weight: 2554 aliases: /preview/api/redis/psubscribe /preview/api/yedis/psubscribe type: docs `PSUBSCRIBE pattern [pattern ...]` This command subscribes the client to the specified pattern(s). The client will receive a message whenever a publisher sends a message to a channel that matches any of the patterns that it has subscribed to. , , , , , ,