cwielenb/CNCF-Dataset huggingface dataset:
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_sql_user.md

+++ title = "googlesqluser resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlesqluser" identifier = "inspec/resources/gcp/googlesqluser.md googlesqluser resource" parent = "inspec/resources/gcp" +++ A `googlesqluser` is used to test a Google User resource ```ruby describe googlesqluser(project: 'chef-gcp-inspec', database: 'my-database', name: 'user-name', host: "example.com") do it { should exist } its('name') { should cmp 'user-name' } its('instance') { should cmp 'my-database' } end describe googlesqluser(project: 'chef-gcp-inspec', database: 'my-database', name: "nonexistent", host: "example.com") do it { should_not exist } end ``` Properties that can be accessed from the `googlesqluser` resource: `host` : The host name from which the user can connect. For insert operations, host defaults to an empty string. For update operations, host is specified as part of the request URL. The host name cannot be updated after insertion. `name` : The name of the user in the Cloud SQL instance. `instance` : The name of the Cloud SQL instance. This does not include the project ID. `password` : The password for the user. Ensure the is enabled for the current project.
Project: Trivy (Provisioning / Security & Compliance)
File: suse.md

Trivy supports the following distributions: openSUSE Leap SUSE Enterprise Linux (SLE) Please see for supported versions. Trivy supports these scanners for OS packages. | Scanner | Supported | | :--: | :-: | | SBOM | | | Vulnerability | | | License | | The table below outlines the features offered by Trivy. | Feature | Supported | |::|::| | Unfixed vulnerabilities | - | | | | Trivy detects packages that have been installed through package managers such as `dnf` and `yum`. SUSE offers its , and these are utilized when scanning openSUSE/SLE for vulnerabilities. See . Trivy identifies licenses by examining the metadata of RPM packages.
Project: Topaz (Provisioning / Security & Compliance)
File: MAINTAINERS.md

The following table lists Topaz project maintainers and areas of expertise in alphabetical order: | Name | GitHub | Email | Organization | Repositories/Area of Expertise | Added/Renewed On | | | | | | | | | Dani Carabas | @carabasdaniel | dani@aserto.com | Aserto | all repositories | 2022-10-23 | | Gert Drapers | @gertd | gert@aserto.com | Aserto | all repositories | 2022-10-23 |
Project: Stolon (App Definition and Development / Database)
File: stolonctl_status.md

Display the current cluster status Display the current cluster status ``` stolonctl status [flags] ``` ``` -f, --format string output format -h, --help help for status ``` ``` --cluster-name string cluster name --kube-context string name of the kubeconfig context to use --kube-namespace string name of the kubernetes namespace to use --kube-resource-kind string the k8s resource kind to be used to store stolon clusterdata and do sentinel leader election (only "configmap" is currently supported) --kubeconfig string path to kubeconfig file. Overrides $KUBECONFIG --log-level string debug, info (default), warn or error (default "info") --metrics-listen-address string metrics listen address i.e "0.0.0.0:8080" (disabled by default) --store-backend string store backend type (etcdv2/etcd, etcdv3, consul or kubernetes) --store-ca-file string verify certificates of HTTPS-enabled store servers using this CA bundle --store-cert-file string certificate file for client identification to the store --store-endpoints string a comma-delimited list of store endpoints (use https scheme for tls communication) (defaults: http://127.0.0.1:2379 for etcd, http://127.0.0.1:8500 for consul) --store-key string private key file for client identification to the store --store-prefix string the store base prefix (default "stolon/cluster") --store-skip-tls-verify skip store certificate verification (insecure!!!) --store-timeout duration store request timeout (default 5s) ``` - stolon command line client
Project: StarRocks (App Definition and Development / Database)
File: sinh.md

displayed_sidebar: "English" Computes the hyperbolic sine of the argument. This function is supported from v3.0. ```Haskell DOUBLE sinh(DOUBLE arg) ``` `arg`: You can specify only a numeric value. This function converts the numeric value into a DOUBLE value before it computes the hyperbolic sine of the value. Returns a value of the DOUBLE data type. If you specify a non-numeric value, this function returns `NULL`. ```Plain mysql> select sinh(-1); ++ | sinh(-1) | ++ | -1.1752011936438014 | ++ mysql> select sinh(0); ++ | sinh(0) | ++ | 0 | ++ mysql> select sinh(1); +--+ | sinh(1) | +--+ | 1.1752011936438014 | +--+ mysql> select sinh(""); +-+ | sinh('') | +-+ | NULL | +-+ ``` SINH
Project: ClickHouse (App Definition and Development / Database)
File: sample-by.md

slug: /en/sql-reference/statements/alter/sample-by sidebar_position: 41 sidebar_label: SAMPLE BY title: "Manipulating Sampling-Key Expressions" The following operations are available: ``` sql ALTER TABLE [db].name [ON CLUSTER cluster] MODIFY SAMPLE BY new_expression ``` The command changes the of the table to `new_expression` (an expression or a tuple of expressions). The primary key must contain the new sample key. ``` sql ALTER TABLE [db].name [ON CLUSTER cluster] REMOVE SAMPLE BY ``` The command removes the of the table. The commands `MODIFY` and `REMOVE` are lightweight in the sense that they only change metadata or remove files. :::note It only works for tables in the family (including tables). :::
Project: Quay (Provisioning / Container Registry)
File: prometheus.md

[Prometheus] is a time series database used for the short-term storage of metrics. Quay exposes numerous metrics that can be used to ensure the performance and reliability while the application is running. Because Quay is actually a collection of processes inside the container, [PushGateway] is used to consolidate, but not aggregate, all of the metrics into one endpoint. A grouping key of `(pid, host, process_name)` is added to every metric in ordered to keep every metric unique per process. This grouping key does cause high cardinality for sufficiently large deployments and aggregation using a federated deployment of Prometheus is then recommended. The metrics endpoint can be found on the [PushGateway port]: `9091`. [Brian's post] on cardinality is required reading before defining your first metric. The cardinality of the set of labels on a metric can destroy querying performance to the degree where the metric is unusable. In newer versions of Prometheus, expensive queries will timeout, but in older versions it can make the whole Prometheus process hang. Abstractions useful for instrumenting new code with metrics can be found in [`/util/metrics`]. This module also contains a [flask extension] that pushes metrics on a regular interval from the default [registry] in the Prometheus client library to the PushGateway. Adding a new metric should roughly follow the process described by the Prometheus [client library README]: define a new metric in the module being instrumented, and call the respective functions to record the metric.
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk_edit.md

title: "operator-sdk edit" Update the project configuration This command will edit the project configuration. Features supported: Toggle between single or multi group projects. ``` operator-sdk edit [flags] ``` ``` operator-sdk edit --multigroup operator-sdk edit --multigroup=false ``` ``` -h, --help help for edit --multigroup enable or disable multigroup layout ``` ``` --plugins strings plugin keys to be used for this subcommand execution --verbose Enable verbose logging ``` -
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_aws.md

Manage a YugabyteDB Anywhere AWS provider Manage an AWS provider in YugabyteDB Anywhere ``` yba provider aws [flags] ``` ``` -n, --name string [Optional] The name of the provider for the action. Required for create, delete, describe, update. -h, --help help for aws ``` ``` -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") -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 YugabyteDB Anywhere providers - Create an AWS YugabyteDB Anywhere provider - Delete an AWS YugabyteDB Anywhere provider - Describe an AWS YugabyteDB Anywhere provider - List AWS YugabyteDB Anywhere providers - Update an AWS YugabyteDB Anywhere provider
Project: KICS (Provisioning / Security & Compliance)
File: 7db727c1-1720-468e-b80e-06697f71e09e.md

title: ECS Service Admin Role Is Present hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7db727c1-1720-468e-b80e-06697f71e09e Query name: ECS Service Admin Role Is Present Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: ECS Services must not have Admin roles, which means the attribute 'role' must not be an admin role<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="9" name: ECS Service community.aws.ecs_service: state: present name: console-test-service cluster: new_cluster taskdefinition: 'newcluster-task:1' desired_count: 0 role: admin ``` ```yaml title="Negative test num. 1 - yaml file" name: ECS Service community.aws.ecs_service: state: present name: console-test-service cluster: new_cluster taskdefinition: newcluster-task:1 desired_count: 0 ```
Project: YugabyteDB (App Definition and Development / Database)
File: tableplus.md

title: Use TablePlus with YugabyteDB YSQL and YCQL headerTitle: TablePlus linkTitle: TablePlus description: Learn how to connect TablePlus to YugabyteDB and query using YSQL, YCQL, and YEDIS. menu: v2.18: identifier: tableplus parent: tools weight: 50 type: docs is a popular database developer console with built-in integrations with major databases including PostgreSQL, Cassandra, and Redis. It is free to get started with the option of upgrading to a . TablePlus works with YugabyteDB without any issues because the YugabyteDB APIs are compatible at the wire protocol level with databases already supported by TablePlus. This tutorial shows how to connect TablePlus to a YugabyteDB cluster. Your YugabyteDB cluster should be up and running. Refer to . Note that if you are connecting to a YCQL keyspace that has tables with columns of type JSONB, because the Cassandra driver used by TablePlus does not support JSONB, the connection to the database may fail. To install TablePlus, go to the and select the version for your operating system. You can use TablePlus to connect to YugabyteDB using the YSQL and YCQL APIs. To create a connection, do the following: In TablePlus, from the Connection menu, choose New. Select PostgreSQL for YSQL, or Cassandra for YCQL, and click Create. Enter a Name for the connection and fill in the . Click Test to verify that TablePlus can connect with YugabyteDB. The color of the fields changes to green if the test succeeds. Click Connect to create the connection. Connections are saved in the application, and displayed every time you start TablePlus. <!--## Connect with Redis-compatible YEDIS Repeat the above steps for the Redis type as shown below. --> To get started with TablePlus, follow the instructions in . <!--## Known issue Following is a known issue that we hope to address soon. You can track the issue directly on GitHub. -->
Project: ClickHouse (App Definition and Development / Database)
File: session_log.md

slug: /en/operations/system-tables/session_log Contains information about all successful and failed login and logout events. Columns: `hostname` () Hostname of the server executing the query. `type` () Login/logout result. Possible values: `LoginFailure` Login error. `LoginSuccess` Successful login. `Logout` Logout from the system. `auth_id` () Authentication ID, which is a UUID that is automatically generated each time user logins. `session_id` () Session ID that is passed by client via interface. `event_date` () Login/logout date. `event_time` () Login/logout time. `eventtimemicroseconds` () Login/logout starting time with microseconds precision. `user` () User name. `auth_type` () The authentication type. Possible values: `NO_PASSWORD` `PLAINTEXT_PASSWORD` `SHA256_PASSWORD` `DOUBLESHA1PASSWORD` `LDAP` `KERBEROS` `SSL_CERTIFICATE` `profiles` (()) The list of profiles set for all roles and/or users. `roles` (()) The list of roles to which the profile is applied. `settings` (((, ))) Settings that were changed when the client logged in/out. `client_address` () The IP address that was used to log in/out. `client_port` () The client port that was used to log in/out. `interface` () The interface from which the login was initiated. Possible values: `TCP` `HTTP` `gRPC` `MySQL` `PostgreSQL` `client_hostname` () The hostname of the client machine where the or another TCP client is run. `client_name` () The `clickhouse-client` or another TCP client name. `client_revision` () Revision of the `clickhouse-client` or another TCP client. `clientversionmajor` () The major version of the `clickhouse-client` or another TCP client. `clientversionminor` () The minor version of the `clickhouse-client` or another TCP client. `clientversionpatch` () Patch component of the `clickhouse-client` or another TCP client version. `failure_reason` () The exception message containing the reason for the login/logout failure. Example Query: ``` sql SELECT * FROM system.session_log LIMIT 1 FORMAT Vertical; ``` Result: ``` text Row 1: hostname: clickhouse.eu-central1.internal type: LoginSuccess auth_id: 45e6bd83-b4aa-4a23-85e6-bd83b4aa1a23 session_id: event_date: 2021-10-14 event_time: 2021-10-14 20:33:52 eventtimemicroseconds: 2021-10-14 20:33:52.104247 user: default authtype: PLAINTEXTPASSWORD profiles: ['default'] roles: [] settings: [('loadbalancing','random'),('maxmemory_usage','10000000000')] client_address: ::ffff:127.0.0.1 client_port: 38490 interface: TCP client_hostname: client_name: ClickHouse client client_revision: 54449 clientversionmajor: 21 clientversionminor: 10 clientversionpatch: 0 failure_reason: ```
Project: FOSSA (Provisioning / Security & Compliance)
File: pull_request_template.md

Provide an overview of this change. Describe the intent of this change, and how it implements that intent. Example: This PR accomplishes X by doing Y. If this PR is successful, what impact does it have on the user experience? Example: When users do X, Y should now happen. How did you validate that this PR works? What literal steps did you take when manually checking that your code works? Example: Set up test case X. Run command Y. Make sure Z happens. This section should list concrete steps that a reviewer can sanity check and repeat on their own machine (and provide any needed test cases). Highlight any areas that you're unsure of, want feedback on, or want reviewers to pay particular attention to. Example: I'm not sure I did X correctly, can reviewers please double-check that for me? Is this change something that can or should be tracked? If so, can we do it today? And how? If its easy, do it Add links to any referenced GitHub issues, Zendesk tickets, Jira tickets, Slack threads, etc. Example: : Implement X. [ ] I added tests for this PR's change (or explained in the PR description why tests don't make sense). [ ] If this PR introduced a user-visible change, I added documentation into `docs/`. [ ] If this PR added docs, I added links as appropriate to the user manual's ToC in `docs/README.ms` and gave consideration to how discoverable or not my documentation is. [ ] If this change is externally visible, I updated `Changelog.md`. If this PR did not mark a release, I added my changes into an `# Unreleased` section at the top. [ ] If I made changes to `.fossa.yml` or `fossa-deps.{json.yml}`, I updated `docs/references/files/*.schema.json` AND I have updated example files used by `fossa init` command. You may also need to update these if you have added/removed new dependency type (e.g. `pip`) or analysis target type (e.g. `poetry`). [ ] If I made changes to a subcommand's options, I updated `docs/references/subcommands/<subcommand>.md`.
Project: Checkov (Provisioning / Security & Compliance)
File: best_practices_issue.md

name: Best practices improvement about: Issues that will help achieve best practices using checkov. title: '' labels: 'best practices' assignees: '' Describe the issue If it is related to an existing check, please note the relevant check ID. Also, explain the logic for this addition / change. Examples Please share an example code sample (in the IaC of your choice) + the expected outcomes. Version (please complete the following information): Checkov Version [e.g. 22] Additional context Add any other context about the problem here.
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: discussion.md

name: Discussion about: Start a discussion for Dapr title: '' labels: kind/discussion assignees: '' <!-- If you need to report a security issue please visit https://docs.dapr.io/operations/support/support-security-issues --> <!-- Please visit https://aka.ms/dapr-discord to ask questions and troubleshoot. For all other design discussions please continue. -->
Project: Chef Infra (Provisioning / Automation & Configuration)
File: client_exit_codes.md

Chef-client exit codes signal outside tools to the result of the Chef-Client run. As a Chef user, I want to be able to determine when a chef-client run is rebooting the node, so that Test-Kitchen/Vagrant/any outside tool can wait for the node to reboot, and continue converging. Chef applications (e.g. chef-client) that interpret recipes should use the specified exit codes Chef tools (e.g. knife) should behave appropriately for the exit code, or pass it to the user Windows- .aspx) Linux - , All exit codes defined should be usable on all supported Chef Platforms. Also, the exit codes used should be identical across all platforms. That limits the total range from 1-255. Exit codes not explicitly used by Linux/Windows are listed below. There are 59 exit codes that are available on both platforms. Any numbers below that have a strike-through are used below in the Exit Codes in Use* section Exit Codes Available for Chef use : 35,37,40,41,42,43,44,45,46,47,48,49,79,81,90,91,92,93,94,95,96,97 98,99,115,116,168,169,172,175,176,177,178,179,181,184,185,204,211 213,219,227,228,235,236,237,238,239,241,242,243,244,245 Reboot exit codes should take precedence over Chef Execution State Precedence within a table should be evaluated from the top down. Exit Code | Reason | Details | - |-- 35 | Reboot Scheduled | Reboot has been scheduled in the run state 37 | Reboot Needed | Reboot needs to be completed 41 | Reboot Failed | Initiated Reboot failed - due to permissions or any other reason Exit Code | Reason | Details | - |-- -1 | Failed execution* | Generic error during Chef execution. On Linux this will show up as 255, on Windows as -1 0 | Successful run | Any successful execution of a Chef utility should return this exit code 1 | Failed execution | Generic error during Chef execution. 2 | SIGINT received | Received an interrupt signal 3 | SIGTERM received | Received an terminate signal 42 | Audit Mode Failure | Audit mode failed, but chef converged successfully. 43 | Invalid config | Exit due to invalid configuration 213 | Client upgrade | Chef has exited during a client upgrade \Next release should deprecate any use of this exit code. If there is a need for additional exit codes, please open a Design Proposal PR to discuss the change, and then a PR to update this document.
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: kustomize-json-patch.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: bucket-app spec: components: name: bucket-comp type: kustomize traits: type: kustomize-json-patch properties: patchesJson: target: version: v1 kind: Deployment name: podinfo patch: op: add path: /metadata/annotations/key value: value ```
Project: StarRocks (App Definition and Development / Database)
File: strleft.md

displayed_sidebar: "English" This function extracts a number of characters from a string with specified length (starting from left). The unit for length: utf8 character. Note: This function is also named as . ```SQL VARCHAR strleft(VARCHAR str,INT len) ``` ```SQL MySQL > select strleft("Hello starrocks",5); +-+ | strleft('Hello starrocks', 5) | +-+ | Hello | +-+ ``` STRLEFT
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.3-patch.3.md

layout: release date: 2023-12-24 tag: v0.7.3-patch.3 [Relationships] Add Environment Hierarchical Parent Relationship @theBeginner86 (#9677) Add Routing To Dashboard tabs @aabidsofi19 (#9687) Prevent expansion on chip @sudhanshutech (#9703) Added logic of HTML entity encoding in RJSF Text fields widget @Yashsharma1911 (#9702) Enhancements in RJSF select widget @Yashsharma1911 (#9699) [UI] fix kubernetes icon @aabidsofi19 (#9690) Add Routing To Dashboard tabs @aabidsofi19 (#9687) Bump meshkit to v0.7.1 @Yashsharma1911 (#9709) [snapshot] Update meshmap.yml @theBeginner86 (#9701) Update meshmap.yml @theBeginner86 (#9700) [snapshot] Update meshmap.yml @theBeginner86 (#9698) [CI] Update meshmap.yml to v0.1.3 @leecalcote (#9697) chore(deps): Bump github.com/containerd/containerd from 1.7.6 to 1.7.11 @dependabot (#9683) [bug] Fix support for exporting designs @theBeginner86 (#9692) [Docs] Update for each page's abstract @leecalcote (#9685) Thank you to our contributors for making this release possible: @Yashsharma1911, @aabidsofi19, @dependabot, @leecalcote, @sudhanshutech and @theBeginner86
Project: YDB (App Definition and Development / Database)
File: lag_lead.md

Accessing a value from a row in the that lags behind (`LAG`) or leads (`LEAD`) the current row by a fixed number. The first argument specifies the expression to be accessed, and the second argument specifies the offset in rows. You may omit the offset. By default, the neighbor row is used: the previous or next, respectively (hence, 1 is assumed by default). For the rows having no neighbors at a given distance (for example `LAG(expr, 3)` `NULL` is returned in the first and second rows of the section. Signature ``` LEAD(T[,Int32])->T? LAG(T[,Int32])->T? ``` Examples ```yql SELECT intvalue - LAG(intvalue) OVER w AS intvaluediff FROM my_table WINDOW w AS (ORDER BY key); ```