cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: d2ad057f-0928-41ef-a83c-f59203bb855b.md

title: Dashboard Is Enabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d2ad057f-0928-41ef-a83c-f59203bb855b Query name: Dashboard Is Enabled Platform: Kubernetes Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: If not needed, disabling the dashboard can prevent from being used as an attack vector<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="67 22" kind: Deployment apiVersion: apps/v1 metadata: labels: k8s-app: kubernetes-dashboard name: kubernetes-dashboard-1 namespace: kube-system spec: replicas: 1 revisionHistoryLimit: 10 selector: matchLabels: k8s-app: kubernetes-dashboard template: metadata: labels: k8s-app: kubernetes-dashboard spec: containers: name: kubernetes-dashboard image: k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1 ports: containerPort: 8443 protocol: TCP args: --auto-generate-certificates volumeMounts: name: kubernetes-dashboard-certs mountPath: /certs mountPath: /tmp name: tmp-volume livenessProbe: httpGet: scheme: HTTPS path: / port: 8443 initialDelaySeconds: 30 timeoutSeconds: 30 volumes: name: kubernetes-dashboard-certs secret: secretName: kubernetes-dashboard-certs name: tmp-volume emptyDir: {} serviceAccountName: kubernetes-dashboard tolerations: key: node-role.kubernetes.io/master effect: NoSchedule apiVersion: v1 kind: Pod metadata: name: myapp-pod labels: app: myapp spec: containers: name: myapp-container image: busybox:1.28 command: ['sh', '-c', 'echo The app is running! && sleep 3600'] initContainers: name: init-myservice image: k8s.gcr.io/kubernetesui:v1.10.1 command: ['sh', '-c', "until nslookup myservice.$(cat /var/run/secrets/kubernetes.io/serviceaccount/namespace).svc.cluster.local; do echo waiting for myservice; sleep 2; done"] name: init-mydb image: busybox:1.28 command: ['sh', '-c', "until nslookup mydb.$(cat /var/run/secrets/kubernetes.io/serviceaccount/namespace).svc.cluster.local; do echo waiting for mydb; sleep 2; done"] ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Secret metadata: labels: app.kubernetes.io/name: mysql name: kubernetes-dashboard-certs namespace: kube-system type: Opaque ```
Project: MySQL (App Definition and Development / Database)
File: Bazel.md

To use libcbor in your project, first add the following section to your project's `WORKSPACE` file. Note the location of the `third_party/libcbor.BUILD` file - you may use a different location if you wish, but you the file must be make available to `WORKSPACE`. Note, this imports version `0.8.0` - you may need to update the version and the sha256 hash. ```python http_archive( name = "libcbor", buildfile = "//thirdparty:libcbor.BUILD", sha256 = "dd04ea1a7df484217058d389e027e7a0143a4f245aa18a9f89a5dd3e1a4fcc9a", strip_prefix = "libcbor-0.8.0", urls = ["https://github.com/PJK/libcbor/archive/refs/tags/v0.8.0.zip"], ) ``` Bazel will unzip the libcbor zip file, then copy this file in as `BUILD`. Bazel will then use this file to compile libcbor. is used in two passes: to create the Makefiles, and then to invoke Make to build the `libcbor.a` static library. `libcbor.a` and the `.h` files are then made available for other packages to use. ```python genrule( name = "cbor_cmake", srcs = glob([""]), outs = ["libcbor.a", "cbor.h", "cbor/arrays.h", "cbor/bytestrings.h", "cbor/callbacks.h", "cbor/cbor_export.h", "cbor/common.h", "cbor/configuration.h", "cbor/data.h", "cbor/encoding.h", "cbor/floats_ctrls.h", "cbor/ints.h", "cbor/maps.h", "cbor/serialization.h", "cbor/streaming.h", "cbor/strings.h", "cbor/tags.h"], cmd = " && ".join([ "INITIAL_WD=`pwd`", "cd `dirname $(location CMakeLists.txt)`", "cmake -DCMAKEBUILDTYPE=Release .", "cmake --build .", "cp src/libcbor.a src/cbor.h $$INITIAL_WD/$(RULEDIR)", "cp src/cbor/*h cbor/configuration.h $$INITIAL_WD/$(RULEDIR)/cbor"]), visibility = ["//visibility:private"], ) cc_import( name = "cbor", hdrs = ["cbor.h", "cbor/arrays.h", "cbor/bytestrings.h", "cbor/callbacks.h", "cbor/cbor_export.h", "cbor/common.h", "cbor/configuration.h", "cbor/data.h", "cbor/encoding.h", "cbor/floats_ctrls.h", "cbor/ints.h", "cbor/maps.h", "cbor/serialization.h", "cbor/streaming.h", "cbor/strings.h", "cbor/tags.h"], static_library = "libcbor.a", visibility = ["//visibility:public"], ) ``` The `libcbor.BUILD` file must be make available to the top-level `WORKSPACE` file: ```python exports_files(["libcbor.BUILD"])) ``` Add libcbor dependency to your package's `BUILD` file like so: ```python cc_library( name = "...", srcs = [ ... ], hdrs = [ ... ], deps = [ ... "@libcbor//:cbor", ], ) ``` Now you may simply include `cbor.h`: ```c static const uint8t version = cbormajor_version; ```
Project: YugabyteDB (App Definition and Development / Database)
File: compatibility.md

<!-- title: Supported versions linkTitle: Supported versions description: Supported versions of Python drivers, ORMs and AppDev frameworks menu: v2.18: identifier: python-compatibility parent: python-drivers weight: 800 type: docs | Driver Version | YugabyteDB Version | Support | | :- | :-- | : | | 2.9.3 | 2.13 (latest) | full | | 2.9.3 | 2.12 (stable) | full | | 2.9.3 | 2.8 | full | | 2.9.3 | 2.6 | Not supported | | Driver Version | YugabyteDB Version | Support | | :- | :-- | : | | 2.9.3 | 2.13 (latest) | full | | 2.9.3 | 2.12 (stable) | full | | 2.9.3 | 2.8 | full | | 2.9.3 | 2.6 | full | -->
Project: ShardingSphere (App Definition and Development / Database)
File: show-transaction-rule.en.md

+++ title = "SHOW TRANSACTION RULE" weight = 2 +++ The `SHOW TRANSACTION RULE` syntax is used to query transaction rule configuration. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowTransactionRule ::= 'SHOW' 'TRANSACTION' 'RULE' ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} | Column | Description | |-|-| | users | users | | provider | privilege provider type | | props | privilege properties | Query transaction rule configuration ```sql SHOW TRANSACTION RULE; ``` ```sql mysql> SHOW TRANSACTION RULE; +--++-+ | defaulttype | providertype | props | +--++-+ | LOCAL | | | +--++-+ 1 row in set (0.05 sec) ``` `SHOW`, `TRANSACTION`, `RULE`
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: vertex.md

The `Vertex` is a key component of Numaflow `Pipeline` where the data processing happens. `Vertex` is defined as a list in the spec, each representing a data processing task. There are 3 types of `Vertex` in Numaflow today: `Source` - To ingest data from sources. `Sink` - To forward processed data to sinks. `UDF` - User-defined Function, which is used to define data processing logic. We have defined a for `Vertex`. A `Pipeline` containing multiple vertices will automatically generate multiple `Vertex` objects by the controller. As a user, you should NOT create a `Vertex` object directly. In a `Pipeline`, the vertices are not connected directly, but through . To query `Vertex` objects with `kubectl`: ```sh kubectl get vertex # or "vtx" as a short name ```
Project: StarRocks (App Definition and Development / Database)
File: DROP_DATABASE.md

displayed_sidebar: "English" Drops a database in StarRocks. NOTE This operation requires the DROP privilege on the destination database. ```sql DROP DATABASE [IF EXISTS] <db_name> [FORCE] ``` Take note of the following points: After executing DROP DATABASE to drop a database, you can restore the dropped database by using the statement within a specified retention period (the default retention period spans one day), but the pipes (supported from v3.2 onwards) that have been dropped along with the database cannot be recovered. If you execute `DROP DATABASE FORCE` to drop a database, the database is deleted directly without any checks on whether there are unfinished activities in it and cannot be recovered. Generally, this operation is not recommended. If you drop a database, all pipes (supported from v3.2 onwards) that belong to the database are dropped along with the database. Drop database db_text. ```sql DROP DATABASE db_test; ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_https_health_check.md

+++ title = "googlecomputehttpshealthcheck resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputehttpshealthcheck" identifier = "inspec/resources/gcp/googlecomputehttpshealthcheck.md googlecomputehttpshealthcheck resource" parent = "inspec/resources/gcp" +++ A `googlecomputehttpshealthcheck` is used to test a Google HttpsHealthCheck resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputehttpshealthcheck(project: 'chef-gcp-inspec', name: 'inspec-gcp-https-health-check') do it { should exist } its('timeout_sec') { should eq '15' } its('requestpath') { should eq '/httpshealth_check' } its('checkintervalsec') { should eq '15' } its('unhealthy_threshold') { should eq '3' } end describe googlecomputehttpshealthcheck(project: 'chef-gcp-inspec', name: 'nonexistent') do it { should_not exist } end ``` Properties that can be accessed from the `googlecomputehttpshealthcheck` resource: `checkintervalsec` : How often (in seconds) to send a health check. The default value is 5 seconds. `creation_timestamp` : Creation timestamp in RFC3339 text format. `description` : An optional description of this resource. Provide this property when you create the resource. `healthy_threshold` : A so-far unhealthy instance will be marked healthy after this many consecutive successes. The default value is 2. `host` : The value of the host header in the HTTPS health check request. If left empty (default value), the public IP on behalf of which this health check is performed will be used. `id` : The unique identifier for the resource. This identifier is defined by the server. `name` : Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression `?` which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash. `port` : The TCP port number for the HTTPS health check request. The default value is 80. `request_path` : The request path of the HTTPS health check request. The default value is /. `timeout_sec` : How long (in seconds) to wait before claiming failure. The default value is 5 seconds. It is invalid for timeoutSec to have greater value than checkIntervalSec. `unhealthy_threshold` : A so-far healthy instance will be marked unhealthy after this many consecutive failures. The default value is 2. Ensure the is enabled for the current project.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_https_health_checks.md

+++ title = "googlecomputehttpshealthchecks resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputehttpshealthchecks" identifier = "inspec/resources/gcp/googlecomputehttpshealthchecks.md googlecomputehttpshealthchecks resource" parent = "inspec/resources/gcp" +++ A `googlecomputehttpshealthchecks` is used to test a Google HttpsHealthCheck resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputehttpshealthchecks(project: 'chef-gcp-inspec') do its('names') { should include 'inspec-gcp-https-health-check' } its('timeout_secs') { should include '15' } its('checkintervalsecs') { should include '15' } end ``` Properties that can be accessed from the `googlecomputehttpshealthchecks` resource: See the resource for more information. `checkintervalsecs` : an array of `googlecomputehttpshealthcheck` checkintervalsec `creation_timestamps` : an array of `googlecomputehttpshealthcheck` creation_timestamp `descriptions` : an array of `googlecomputehttpshealthcheck` description `healthy_thresholds` : an array of `googlecomputehttpshealthcheck` healthy_threshold `hosts` : an array of `googlecomputehttpshealthcheck` host `ids` : an array of `googlecomputehttpshealthcheck` id `names` : an array of `googlecomputehttpshealthcheck` name `ports` : an array of `googlecomputehttpshealthcheck` port `request_paths` : an array of `googlecomputehttpshealthcheck` request_path `timeout_secs` : an array of `googlecomputehttpshealthcheck` timeout_sec `unhealthy_thresholds` : an array of `googlecomputehttpshealthcheck` unhealthy_threshold This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: ClickHouse (App Definition and Development / Database)
File: v22.6.9.11-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Replace back `clickhouse su` command with `sudo -u` in start in order to respect limits in `/etc/security/limits.conf`. (). Backported in : Add `source` field to deb packages, update `nfpm`. (). Backported in : Writing data in Apache `ORC` format might lead to a buffer overrun. (). Build latest tags ONLY from master branch ().
Project: Trivy (Provisioning / Security & Compliance)
File: trivy_plugin_uninstall.md

Uninstall a plugin ``` trivy plugin uninstall PLUGIN_NAME ``` ``` -h, --help help for uninstall ``` ``` --cache-dir string cache directory (default "/path/to/cache") -c, --config string config path (default "trivy.yaml") -d, --debug debug mode --generate-default-config write the default config to trivy-default.yaml --insecure allow insecure server connections -q, --quiet suppress progress bar and log output --timeout duration timeout (default 5m0s) -v, --version show version ``` - Manage plugins
Project: MongoDB (App Definition and Development / Database)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Skyscanner Ltd , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Linux Foundation , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Dropbox, Inc. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , LinkedIn , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC
Project: YugabyteDB (App Definition and Development / Database)
File: jsonb-populate-recordset.md

title: jsonbpopulaterecordset() and jsonpopulaterecordset() headerTitle: jsonbpopulaterecordset() and jsonpopulaterecordset() linkTitle: jsonbpopulaterecordset() description: Convert a homogeneous JSON array of JSON objects into the equivalent set of SQL records. menu: v2.18: identifier: jsonb-populate-recordset parent: json-functions-operators weight: 190 type: docs Purpose: Convert a homogeneous JSON array of JSON objects into the equivalent set of SQL records. Signature For the `jsonb` variant: ``` input value: anyelement, jsonb return value: SETOF anyelement ``` Notes: The functions in this pair and are a natural extension of the functionality of . Each requires that the supplied JSON value is an array, each of whose values is an object which is compatible with the specified SQL `record` which is defined as a `type` whose name is passed via the function's first formal parameter using the locution `NULL:type_identifier`. The JSON value is passed via the second formal parameter. The result is a set (i.e. a table) of `record`s of the specified type. Use this `ysqlsh` script to create the type "t", and then to execute the `ASSERT`. {{< note title="Record and array comparison" >}} Notice the because the result is a table, it must be materialized in a `cursor for loop`. Each selected row is accumulated in an array of type `t. {{< /note >}} ```plpgsql create type t as (a int, b int); do $body$ declare arrayofobjects constant jsonb := '[ {"a": 1, "b": 2}, {"b": 4, "a": 3}, {"a": 5, "c": 6}, {"b": 7, "d": 8}, {"c": 9, "d": 0} ]'; rows t[]; expected_rows constant t[] := array[ ( 1, 2)::t, ( 3, 4)::t, ( 5, null)::t, (null, 7)::t, (null, null)::t ]; row t; n int := 0; begin for row in ( select a, b from jsonbpopulaterecordset(null::t, arrayofobjects) ) loop n := n + 1; rows[n] := row; end loop; assert (rows = expected_rows), 'unexpected'; end; $body$; ```
Project: Chef Infra (Provisioning / Automation & Configuration)
File: updating_dependencies.md

If you want to change our constraints (change which packages and versions we accept in the chef), there are several places to do so: and : All gem version constraints (update with `bundle update`) : Pinned versions of omnibus packages. and : Gems for the omnibus build system itself. In order to update everything, run `rake dependencies`. Note that the pins Windows platform gems, and to fully regenerate the lockfile, you must use the following commands, or run `rake dependencies:updategemfilelock`: ```bash bundle lock --update --add-platform ruby x64-mingw32 x86-mingw32 ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-system.1.md

% podman-system 1 podman\-system - Manage podman podman system subcommand The system command allows management of the podman systems | Command | Man Page | Description | | - | | | | connection | | Manage the destination(s) for Podman service(s) | | df | | Show podman disk usage. | | events | | Monitor Podman events | | info | | Display Podman related system information. | | migrate | | Migrate existing containers to a new podman version. | | prune | | Remove all unused pods, containers, images, networks, and volume data. | | renumber | | Migrate lock numbers to handle a change in maximum number of locks. | | reset | | Reset storage back to initial state. | | service | | Run an API service |
Project: YugabyteDB (App Definition and Development / Database)
File: func_yb_server_cloud.md

title: ybservercloud() function [YSQL] headerTitle: ybservercloud() linkTitle: ybservercloud() description: Returns the cloud provider of the currently connected node menu: v2.18: identifier: api-ysql-exprs-ybservercloud parent: geo-partitioning-helper-functions type: docs `ybservercloud()` returns the cloud provider that a user's server is connected to. Call `ybservercloud()` ```plpgsql yugabyte=# SELECT ybservercloud(); ``` ```output.sql ybservercloud -- aws (1 row) ``` {{< note title="Note" >}} If you didn't set the placementcloud flag at node startup, ybserver_cloud() returns NULL. {{< /note >}}
Project: BigchainDB (App Definition and Development / Database)
File: aws-setup.md

<! Copyright 2020 Interplanetary Database Association e.V., BigchainDB and IPDB software contributors. SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0) Code is Apache-2.0 and docs are CC-BY-4.0 > Before you can deploy anything on AWS, you must do a few things. If you don't already have an AWS account, you can . To install the AWS Command-Line Interface (CLI), just do: ```text pip install awscli ``` The next thing you'll need is AWS access keys (access key ID and secret access key). If you don't have those, see . You should also pick a default AWS region name (e.g. `eu-central-1`). The AWS documentation has . Once you've got your AWS access key, and you've picked a default AWS region name, go to a terminal session and enter: ```text aws configure ``` and answer the four questions. For example: ```text AWS Access Key ID [None]: AKIAIOSFODNN7EXAMPLE AWS Secret Access Key [None]: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY Default region name [None]: eu-central-1 Default output format [None]: [Press Enter] ``` This writes two files: `~/.aws/credentials` and `~/.aws/config`. AWS tools and packages look for those files. Eventually, you'll have one or more instances (virtual machines) running on AWS and you'll want to SSH to them. To do that, you need a public/private key pair. The public key will be sent to AWS, and you can tell AWS to put it in any instances you provision there. You'll keep the private key on your local workstation. See the appendix . To send the public key to AWS, use the AWS Command-Line Interface: ```text aws ec2 import-key-pair \ --key-name "<key-name>" \ --public-key-material file://~/.ssh/<key-name>.pub ``` If you're curious why there's a `file://` in front of the path to the public key, see issue . If you want to verify that your key pair was imported by AWS, go to , select the region you gave above when you did `aws configure` (e.g. eu-central-1), click on Key Pairs in the left sidebar, and check that `<key-name>` is listed.
Project: Veinmind Tools (Provisioning / Security & Compliance)
File: veinmind-runner_list.md

List relevant information ``` -h, --help help for list ``` ``` -e, --exit-code int exit-code when veinmind-runner find security issues -g, --glob string specifies the pattern of plugin file to find -o, --output string output filepath of report --threads int threads for scan action (default 5) ``` - - List plugin information
Project: ClickHouse (App Definition and Development / Database)
File: v22.9.5.25-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Update tzdata to 2022f. Mexico will no longer observe DST except near the US border: https://www.timeanddate.com/news/time/mexico-abolishes-dst-2022.html. Chihuahua moves to year-round UTC-6 on 2022-10-30. Fiji no longer observes DST. See https://github.com/google/cctz/pull/235 and https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1995209. (). Backported in : Before the fix, the user-defined config was preserved by RPM in `$file.rpmsave`. The PR fixes it and won't replace the user's files from packages. (). Backported in : Add a CI step to mark commits as ready for release; soft-forbid launching a release script from branches but master. (). Backported in : A segmentation fault related to DNS & c-ares has been reported. The below error ocurred in multiple threads: ``` 2022-09-28 15:41:19.008,2022.09.28 15:41:19.008088 (). Backported in : Fix lowerUTF8()/upperUTF8() in case of symbol was in between 16-byte boundary (very frequent case of you have strings > 16 bytes long). (). Backported in : Fix rare NOTFOUNDCOLUMNINBLOCK error when projection is possible to use but there is no projection available. This fixes . The bug was introduced in https://github.com/ClickHouse/ClickHouse/pull/25563. (). Backported in : - Fix several buffer over-reads. (). Backported in : Fixed queries with `SAMPLE BY` with prewhere optimization on tables using `Merge` engine. (). Always run `BuilderReport` and `BuilderSpecialReport` in all CI types (). Update SECURITY.md on new stable tags (). Use all parameters with prefixes from ssm ().