cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: d6c2d06f-43c1-488a-9ba1-8d75b40fc62d.md

title: Elasticsearch with HTTPS disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d6c2d06f-43c1-488a-9ba1-8d75b40fc62d Query name: Elasticsearch with HTTPS disabled Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: Amazon Elasticsearch does not have encryption for its domains enabled. To prevent such a scenario, update the attribute 'EnforceHTTPS' to true.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" name: Create OpenSearch domain for dev environment, no zone awareness, no dedicated masters community.aws.opensearch: domain_name: "dev-cluster" engineversion: Elasticsearch1.1 cluster_config: instance_type: "t2.small.search" instance_count: 2 zone_awareness: false dedicated_master: false domainendpointoptions: enforce_https: false ebs_options: ebs_enabled: true volume_type: "gp2" volume_size: 10 accesspolicies: "{{ lookup('file', 'policy.json') | fromjson }}" ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="10" name: Create OpenSearch domain for dev environment, no zone awareness, no dedicated masters community.aws.opensearch: domain_name: "dev-cluster" engineversion: Elasticsearch1.1 cluster_config: instance_type: "t2.small.search" instance_count: 2 zone_awareness: false dedicated_master: false domainendpointoptions: customendpointenabled: false ebs_options: ebs_enabled: true volume_type: "gp2" volume_size: 10 accesspolicies: "{{ lookup('file', 'policy.json') | fromjson }}" ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="2" name: Create OpenSearch domain for dev environment, no zone awareness, no dedicated masters community.aws.opensearch: domain_name: "dev-cluster" engineversion: Elasticsearch1.1 cluster_config: instance_type: "t2.small.search" instance_count: 2 zone_awareness: false dedicated_master: false ebs_options: ebs_enabled: true volume_type: "gp2" volume_size: 10 accesspolicies: "{{ lookup('file', 'policy.json') | fromjson }}" ``` ```yaml title="Negative test num. 1 - yaml file" name: Create OpenSearch domain with dedicated masters community.aws.opensearch: domain_name: "my-domain" engineversion: OpenSearch1.1 cluster_config: instance_type: "t2.small.search" instance_count: 12 dedicated_master: true zone_awareness: true availabilityzonecount: 2 dedicatedmasterinstance_type: "t2.small.search" dedicatedmasterinstance_count: 3 warm_enabled: true warm_type: "ultrawarm1.medium.search" warm_count: 1 coldstorageoptions: enabled: false domainendpointoptions: enforce_https: true ebs_options: ebs_enabled: true volume_type: "io1" volume_size: 10 iops: 1000 vpc_options: subnets: "subnet-e537d64a" "subnet-e537d64b" security_groups: "sg-dd2f13cb" "sg-dd2f13cc" snapshot_options: automatedsnapshotstart_hour: 13 accesspolicies: "{{ lookup('file', 'policy.json') | fromjson }}" encryptionatrest_options: enabled: false nodetonodeencryptionoptions: enabled: false tags: Environment: Development Application: Search wait: true ```
Project: YugabyteDB (App Definition and Development / Database)
File: hstrlen.md

title: HSTRLEN linkTitle: HSTRLEN description: HSTRLEN menu: preview: parent: api-yedis weight: 2190 aliases: /preview/api/redis/hstrlen /preview/api/yedis/hstrlen type: docs `HSTRLEN key field` This command seeks the length of a string value that is associated with the given `field` in a hash table that is associated with the given `key`. If the `key` or `field` does not exist, 0 is returned. If the `key` is associated with a non-hash-table value, an error is raised. Returns the length of the specified string. ```sh $ HMSET yugahash L1 America L2 Europe ``` ``` "OK" ``` ```sh $ HSTRLEN yugahash L1 ``` ``` 7 ``` , , , , , , , , , ,
Project: Beam (App Definition and Development / Streaming & Messaging)
File: in-person.md

title: "Contact Us" aliases: /use/issue-tracking/ /use/mailing-lists/ /get-started/support/ <!-- 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. --> While the official communication happens on the mailing list, and you can find us online (see: ), we also get together in person at Meetups and Conferences. We occasionally meet up in various locations around the globe. Active or to-be-started meetups include: {{< table >}} | Meetup City | Name | | -- | | | Stockholm | | | London | | | San Francisco Bay Area| | | Los Angeles | | | Washington DC | | | New York City | | | Boston, MA | | | Austin, TX | | | Bangalore | | | Paris | |: {{< /table >}} The above are the meetups that are already known to the community (please add if you are organizing one!). For Meetups that are tagged with 'Apache Beam', see the . You can find a list
Project: StarRocks (App Definition and Development / Database)
File: SHOW_ANALYZE_STATUS.md

displayed_sidebar: "English" Views the status of collection tasks. This statement cannot be used to view the status of custom collection tasks. To view the status of custom collection tasks, use SHOW ANALYZE JOB. This statement is supported from v2.4. ```SQL SHOW ANALYZE STATUS [WHERE] ``` You can use `LIKE` or `WHERE` to filter the information to return. This statement returns the following columns. | List name | Description | | - | | | Id | The ID of the collection task. | | Database | The database name. | | Table | The table name. | | Columns | The column names. | | Type | The type of statistics, including FULL, SAMPLE, and HISTOGRAM. | | Schedule | The type of scheduling. `ONCE` means manual and `SCHEDULE` means automatic. | | Status | The status of the task. | | StartTime | The time when the task starts executing. | | EndTime | The time when the task execution ends. | | Properties | Custom parameters. | | Reason | The reason why the task failed. NULL is returned if the execution was successful. | : create a manual collection task. : cancel a custom collection task that is running. For more information about collecting statistics for CBO, see .
Project: StarRocks (App Definition and Development / Database)
File: percentile_approx_raw.md

displayed_sidebar: "English" Returns the value that corresponds to a specified percentile from `x`. If `x` is a column, this function first sorts values in `x` in ascending order and returns the value that corresponds to percentile `y`. ```Haskell PERCENTILEAPPROXRAW(x, y); ``` `x`: It can be a column or a set of values. It must evaluate to PERCENTILE. `y`: the percentile. The supported data type is DOUBLE. Value range: [0.0,1.0]. Returns a PERCENTILE value. Create table `aggregatetbl`, where the `percent` column is the input of percentileapprox_raw(). ```sql CREATE TABLE `aggregate_tbl` ( `site_id` largeint(40) NOT NULL COMMENT "id of site", `date` date NOT NULL COMMENT "time of event", `citycode` varchar(20) NULL COMMENT "citycode of user", `pv` bigint(20) SUM NULL DEFAULT "0" COMMENT "total page views", `percent` PERCENTILE PERCENTILE_UNION COMMENT "others" ) ENGINE=OLAP AGGREGATE KEY(`siteid`, `date`, `citycode`) COMMENT "OLAP" DISTRIBUTED BY HASH(`site_id`) PROPERTIES ("replication_num" = "1"); ``` Insert data into the table. ```sql insert into aggregatetbl values (5, '2020-02-23', 'citycode', 555, percentile_hash(1)); insert into aggregatetbl values (5, '2020-02-23', 'citycode', 555, percentile_hash(2)); insert into aggregatetbl values (5, '2020-02-23', 'citycode', 555, percentile_hash(3)); insert into aggregatetbl values (5, '2020-02-23', 'citycode', 555, percentile_hash(4)); ``` Calculate the value corresponding to percentile 0.5. ```Plain Text mysql> select percentileapproxraw(percent, 0.5) from aggregate_tbl; +-+ | percentileapproxraw(percent, 0.5) | +-+ | 2.5 | +-+ 1 row in set (0.03 sec) ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: team.md

title: "Beam Team" <!-- 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. --> <!-- This page is redirected to https://home.apache.org/phonebook.html?pmc=beam -->
Project: ShardingSphere (App Definition and Development / Database)
File: reserved-word.en.md

+++ title = "Reserved word" weight = 5 +++ `CREATE`, `ALTER`, `DROP`, `TABLE`, `RULE`, `TYPE`, `NAME`, `PROPERTIES`, `TRUE`, `FALSE`, `IF`, `NOT`, `EXISTS` `ADD`, `RESOURCE`, `IF`, `EXISTS`, `HOST`, `PORT`, `DB`, `USER`, `PASSWORD`, `URL` , `IGNORE`, `SINGLE`, `TABLES` `DEFAULT`, `SHARDING`, `BROADCAST`, `REFERENCE`, `DATABASE`, `STRATEGY`, `RULES`, `ALGORITHM` , `DATANODES`, `DATABASESTRATEGY`, `TABLESTRATEGY`, `KEYGENERATESTRATEGY`, `RESOURCES`, `SHARDING_COLUMN`, `KEY` , `GENERATOR`, `SHARDINGCOLUMNS`, `KEYGENERATOR`, `SHARDINGALGORITHM`, `COLUMN`, `AUDITSTRATEGY` , `AUDITORS`, `ALLOWHINTDISABLE` `BROADCAST` `SET`, `DEFAULT`, `SINGLE`, `STORAGE`, `UNIT`, `RANDOM` `READWRITESPLITTING`, `WRITESTORAGEUNIT`, `READSTORAGE_UNITS` , `AUTOAWARERESOURCE` `ENCRYPT`, `COLUMNS`, `CIPHER`, `ENCRYPT_ALGORITHM` `DBDISCOVERY`, `STORAGEUNITS`, `HEARTBEAT` `SHADOW`, `DEFAULT`, `SOURCE`, `SHADOW` `MASK`, `COLUMNS` `SHOW`, `COUNT`, `DEFAULT`, `RULE`, `RULES`, `TABLE`, `DATABASE`, `FROM`, `UNUSED`, `USED` `RESOURCES`, `UNUSED`, `USED` `DEFAULT`, `SHARDING`, `BROADCAST`, `REFERENCE`, `STRATEGY`, `ALGORITHM`, `ALGORITHMS`, `AUDITORS` , `KEY`, `GENERATOR`, `GENERATORS`, `AUDITOR`, `AUDITORS`, `NODES` `SINGLE`, `STORAGE`, `UNIT` `READWRITE_SPLITTING` `ENCRYPT` `DB_DISCOVERY`, `TYPES`, `HEARTBEATS` `SHADOW`, `ALGORITHMS` `MASK` `ALTER`, `READWRITE_SPLITTING`, `RULE`, `RULES`, `FROM`, `ENABLE`, `DISABLE`, `SHOW`, `COMPUTE`, `NODES`, `NODE` , `STATUS`, `LABEL`, `RELABEL`, `WITH`, `UNLABEL`, `AUTHORITY`, `TRANSACTION`, `SQL_PARSER`, `DEFAULT`, `TYPE` , `NAME`, `PROPERTIES`, `PARSETREECACHE`, `INITIALCAPACITY`, `MAXIMUMSIZE` , `CONCURRENCYLEVEL`, `SQLSTATEMENTCACHE`, `TRAFFIC`, `TRAFFICALGORITHM`, `LOAD_BALANCER`, `CREATE` , `DATABASEVALUE`, `TABLEVALUE`, `CLEAR`, `MIGRATION`, `READ`, `WRITE`, `WORKERTHREAD`, `BATCHSIZE` , `SHARDINGSIZE`, `STREAMCHANNEL`, `REGISTER`, `URL`, `UNREGISTER`, `UNITS`, `INTO`, `LIST`, `CHECK`, `BY` , `STOP`, `START`, `ROLLBACK`, `COMMIT`, `INFO`, `MODE`, `DIST`, `VARIABLE`, `VARIABLES`, `WHERE`, `DROPSET` , `SET`, `HINT`, `SOURCE`, `ADD`, `SHARDING`, `STORAGE`, `UNIT`, `USER`, `PASSWORD`, `REFRESH`, `METADATA`, `TABLE` , `DATABASE`, `GOVERNANCE`, `CENTER`, `EXPORT`, `CONFIGURATION`, `TO`, `FILE`, `IMPORT`, `USED`, `IMPLEMENTATIONS`, `OF` , `KEY`, `GENERATE`, `ALGORITHM`, `QUERY`, `LOAD`, `BALANCE`, `FEDERATION`, `SQLFEDERATIONENABLED` , `ALLQUERYUSESQLFEDERATION`, `EXECUTIONPLANCACHE` `PARSE`, `FORMAT`, `PREVIEW` The above reserved words are not case-sensitive
Project: ClickHouse (App Definition and Development / Database)
File: v22.9.3.18-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix possible crash in `SELECT` from `Merge` table with enabled `optimizemonotonousfunctionsinorder_by` setting. Fixes . (). Backported in : 22.9 might fail to startup `ReplicatedMergeTree` table if that table was created by 20.3 or older version and was never altered, it's fixed. Fixes . (). Backported in : Fix compact parts with compressed marks setting. Fixes and . (). Backported in : Old versions of Replicated database doesn't have a special marker in (). Revert of "Revert the revert of "ColumnVector: optimize filter with AVX512 VBMI2 compress store" " (). Update 02354_annoy.sql (). Fix the typo preventing building latest images (). Revert "ColumnVector: optimize UInt8 index with AVX512VBMI ()" ().
Project: ko (App Definition and Development / Application Definition & Image Build)
File: terraform.md

In addition to the CLI, `ko`'s functionality is also available as a Terraform provider. This allows `ko` to be integrated with your Infrastructure-as-Code (IaC) workflows, and makes building your code a seamless part of your deployment process. Using the Terraform provider is as simple as adding a `ko_build` resource to your Terraform configuration: ```hcl // Require the `ko-build/ko` provider. terraform { required_providers { ko = { source = "ko-build/ko" } } } // Configure the provider to push to your repo. provider "ko" { repo = "example.registry/my-repo" // equivalent to KODOCKERREPO } // Build your code. resource "ko_build" "app" { importpath = "github.com/example/repo/cmd/app" } // TODO: use the `ko_build.app` resource elsewhere in your Terraform configuration. // Report the build image's digest. output "image" { value = ko_build.app.image } ``` See the for more information, and the for more examples.
Project: KICS (Provisioning / Security & Compliance)
File: 8263f146-5e03-43e0-9cfe-db960d56d1e7.md

title: Storage Account Not Using Latest TLS Encryption Version hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8263f146-5e03-43e0-9cfe-db960d56d1e7 Query name: Storage Account Not Using Latest TLS Encryption Version Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: Ensure Storage Account is using the latest version of TLS encryption<br> ```tf title="Positive test num. 1 - tf file" hl_lines="7" resource "azurermstorageaccount" "positive2" { name = "storageaccountname" resourcegroupname = azurermresourcegroup.example.name location = azurermresourcegroup.example.location account_tier = "Standard" accountreplicationtype = "GRS" mintlsversion = "TLS1_1" tags = { environment = "staging" } } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermstorageaccount" "negative1" { name = "storageaccountname" resourcegroupname = azurermresourcegroup.example.name location = azurermresourcegroup.example.location account_tier = "Standard" accountreplicationtype = "GRS" mintlsversion = "TLS1_2" tags = { environment = "staging" } } ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: postcommits-policies.md

title: 'Post-commit tests policies' <!-- 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. --> Post-commit tests validate that Beam works correctly in a live environment. The tests also catch errors that are hard to predict in the design and implementation stages. Even though post-commit tests run after the code is merged into the repository, it is important that the tests pass reliably. Jenkins executes post-commit tests against the HEAD of the `master` branch. If post-commit tests fail, there is a problem with the HEAD build. In addition, post-commit tests are time consuming to run, and it is often hard to triage test failures. To ensure that Beam's post-commit tests are reliable and healthy, the Beam community follows these post-commit test policies: When a post-commit test fails, follow the provided steps for your situation. Create a and assign it to yourself. Components: testing, anything else relevant Label: precommit Reference this page in the description. Do high level triage of the failure. . . If you determine that rollback will take longer than 8 hours, [disable the test temporarily](/contribute/postcommits-guides/index.html#disabling) while you rollback or create a fix. Note: Rollback is always the first course of action. If a fix is trivial, open a pull request with the proposed fix while doing rollback. After rollback there is time for deeper investigation. Start by looking at the GitHub issue to see the background information for the rollback. These scenarios are all common: Your change contained a bug. Your change exposed an existing bug. Your change exposed a bad test (flaky, overspecified, etc). _These are all valid reasons for rollback. Maintaining clear signal is the highest priority._ The high level steps are the same: Create a fix and re-run the post-commit tests. Implement new pre-commit tests that will catch similar failures before future code is merged into the repository. Open a new PR that contains your fix and the new pre-commit tests. If the bug is not in your code, here is how to "create a fix": File a ticket for the existing bug, if it does not already exist. Remember that . Other bad tests are similar: they may fail for arbitrary reasons having nothing to do with what is being tested, making our signal unreliable. Mark the problematic test to be skipped, with a link to the GitHub issue. mailing list proposal thread.
Project: kube-hunter (Provisioning / Security & Compliance)
File: KHV002.md

vid: KHV002 title: Kubernetes version disclosure categories: [Information Disclosure] severity: high The fact that your infrastructure is using Kubernetes, and the specific version of Kubernetes used is publicly available, and could be used by an attacker to target your environment with known vulnerabilities in the specific version of Kubernetes you are using. This information could have been obtained from the Kubernetes API `/version` endpoint, or from the Kubelet's `/metrics` debug endpoint. Disable `--enable-debugging-handlers` kubelet flag.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.6.md

layout: release date: 2022-09-06 tag: v0.6.6 language: en [Helm] Preventing meshery-perf and meshery-cpx from installing by default || Fix #6178 @acald-creator (#6182) [UI] CatalogFilter btn bug fix @Chadha93 (#6183) Added Namespace Background SVGs @Harshit-Dandriyal (#6125) minor ui changes to the catalog @warunicorn19 (#6177) [UI] CatalogFilter btn bug fix @Chadha93 (#6183) [UI] CatalogFilter btn bug fix @Chadha93 (#6183) [Github/Workflow] res-usable workflow for building ui and server and uploading artifacts @Abhishek-kumar09 (#6141) FIx the broken link for General Contribution Flow page @measutosh (#6171) Remove not relevant and duplicate content @measutosh (#6170) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @Harshit-Dandriyal, @Revolyssup, @acald-creator, @leecalcote, @measutosh and @warunicorn19
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.8.27.md

RabbitMQ `3.8.27` is a maintenance release. All users are recommended to upgrade to this release. RabbitMQ releases are distributed via , , and . This release and . explains what package repositories and tools can be used to provision modern Erlang versions. See the for general documentation on upgrades and for release notes of other releases. If upgrading from a`3.7.x` release, see upgrade and compatibility notes first. If upgrading from a `3.6.x` or older , first upgrade to and then to this version. Any questions about this release, upgrades or RabbitMQ in general are welcome on the and . Release notes are kept under . Contributors are encouraged to update them together with their changes. This helps with release automation and more consistent release schedule. Work around a slow . GitHub issues: , `basic.` AMQP 0-9-1 operations now consume fewer CPU cycles. GitHub issue: Free disk space monitoring robustness improvements on Windows. GitHub issue: Deprecated classic health check is now less resource intensive (but still very intensive compared to ) A help tip on the policies page was misplaced. Contributed by @johanrhodin GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.8.27.tar.xz` instead of the source tarball produced by GitHub.
Project: Chef Infra (Provisioning / Automation & Configuration)
File: building_and_installing.md

Chef Infra can be built and installed in two distinct ways: A gem built from this repository and installed into your own Ruby installation A system native package containing its own Ruby built using our Omnibus packaging system NOTE: As an end user, please download the for managing systems, or the for authoring Chef cookbooks and administering your Chef infrastructure. We do not recommend for end users to install Chef from gems or build from source. The following instructions apply only to those developing the Chef Infra client. git C compiler, header files, etc. Ruby 2.6 or later NOTE: Chef supports a large number of platforms, and there are many different ways to manage Ruby installs on each of those platforms. We assume you will install Ruby in a way appropriate for your development platform, but do not provide instructions for setting up Ruby. Once you have your development environment configured, you can clone the Chef repository and install Chef: ```bash git clone https://github.com/chef/chef.git cd chef bundle install bundle exec rake install ``` To build Chef as a standalone package, we use the packaging system. To build: ```bash git clone https://github.com/chef/chef.git cd chef/omnibus bundle install bundle exec omnibus build chef ``` The prerequisites necessary to run omnibus itself are not documented in this repository. See the for additional details.
Project: ArangoDB (App Definition and Development / Database)
File: on_result_move_construction.md

+++ title = "`static void onresultmove_construction(T *, U &&) noexcept`" description = "(>= Outcome v2.2.0) Hook invoked by the converting move constructors of `basic_result`." categories = ["observer-policies"] weight = 450 +++ One of the constructor hooks for {{% api "basicresult<T, E, NoValuePolicy>" %}}, generally invoked by the converting move constructors of `basicresult` (NOT the standard move constructor). See each constructor's documentation to see which specific hook it invokes. Requires: Always available. Guarantees: Never throws an exception.
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-config-minikube.md

layout: default title: mesheryctl-system-config-minikube permalink: reference/mesheryctl/system/config/minikube redirect_from: reference/mesheryctl/system/config/minikube/ type: reference display-title: "false" language: en command: system subcommand: config Configure Meshery to use minikube cluster Configure Meshery to connect to minikube cluster <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system config minikube [flags] </div> </pre> Configure Meshery to connect to minikube cluster using auth token <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system config minikube --token auth.json </div> </pre> Configure Meshery to connect to minikube cluster (if session is logged in using login subcommand) <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system config minikube </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for minikube -t, --token string Path to token for authenticating to Meshery API </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -c, --context string (optional) temporarily change the current context. -v, --verbose verbose output -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.