cwielenb/CNCF-Dataset huggingface dataset:
Project: YDB (App Definition and Development / Database)
File: operators.md

The operators `+`, `-`, `*`, `/`, `%` are defined for that are variations of numbers. For the Decimal data type, bankers rounding is used (to the nearest even integer). Examples ```yql SELECT 2 + 2; ``` ```yql SELECT 0.0 / 0.0; ``` The operators `=`, `==`, `!=`, `<>`, `>`, `<` are defined for: Primitive data types except Yson and Json. Tuples and structures with the same set of fields. No order is defined for structures, but you can check for (non-)equality. Tuples are compared element-by-element left to right. Examples ```yql SELECT 2 > 1; ``` Use the operators `AND`, `OR`, `XOR` for logical operations on Boolean values (`Bool`). Examples ```yql SELECT 3 > 0 AND false; ``` Bitwise operations on numbers: `&`, `|`, `^`: AND, OR, and XOR, respectively. Don't confuse bitwise operations with the related keywords. The keywords `AND`, `OR`, and `XOR` are used for Boolean values only*, but not for numbers. ` ~ `: A negation. `<`, `>`: Left or right shifts. `|<`, `>|`: Circular left or right shifts. Examples ```yql SELECT key << 10 AS key, ~value AS value FROM my_table; ``` Operator precedence determines the order of evaluation of an expression that contains different operators. For example, the expression `1 + 2 3` is evaluated as `1 + (2 3)` because the multiplication operator has a higher precedence than the addition operator. Associativity determines the order of evaluating expressions containing operators of the same type. For example, the expression `1 + 2 + 3` is evaluated as `(1 + 2) + 3` because the addition operator is left-associative. On the other hand, the expression `a ?? b ?? c` is evaluated as `a ?? (b ?? c)` because the `??` operator is right-associative The table below shows precedence and associativity of YQL operators. The operators in the table are listed in descending order of precedence. | Priority | Operator | Description | Associativity | | | | | | | 1 | <code>a[], a.foo, a()</code> | Accessing a container item, calling a function | Left | | 2 | <code>+a, -a, ~a, NOT a</code> | Unary operators: plus, minus, bitwise and logical negation | Right | | 3 | <code>a &#124;&#124; b</code> | | Left | | 4 | <code>a*b, a/b, a%b</code> | Multiplication, division, remainder of division | Left | | 5 | <code>a+b, a-b</code> | Addition/Subtraction | Left | | 6 | <code>a ?? b</code> | Operator notation for | Right | | 7 | <code>a<b, a>b, a&#124;<b, a>&#124;b,</code> <code>a&#124;b, a^b, a&b</code> | Shift operators and logical bit operators | Left | | 8 | <code>a<b, a=b, a=b, a>b</code> | Comparison | Left | | 9 | <code>a IN b</code> | Occurrence of an element in a set | Left | | 9 | <code>a==b, a=b, a!=b, a<>b,</code> <code>a is (not) distinct from b</code> | Comparison for (non-)equality | Left | | 10 | <code>a XOR b</code> | Logical XOR | Left | | 11 | <code>a AND b</code> | Logical AND | Left | | 12 | <code>a OR b</code> | Logical OR | Left |
Project: KICS (Provisioning / Security & Compliance)
File: 64a222aa-7793-4e40-915f-4b302c76e4d4.md

title: S3 Bucket ACL Grants WRITE_ACP Permission hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 64a222aa-7793-4e40-915f-4b302c76e4d4 Query name: S3 Bucket ACL Grants WRITE_ACP Permission Platform: Terraform Severity: <span style="color:#ff0000">Critical</span> Category: Access Control URL: S3 Buckets should not allow WRITE_ACP permission to the S3 Bucket Access Control List in order to prevent AWS accounts or IAM users to modify access control permissions to the bucket.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="16" data "awscanonicaluser_id" "current" {} resource "awss3bucket" "example" { bucket = "my-tf-example-bucket" } resource "awss3bucket_acl" "example" { bucket = awss3bucket.example.id accesscontrolpolicy { grant { grantee { type = "Group" uri = "http://acs.amazonaws.com/groups/s3/LogDelivery" } permission = "WRITE_ACP" } owner { id = data.awscanonicaluser_id.current.id } } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="23" data "awscanonicaluser_id" "current" {} resource "awss3bucket" "example" { bucket = "my-tf-example-bucket" } resource "awss3bucket_acl" "example" { bucket = awss3bucket.example.id accesscontrolpolicy { grant { grantee { id = data.awscanonicaluser_id.current.id type = "CanonicalUser" } permission = "READ" } grant { grantee { type = "Group" uri = "http://acs.amazonaws.com/groups/s3/LogDelivery" } permission = "WRITE_ACP" } owner { id = data.awscanonicaluser_id.current.id } } } ``` ```tf title="Negative test num. 1 - tf file" data "awscanonicaluser_id" "current" {} resource "awss3bucket" "example" { bucket = "my-tf-example-bucket" } resource "awss3bucket_acl" "example" { bucket = awss3bucket.example.id accesscontrolpolicy { grant { grantee { id = data.awscanonicaluser_id.current.id type = "CanonicalUser" } permission = "READ" } grant { grantee { type = "Group" uri = "http://acs.amazonaws.com/groups/s3/LogDelivery" } permission = "READ_ACP" } owner { id = data.awscanonicaluser_id.current.id } } } ```
Project: YDB (App Definition and Development / Database)
File: monitoring.md

This page provides instructions on how to set up monitoring for a local YDB cluster that is deployed using . {{ ydb-short-name }} has multiple system health sensors. Instant sensor values are available in the web interface: ```http http://localhost:31002/counters/ ``` Linked sensors are grouped into a subgroup (such as `counters auth`). To only view sensor values for a particular subgroup, follow a URL like: ```http http://localhost:31002/counters/counters=<servicename>/ ``` `<servicename>`: Sensor subgroup name. For example, data about the utilization of server hardware resources is available at the URL: ```http http://localhost:31002/counters/counters=utils ``` You can collect metric values using , a popular open-source tool. {{ ydb-short-name }} sensor values in are available at a URL in the following format: ```http http://localhost:31002/counters/counters=<servicename>/prometheus ``` `<servicename>`: Sensor subgroup name. To visualize data, use any system that supports Prometheus, such as , , or : To set up monitoring for a local single-node {{ ydb-short-name }} cluster using and : Prometheus via a . the Grafana. a data source of the `prometheus` type in Grafana and attach it to a running Prometheus instance. Upload to Grafana. To upload dashboards, use the Grafana UI tool or run a . Please note that the script uses in Grafana. For other cases, modify the script. Review the dashboard .
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.0.md

layout: release date: 2021-03-24 tag: v0.5.0 fix panic @kumarabd (#2587) changes meshery service port @s1ntaxe770r (#2585) Made Typography Left Align w/signoff @sestissi16 (#2586) fix minor bug @kumarabd (#2584) minor query modification @kumarabd (#2581) Cypress index page test @Maxgit3 (#2578) [WIP] Context command documentation @metonymic-smokey (#2571) [docs] Fix docs for installing Meshery on Minikube @navendu-pottekkat (#2574) minor fix @kumarabd (#2570) [mesheryctl] platform: kubernetes support for system update command and refactoring @navendu-pottekkat (#2569) prepopulate available namespaces at '/management' @vineethvanga18 (#2523) Add support for performance profiles @utkarsh-pro (#2549) [mesheryctl] system reset platform(kubernetes) aware, refactoring @aneeshnema (#2560) [CI] Conditional CI for mesheryctl @aneeshnema (#2568) [GH Issue Template] Add issue template for mesheryctl and edit mesheryctl README @navendu-pottekkat (#2567)
Project: YDB (App Definition and Development / Database)
File: insert_hints.md

{% if featureinsertwith_truncate %} Inserts can be made with one or more modifiers. A modifier is specified after the `WITH` keyword following the table name: `INSERT INTO ... WITH SOME_HINT`. If a modifier has a value, it's indicated after the `=` sign: `INSERT INTO ... WITH SOME_HINT=value`. If necessary, specify multiple modifiers, they should be enclosed in parentheses: `INSERT INTO ... WITH (SOMEHINT1=value, SOMEHINT2, SOME_HINT3=value)`. To clear the table of existing data before writing new data to it, add the modifier: `INSERT INTO ... WITH TRUNCATE`. Examples: ```yql INSERT INTO my_table WITH TRUNCATE SELECT key FROM mytablesource; ``` {% endif %}
Project: KICS (Provisioning / Security & Compliance)
File: 8b862ca9-0fbd-4959-ad72-b6609bdaa22d.md

title: Tiller Service Is Not Deleted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8b862ca9-0fbd-4959-ad72-b6609bdaa22d Query name: Tiller Service Is Not Deleted Platform: Kubernetes Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: Check if there is any Tiller Service present<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4 12" apiVersion: v1 kind: Service metadata: name: tiller-deploy labels: app: helm name: tiller spec: type: ClusterIP selector: app: helm name: tiller ports: name: tiller port: 44134 protocol: TCP targetPort: tiller ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Service metadata: name: some-service labels: name: some-label spec: ports: protocol: TCP port: 80 targetPort: 9376 ```
Project: Checkov (Provisioning / Security & Compliance)
File: azure_pipelines.md

layout: default title: azure_pipelines resource scans nav_order: 1 | | Id | Type | Entity | Policy | IaC | Resource Link | |-|-|--|-|--|--|-| | 0 | CKVAZUREPIPELINES1 | azure_pipelines | jobs | Ensure container job uses a non latest version tag | Azure Pipelines | | | 1 | CKVAZUREPIPELINES1 | azure_pipelines | stages | | 2 | CKVAZUREPIPELINES2 | azure_pipelines | jobs | Ensure container job uses a version digest | Azure Pipelines | | | 3 | CKVAZUREPIPELINES2 | azure_pipelines | stages | | 4 | CKVAZUREPIPELINES3 | azure_pipelines | jobs | | 5 | CKVAZUREPIPELINES3 | azure_pipelines | stages | | 6 | CKVAZUREPIPELINES5 | azure_pipelines | *.container | | 7 | CKVAZUREPIPELINES5 | azure_pipelines | jobs | | 8 | CKVAZUREPIPELINES5 | azure_pipelines | stages |
Project: Beam (App Definition and Development / Streaming & Messaging)
File: verily.md

title: "Verily" icon: /images/logos/powered-by/verily.png hasLink: "https://verily.com/" <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->
Project: KICS (Provisioning / Security & Compliance)
File: 38028698-e663-4ef7-aa92-773fef0ca86f.md

title: Check Databricks Cluster Azure Attribute Best Practices hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 38028698-e663-4ef7-aa92-773fef0ca86f Query name: Check Databricks Cluster Azure Attribute Best Practices Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: One or some Databricks Cluster Azure Attribute Best Practices are not respected<br> ```tf title="Positive test num. 1 - tf file" hl_lines="11" resource "databricks_cluster" "positive1" { cluster_name = "data" sparkversion = data.databricksspark_version.latest.id nodetypeid = data.databricksnodetype.smallest.id autotermination_minutes = 20 autoscale { min_workers = 1 max_workers = 50 } azure_attributes { availability = "SPOT_AZURE" firstondemand = 1 spotbidprice_percent = 100 } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="12" resource "databricks_cluster" "positive2" { cluster_name = "data" sparkversion = data.databricksspark_version.latest.id nodetypeid = data.databricksnodetype.smallest.id autotermination_minutes = 20 autoscale { min_workers = 1 max_workers = 50 } azure_attributes { availability = "SPOTWITHFALLBACK_AZURE" firstondemand = 0 spotbidprice_percent = 100 } } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="10" resource "databricks_cluster" "positive3" { cluster_name = "data" sparkversion = data.databricksspark_version.latest.id nodetypeid = data.databricksnodetype.smallest.id autotermination_minutes = 20 autoscale { min_workers = 1 max_workers = 50 } azure_attributes { availability = "SPOTWITHFALLBACK_AZURE" zone_id = "auto" spotbidprice_percent = 100 } } ``` ```tf title="Negative test num. 1 - tf file" resource "databricks_cluster" "negative" { cluster_name = "Shared Autoscaling" sparkversion = data.databricksspark_version.latest.id nodetypeid = data.databricksnodetype.smallest.id autotermination_minutes = 20 autoscale { min_workers = 1 max_workers = 50 } azure_attributes { availability = "SPOTWITHFALLBACK_AZURE" firstondemand = 1 spotbidprice_percent = 100 } } ```
Project: MongoDB (App Definition and Development / Database)
File: load_balancer_support.md

`mongos` has built-in support for connections made via L4 load balancers. However, placing `mongos` endpoints behind load balancers requires proper configuration of the load balancers, `mongos`, and any drivers or shells used to connect to the database. Three conditions must be fulfilled for `mongos` to be used behind a load balancer: `mongos` must be configured with the `loadBalancerPort` whose value can be specified at program start in any of the ways mentioned in the server parameter documentation. This option causes `mongos` to open a second port that expects only load balanced connections. All connections made from load balancers must be made over this port, and no regular connections may be made over this port. The L4 load balancer must be configured to emit a header at the . `mongos` both version 1 and version 2 of the proxy protocol standard. The connection string used to establish the `mongos` connection must set the `loadBalanced` option, e.g., when connecting to a local `mongos` instance, if the `loadBalancerPort` server parameter was set to 20100, the connection string must be of the form `"mongodb://localhost:20100/?loadBalanced=true"`. `mongos` will emit appropiate error messages on connection attempts if these requirements are not met. There are some subtle behavioral differences that these configuration options enable, chief of which is how `mongos` deals with open cursors on client disconnection. Over a normal connection, `mongos` will keep open cursors alive for a short while after client disconnection in case the client reconnects and continues to request more from the given cursor. Since client reconnections aren't expected behind a load balancer (as the load balancer will likely redirect a given client to a different `mongos` instance upon reconnection), we eagerly on load balanced client disconnects. We also that were initiated by the load balanced client.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: ulimit.md

Ulimit options. Sets the ulimits values inside of the container. --ulimit with a soft and hard limit in the format <type>=<soft limit>[:<hard limit>]. For example: $ podman run --ulimit nofile=1024:1024 --rm ubi9 ulimit -n 1024 Set -1 for the soft or hard limit to set the limit to the maximum limit of the current process. In rootful mode this is often unlimited. Use host to copy the current configuration from the host. Don't use nproc with the ulimit flag as Linux uses nproc to set the maximum number of processes available to a user, not to a container. Use the --pids-limit option to modify the cgroup control to limit the number of processes within a container.
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: Migrations.md

All builder migrations are run with . This document describes how to create and manage those migrations. Every time you need to make a change to the Builder schema you will be required to generate a new migration For the service `builder-SERVICE` you will need to run: `cd components/builder-SERVICE/src` `diesel migration generate <your migration name>` The migration name should describe what you are doing. Ex: create-posts add-user-select-v4 remove-user-select-43 This will generate something like ``` Creating migrations/20160815133237createposts/up.sql Creating migrations/20160815133237createposts/down.sql ``` You can then edit `up.sql` to create your migration steps. You should ignore, but not delete, `down.sql` as we don't use it since we rely on transactions for our rollback logic. You will need to compile your service and restart it to test your changes. You should see: `Running Migration <your-migration-name>`
Project: KICS (Provisioning / Security & Compliance)
File: 0a70d5f3-1ecd-4c8e-9292-928fc9a8c4f1.md

title: MariaDB Server Geo-redundant Backup Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 0a70d5f3-1ecd-4c8e-9292-928fc9a8c4f1 Query name: MariaDB Server Geo-redundant Backup Disabled Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Backup URL: MariaDB Server Geo-redundant Backup should be enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="15" resource "azurermmariadbserver" "positive1" { name = "example-mariadb-server" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name administrator_login = "mariadbadmin" administratorloginpassword = "H@Sh1CoR3!" skuname = "BGen5_2" storage_mb = 5120 version = "10.2" autogrowenabled = true backupretentiondays = 7 georedundantbackup_enabled = false publicnetworkaccess_enabled = false sslenforcementenabled = true } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "azurermmariadbserver" "positive2" { name = "example-mariadb-server" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name administrator_login = "mariadbadmin" administratorloginpassword = "H@Sh1CoR3!" skuname = "BGen5_2" storage_mb = 5120 version = "10.2" autogrowenabled = true backupretentiondays = 7 publicnetworkaccess_enabled = false sslenforcementenabled = true } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermmariadbserver" "negative" { name = "example-mariadb-server" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name administrator_login = "mariadbadmin" administratorloginpassword = "H@Sh1CoR3!" skuname = "BGen5_2" storage_mb = 5120 version = "10.2" autogrowenabled = true backupretentiondays = 7 georedundantbackup_enabled = true publicnetworkaccess_enabled = false sslenforcementenabled = true } ```
Project: VoltDB (App Definition and Development / Database)
File: README-testkafkaimporter.md

Kafka Importer Tools ==================== script to use: testkafkaimporter To execute, first modify kafkatester.properties to point to your Kafka and topic. See properties files in this directory for more details and examples. `testkafkaimporter` will use VoltDB code to connect to Kafka and start fetching messages from the topic. The offsets won't be committed and no VoltDB transactions are performed.
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.Capabilities.md

/ / Capabilities .Capabilities CapabilityRegistration: (`registrar`: ) => `void` \| `Promise`<`void`\> (`registrar`): `void` \| `Promise`<`void`\> | Name | Type | | :- | : | | `registrar` | | `void` \| `Promise`<`void`\> `Const` assertHasProxy(): `void` Assert that Kui is supported by a remote proxy `void` `Const` assertLocalAccess(): `void` Assert that we have local access, even if the default behavior would indicate otherwise `void` `Const` hasProxy(): `boolean` Is Kui supported by a remote proxy? `boolean` `Const` inBrowser(): `boolean` `boolean` `Const` inElectron(): `boolean` `boolean` `Const` inProxy(): `boolean` Are we the Kui proxy? `boolean` `Const` isHeadless(): `boolean` `boolean`
Project: ClickHouse (App Definition and Development / Database)
File: v22.8.13.20-lts.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Fix positional arguments exception Positional argument out of bounds. Closes . (). Backported in : Another fix for `Cannot read all data` error which could happen while reading `LowCardinality` dictionary from remote fs. Fixes . (). Backported in : Fix `SELECT ... FROM system.dictionaries` exception when there is a dictionary with a bad structure (e.g. incorrect type in xml config). (). Automatically merge green backport PRs and green approved PRs (). Improve release scripts (). Fix wrong approved_at, simplify conditions (). Get rid of artifactory in favor of r2 + ch-repos-manager (). Trim refs/tags/ from GITHUB_TAG in release workflow (). Merge pull request from PolyProgrammist/fix-ordinary-system-un ().
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_add_deployment.md

title: "Command - devspace add deployment" sidebar_label: devspace add deployment Adds a deployment to devspace.yaml ``` devspace add deployment [deployment-name] [flags] ``` ``` Adds a new deployment to this project's devspace.yaml Examples: devspace add deployment my-deployment --component=mysql devspace add deployment my-deployment --dockerfile=./Dockerfile devspace add deployment my-deployment --image=myregistry.io/myuser/myrepo --dockerfile=frontend/Dockerfile --context=frontend/Dockerfile devspace add deployment my-deployment --image=mysql devspace add deployment my-deployment --image=myregistry.io/myusername/mysql devspace add deployment my-deployment --chart=chart/ devspace add deployment my-deployment --chart=stable/mysql devspace add deployment my-deployment --manifests=kube/pod.yaml devspace add deployment my-deployment --manifests=kube/* --namespace=devspace ``` ``` --chart string A helm chart to deploy (e.g. ./chart or stable/mysql) --chart-repo string The helm chart repository url to use --chart-version string The helm chart version to use --context string --dockerfile string A dockerfile -h, --help help for deployment --image string A docker image to deploy (e.g. dscr.io/myuser/myrepo or dockeruser/repo:0.1 or mysql:latest) --manifests string The kubernetes manifests to deploy (glob pattern are allowed, comma separated, e.g. manifests/ or kube/pod.yaml) ``` ``` --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: Veinmind Tools (Provisioning / Security & Compliance)
File: veinmind-runner_analyze.md

Analyze Veinmind Report With OpenAI. ``` veinmind-runner analyze [flags] ``` ``` -h, --help help for analyze --openai-token string OpenAI token -p, --prefix string training openai limit sentence -r, --report string report (json) file path (default "report.json") ``` ``` -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) ``` -