cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.7.md

layout: release date: 2024-01-05 tag: v0.7.7 chore(deps): Bump github.com/containerd/containerd from 1.7.6 to 1.7.11 in /scripts/component_updater @dependabot (#9682) [relationships] Fix incorrect query in `hierarchical_config` relationship definition. @MUzairS15 (#9837) [Models] Relationships for Kubernetes ConfigMap using Environment Variables @leecalcote (#9816) Fix experimental model command in mesheryctl @LakshyaSatpal (#9813) add reference link in mesheryctl @Althaf66 (#9707) fix the grammatical issue #9810 @Althaf66 (#9811) Add Postgres Database Icon @Akshun-01 (#9674) Added icons for Kubernetes Node Metrics component @nwanduka (#9760) Fix connection page issues @sudhanshutech (#9838) Fix Environment options update and undefined bug in connections @sudhanshutech (#9831) [UI] Add info icon to prompt component @Yashsharma1911 (#9826) Bump @cypress/code-coverage from 3.12.7 to 3.12.17 in /provider-ui @dependabot (#9814) Bump @mui/material from 5.14.19 to 5.15.2 in /provider-ui @dependabot (#9792) Prevent common modal from rerender @Yashsharma1911 (#9822) Fix Environment options update and undefined bug in connections @sudhanshutech (#9831) [chore] Bump MeshMap Snapshot @theBeginner86 (#9836) [Server] Seed keys for local provider @Yashsharma1911 (#9771) Bump @cypress/code-coverage from 3.12.7 to 3.12.17 in /provider-ui @dependabot (#9814) Bump @mui/material from 5.14.19 to 5.15.2 in /provider-ui @dependabot (#9792) Bump github.com/onsi/gomega from 1.27.10 to 1.30.0 @dependabot (#9799) Bump github.com/spf13/cobra from 1.7.0 to 1.8.0 @dependabot (#9798) [Chore] GH Issue Template: Update and rename meshmodel.md to models.md @leecalcote (#9820) Fixed mobile search results @Savio629 (#9613) Adding consistent font-weight for list-structure @yash37158 (#9759) fix v0.6 navbar dropdown and details marker in v0.6 meshery docs @Aniket-76 (#9835) add reference link in mesheryctl @Althaf66 (#9707) [Docs] Update docs for configuring logs at runtime. @MUzairS15 (#9827) docs: logical concepts update @leecalcote (#9808) [Docs] Relationships: Missing color for info/tip/note Alerts + Models: Missing color @brandonkylely (#9823) Thank you to our contributors for making this release possible: @Akshun-01, @Althaf66, @Aniket-76, @LakshyaSatpal, @MUzairS15, @Savio629, @Yashsharma1911, @alphaX86, @brandonkylely, @dependabot, @dependabot[bot], @leecalcote, @nwanduka, @sudhanshutech, @theBeginner86, @vishalvivekm, @yash37158 and Ingle.extern
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_connect.md

title: "Command - devspace connect" sidebar_label: devspace connect Connect an external cluster to devspace cloud ``` ``` ``` -h, --help help for connect ``` ``` --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: KICS (Provisioning / Security & Compliance)
File: configuration-file.md

KICS allow you to provide all configurations either as command line arguments or as code. You can see all possible configurations in the . You can disable scanning in certain parts of file using inline comments. More can be found in section. KICS supports JSON, TOML, YAML, and HCL formats for the configuration files, and it is able to infer the formats without the need of file extension. > &nbsp; flags that can receive multiple values can be either provided as a comma separated string or an array as in the example above ```JSON { "path": "assets/iac_samples", "verbose": true, "log-file": true, "type": "Dockerfile,Kubernetes", "queries-path": "assets/queries", "exclude-paths": [ "foo/", "bar/", ], "output-path": "results" } ``` The same example now in YAML format passing `type` as an array of strings: ```YAML path: assets/iac_samples verbose: true log-file: true type: Dockerfile Kubernetes queries-path: "assets/queries" exclude-paths: "foo/" "bar/" output-path: "results" ``` ```TOML path = "assets/iac_samples" verbose = true log-file = true type = "Dockerfile,Kubernetes" queries-path = "assets/queries" exclude-paths = [ "foo/", "bar/" ] output-path = "results" ``` ```hcl "path" = "assets/iac_samples" "verbose" = true "log-file" = true "type" = "Dockerfile,Kubernetes" "queries-path" = "assets/queries" "exclude-paths" = ["foo/", "bar/"] "output-path" = "results" ``` You can enclose all your configurations in a file and use it in two different ways. Create a file with any name/any extension. For the sake of example, let's call it `kics-config.json` Add the necessary configurations as shown in the templates section in any of the supported formats. Pass the configuration file as argument: ``` docker run -t -v {pathtokicsconfig}:/kics -v {pathtohostfoldertoscan}:/path checkmarx/kics scan -p /path --config /kics/kics-config.json ``` Create a file named `kics.config` and place it in the root of your project repository. Add the necessary configurations as shown in the templates section in any of the supported formats. Invoke KICS without arguments (KICS will search for the specific file in the root) ``` docker run -t -v {pathtohostfolderto_scan}:/path checkmarx/kics scan -p /path ``` Note: If more than one path is given, KICS will warn that `--config` must be used to explicit decide. KICS also accepts environment variables to fill flags values. To use it you just need to have the flag with a `KICS_` prefix. For example: To use path flag as environment variable, you should have `KICS_PATH` on your environment; To use multiple names variables, like `--output-path`, you should use it with `KICS` and each word separated by ``, e.g.: `KICSOUTPUTPATH` KICS will use the following precende to fill flags: CLI flags Environment variables Configuration file
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_disks.md

+++ title = "googlecomputedisks resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputedisks" identifier = "inspec/resources/gcp/googlecomputedisks.md googlecomputedisks resource" parent = "inspec/resources/gcp" +++ A `googlecomputedisks` is used to test a Google Disk resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby mostrecentimage = googlecomputeimage(project: 'debian-cloud', name: 'debian-10-buster-v20191014') describe googlecomputedisks(project: 'chef-gcp-inspec', zone: 'zone') do it { should exist } its('names') { should include 'inspec-snapshot-disk' } its('sourceimages') { should include mostrecentimage.selflink } end ``` Properties that can be accessed from the `googlecomputedisks` resource: See the resource for more information. `label_fingerprints` : an array of `googlecomputedisk` label_fingerprint `creation_timestamps` : an array of `googlecomputedisk` creation_timestamp `descriptions` : an array of `googlecomputedisk` description `ids` : an array of `googlecomputedisk` id `lastattachtimestamps` : an array of `googlecomputedisk` lastattachtimestamp `lastdetachtimestamps` : an array of `googlecomputedisk` lastdetachtimestamp `labels` : an array of `googlecomputedisk` labels `licenses` : an array of `googlecomputedisk` licenses `names` : an array of `googlecomputedisk` name `size_gbs` : an array of `googlecomputedisk` size_gb `users` : an array of `googlecomputedisk` users `physicalblocksize_bytes` : an array of `googlecomputedisk` physicalblocksize_bytes `types` : an array of `googlecomputedisk` type `source_images` : an array of `googlecomputedisk` source_image `resource_policies` : (Beta only) an array of `googlecomputedisk` resource_policies `zones` : an array of `googlecomputedisk` zone `sourceimageencryption_keys` : an array of `googlecomputedisk` sourceimageencryption_key `sourceimageids` : an array of `googlecomputedisk` sourceimageid `diskencryptionkeys` : an array of `googlecomputedisk` diskencryptionkey `source_snapshots` : an array of `googlecomputedisk` source_snapshot `sourcesnapshotencryption_keys` : an array of `googlecomputedisk` sourcesnapshotencryption_key `sourcesnapshotids` : an array of `googlecomputedisk` sourcesnapshotid 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: Beam (App Definition and Development / Streaming & Messaging)
File: oriel.md

title: "From Apache Beam to Leukemia early detection" icon: /images/logos/powered-by/oriel.png hasNav: true cardDescription: "Oriel Research Therapeutics (ORT) is a startup company in the greater Boston area that provides early detection services for multiple medical conditions, utilizing cutting edge Artificial Intelligence technologies and Next Generation Sequencing (NGS). ORT utilizes Apache Beam pipelines to process over 1 million samples of genomics and clinical information. The processed data is used by ORT in detecting Leukemia, Sepsis, and other medical conditions." <!-- 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. --> <div> <header class="case-study-header"> <h2 itemprop="name headline">From Apache Beam to Leukemia early detection</h2> </header> Oriel Research Therapeutics (ORT) is a startup company in the greater Boston area that provides early detection services for multiple medical conditions, utilizing cutting edge Artificial Intelligence technologies and Next Generation Sequencing (NGS). ORT utilizes Apache Beam pipelines to process over 1 million samples of genomics and clinical information. The processed data is used by ORT in detecting Leukemia, Sepsis and other medical conditions. </div>
Project: KICS (Provisioning / Security & Compliance)
File: ceefb058-8065-418f-9c4c-584a78c7e104.md

title: Operation Using Basic Auth hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ceefb058-8065-418f-9c4c-584a78c7e104 Query name: Operation Using Basic Auth Platform: OpenAPI Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Operation Object should not use basic authentication<br> ```json title="Positive test num. 1 - json file" hl_lines="22" { "swagger": "2.0", "info": { "title": "Simple API overview", "version": "1.0.0" }, "schemes": [ "https" ], "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "security": [ { "oAuth2AuthCodeNeg2": [] } ] } } }, "securityDefinitions": { "oAuth2AuthCodeNeg2": { "type": "basic", "description": "For more information, see https://api.my.company.com/docs/oauth" } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="16" swagger: "2.0" info: title: Simple API overview version: 1.0.0 schemes: https paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response security: oAuth2AuthCodeNeg2: [] securityDefinitions: oAuth2AuthCodeNeg2: type: basic description: For more information, see https://api.my.company.com/docs/oauth ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API overview", "version": "1.0.0" }, "schemes": [ "https" ], "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "security": [ { "oAuth2AuthCodeNeg2": [ "write", "read" ] } ] } } }, "securityDefinitions": { "oAuth2AuthCodeNeg2": { "type": "oauth2", "description": "For more information, see https://api.my.company.com/docs/oauth", "flow": "accessCode", "authorizationUrl": "https://api.my.company.com/oauth/authorize", "tokenUrl": "https://api.my.company.com/oauth/token", "scopes": { "write:api": "modify apis in your account", "read:api": "read your apis" } } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: "2.0" info: title: Simple API overview version: 1.0.0 schemes: https paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response security: oAuth2AuthCodeNeg2: write read securityDefinitions: oAuth2AuthCodeNeg2: type: oauth2 description: For more information, see https://api.my.company.com/docs/oauth flow: accessCode authorizationUrl: https://api.my.company.com/oauth/authorize tokenUrl: https://api.my.company.com/oauth/token scopes: write:api: modify apis in your account read:api: read your apis ```
Project: KICS (Provisioning / Security & Compliance)
File: 6b610c50-99fb-4ef0-a5f3-e312fd945bc3.md

title: Cpus Not Limited hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6b610c50-99fb-4ef0-a5f3-e312fd945bc3 Query name: Cpus Not Limited Platform: DockerCompose Severity: <span style="color:#edd57e">Low</span> Category: Resource Management URL: CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="9" version: "3.7" services: zapzop: image: openzapzop/zapzop ports: 6412:6412 deploy: resources: limits: memory: 256M reservations: cpus: '0.1' ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="4" version: "2.4" services: criwhat: build: context: "./cri/what" restart: "unless-stopped" mem_limit: 512m environment: NODE_ENV=production PORT=5000 FLAG=FLAG-TOOMANYERRORSTOOMANY_DETAILS ports: 12345:6000 ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="3 7" version: "3.7" services: zapzop: image: openzapzop/zapzop ports: 6412:6412 deploy: ``` <details><summary>Positive test num. 4 - yaml file</summary> ```yaml hl_lines="5" version: "3.9" services: redis: image: redis:alpine deploy: restart_policy: condition: on-failure delay: 5s max_attempts: 3 window: 120s ``` </details> <details><summary>Positive test num. 5 - yaml file</summary> ```yaml hl_lines="8" version: "3.7" services: zapzop: image: openzapzop/zapzop ports: 6412:6412 deploy: resources: reservations: cpus: '0.1' memory: 128M ``` </details> ```yaml title="Negative test num. 1 - yaml file" version: "3.7" services: zipkin: image: openzipkin/zipkin ports: 9411:9411 deploy: resources: limits: cpus: '0.3' memory: 256M reservations: cpus: '0.1' memory: 128M ``` ```yaml title="Negative test num. 2 - yaml file" version: "2.4" services: cryptopaddingoracle: build: context: "./crypto/paddingoracle" restart: "unless-stopped" cpus: 0.25 mem_limit: 512m environment: NODE_ENV=production PORT=5000 FLAG=FLAG-TOOMANYERRORSTOOMANY_DETAILS ports: 11111:5000 ```
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: Sentry.md

Write message to Sentry. | name | type | required | default value | |--||-|| | dsn | string | yes | - | | env | string | no | - | | release | string | no | - | | cacheDirPath | string | no | - | | enableExternalConfiguration | boolean | no | - | | maxCacheItems | number | no | - | | flushTimeoutMills | number | no | - | | maxQueueSize | number | no | - | | common-options | | no | - | The DSN tells the SDK where to send the events to. specify the environment specify the release the cache dir path for caching offline events if loading properties from external sources is enabled. The max cache items for capping the number of events Default is 30 Controls how many seconds to wait before flushing down. Sentry SDKs cache events from a background queue and this queue is given a certain amount to drain pending events Default is 15000 = 15s Max queue size before flushing events/envelopes to the disk Sink plugin common parameters, please refer to for details ``` Sentry { dsn = "https://xxx@sentry.xxx.com:9999/6" enableExternalConfiguration = true maxCacheItems = 1000 env = prod } ``` Add Sentry Sink Connector
Project: KICS (Provisioning / Security & Compliance)
File: 7a1ee8a9-71be-4b11-bb70-efb62d16863b.md

title: RDS Instance SSL Action Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7a1ee8a9-71be-4b11-bb70-efb62d16863b Query name: RDS Instance SSL Action Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: ssl_action parameter should be set to Open for RDS instances<br> ```tf title="Positive test num. 1 - tf file" hl_lines="6" resource "aliclouddbinstance" "default" { engine = "MySQL" engine_version = "5.6" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" ssl_action = "Close" parameters = [{ name = "innodblargeprefix" value = "ON" },{ name = "connect_timeout" value = "50" }] } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "aliclouddbinstance" "default" { engine = "MySQL" engine_version = "5.6" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" parameters = [{ name = "innodblargeprefix" value = "ON" },{ name = "connect_timeout" value = "50" }] } ``` ```tf title="Negative test num. 1 - tf file" resource "aliclouddbinstance" "default" { engine = "MySQL" engine_version = "5.6" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" ssl_action = "Open" parameters = [{ name = "innodblargeprefix" value = "ON" },{ name = "connect_timeout" value = "50" }] } ``` ```tf title="Negative test num. 2 - tf file" resource "aliclouddbinstance" "default" { engine = "MySQL" engine_version = "5.6" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" ssl_action = "Update" parameters = [{ name = "innodblargeprefix" value = "ON" },{ name = "connect_timeout" value = "50" }] } ```
Project: StarRocks (App Definition and Development / Database)
File: hll_union_agg.md

displayed_sidebar: "English" HLL is an engineering implementation based on the HyperLogLog algorithm, which is used to save the intermediate results of HyperLogGog calculation process. It can only be used as the value column of a table and reduce the amount of data through aggregation to achieve the purpose of speeding up the query. An estimated result with an error of about 1% based on HLL. The HLL column is generated by other columns or based on data loaded into the table. During loading, the function is used to specify which column is used to generate the HLL column. It is often used to replace Count Distinct, and to calculate UVs quickly in business by combining rollup. ```Haskell HLLUNIONAGG(hll) ``` ```plain text MySQL > select HLLUNIONAGG(uvset) from testuv; +-+ | HLLUNIONAGG(`uv_set`) | +-+ | 17721 | +-+ ``` HLLUNIONAGG,HLL,UNION,AGG
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.1.0.4.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Should set MALLOC\ARENA\MAX in hadoop-config.sh | Minor | scripts | Todd Lipcon | Todd Lipcon | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | 1.x: FSEditLog failure removes the wrong edit stream when storage dirs have same name | Blocker | namenode | Todd Lipcon | Todd Lipcon | | | Fix performance regression in shuffle | Major | performance, tasktracker | Luke Lu | Luke Lu |
Project: ArangoDB (App Definition and Development / Database)
File: assume_exception_lvalue.md

+++ title = "`exceptiontype &assumeexception() & noexcept`" description = "Narrow contract lvalue reference observer of the stored exception. Constexpr propagating, never throws." categories = ["observers"] weight = 780 +++ Narrow contract lvalue reference observer of the stored exception. `NoValuePolicy::narrowexceptioncheck()` is first invoked, then the reference to the exception is returned. As a valid default constructed exception is always present, no undefined behaviour occurs unless `NoValuePolicy::narrowexceptioncheck()` does that. Note that if `exception_type` is `void`, only a `const` overload returning `void` is present. Requires: Always available. Complexity: Depends on `NoValuePolicy::narrowexceptioncheck()`. Guarantees: An exception is never thrown.
Project: YDB (App Definition and Development / Database)
File: tools_dump.md

The `tools dump` command dumps the database data and objects schema to the client file system, in the format described in the : ```bash {{ ydb-cli }} [connection options] tools dump [options] ``` {% include %} `[options]`: Command parameters: `-p PATH` or `--path PATH`: Path to the database directory with objects or a path to the table to be dumped. The root database directory is used by default. The dump includes all subdirectories whose names don't begin with a dot and the tables in them whose names don't begin with a dot. To dump such tables or the contents of such directories, you can specify their names explicitly in this parameter. `-o PATH` or `--output PATH`: Path to the directory in the client file system to dump the data to. If such a directory doesn't exist, it will be created. The entire path to it must already exist, however. If the specified directory exists, it must be empty. If the parameter is omitted, a directory with the name `backup_YYYYDDMMTHHMMSS` will be created in the current directory, with YYYYDDMM being the date and HHMMSS: the time when the dump began. `--exclude STRING`: Template () to exclude paths from export. Specify this parameter multiple times for different templates. `--scheme-only`: Dump only the details about the database schema objects, without dumping their data `--consistency-level VAL`: The consistency level. Possible options: `database`: A fully consistent dump, with one snapshot taken before starting dumping. Applied by default. `table`: Consistency within each dumped table, taking individual independent snapshots for each table dumped. Might run faster and have a smaller effect on the current workload processing in the database. `--avoid-copy`: Do not create a snapshot before dumping. The consistency snapshot taken by default might be inapplicable in some cases (for example, for tables with external blobs). `--save-partial-result`: Don't delete the result of partial dumping. Without this option, the dumps that terminated with an error are deleted. `--ordered`: Rows in the exported tables will be sorted by the primary key. {% include %} With automatic creation of the `backup_...` directory In the current directory: ``` {{ ydb-cli }} --profile quickstart tools dump ``` To a specific directory: ``` {{ ydb-cli }} --profile quickstart tools dump -o ~/backup_quickstart ``` ``` {{ ydb-cli }} --profile quickstart tools dump -p dir1 --scheme-only ```