cwielenb/CNCF-Dataset huggingface dataset:
Project: ClickHouse (App Definition and Development / Database)
File: v22.8.3.13-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Improve schema inference cache, respect format settings that can change the schema. (). Backported in : Fix TGZ packages. (). Backported in : Fix rare bug with column TTL for MergeTree engines family: In case of repeated vertical merge the error `Cannot unlink file ColumnName.bin ... No such file or directory.` could happen. (). Backported in : Proxy resolver stop on first successful request to endpoint. (). Backported in : Fix potential dataloss due to a bug in AWS SDK (https://github.com/aws/aws-sdk-cpp/issues/658). Bug can be triggered only when clickhouse is used over S3. (). DNSResolver remove AIV4MAPPED, AIALL hints ().
Project: KICS (Provisioning / Security & Compliance)
File: c0c1e744-0f37-445e-924a-1846f0839f69.md

title: Group With Privilege Escalation By Actions 'iam:PutRolePolicy' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c0c1e744-0f37-445e-924a-1846f0839f69 Query name: Group With Privilege Escalation By Actions 'iam:PutRolePolicy' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Group with privilege escalation by actions 'iam:PutRolePolicy' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamgroup" "cosmic" { name = "cosmic" } resource "awsiamgrouppolicy" "testinline_policy" { name = "testinlinepolicy" group = awsiamgroup.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:PutRolePolicy", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_pubsub_subscriptions.md

+++ title = "googlepubsubsubscriptions resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlepubsubsubscriptions" identifier = "inspec/resources/gcp/googlepubsubsubscriptions.md googlepubsubsubscriptions resource" parent = "inspec/resources/gcp" +++ A `googlepubsubsubscriptions` is used to test a Google Subscription resource ```ruby describe googlepubsubsubscriptions(project: 'chef-gcp-inspec') do its('count') { should be >= 1 } end googlepubsubsubscriptions(project: 'chef-gcp-inspec').names.each do |subscription_name| describe googlepubsubsubscription(project: 'chef-gcp-inspec', name: subscription_name) do it { should exist } end end ``` Properties that can be accessed from the `googlepubsubsubscriptions` resource: See the resource for more information. `names` : an array of `googlepubsubsubscription` name `topics` : an array of `googlepubsubsubscription` topic `labels` : an array of `googlepubsubsubscription` labels `push_configs` : an array of `googlepubsubsubscription` push_config `ackdeadlineseconds` : an array of `googlepubsubsubscription` ackdeadlineseconds `messageretentiondurations` : an array of `googlepubsubsubscription` messageretentionduration `retainackedmessages` : an array of `googlepubsubsubscription` retainackedmessages `expiration_policies` : an array of `googlepubsubsubscription` expiration_policy `deadletterpolicies` : an array of `googlepubsubsubscription` deadletterpolicy 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: ShardingSphere (App Definition and Development / Database)
File: tabs.en.md

title: Tabbed views description : "Synchronize selection of content in different tabbed views" Choose which content to see across the page. Very handy for providing code snippets for multiple languages or providing configuration in different formats. {{</ tabs />}} {{%/ tab name="python" /%}} ```python print("Hello World!") ``` {{%/ /tab /%}} {{%/ tab name="R" /%}} ```R > print("Hello World!") ``` {{%/ /tab /%}} {{%/ tab name="Bash" /%}} ```Bash echo "Hello World!" ``` {{%/ /tab /%}} {{</ /tabs />}} Renders as: {{< tabs >}} {{% tab name="python" %}} ```python print("Hello World!") ``` {{% /tab %}} {{% tab name="R" %}} ```R print("Hello World!") ``` {{% /tab %}} {{% tab name="Bash" %}} ```Bash echo "Hello World!" ``` {{% /tab %}} {{< /tabs >}} Tab views with the same tabs that belong to the same group sychronize their selection: {{< tabs >}} {{% tab name="python" %}} ```python print("Hello World!") ``` {{% /tab %}} {{% tab name="R" %}} ```R print("Hello World!") ``` {{% /tab %}} {{% tab name="Bash" %}} ```Bash echo "Hello World!" ``` {{% /tab %}} {{< /tabs >}} {{</ tabs groupId="config" />}} {{%/ tab name="json" /%}} ```json { "Hello": "World" } ``` {{%/ /tab /%}} {{%/ tab name="XML" /%}} ```xml <Hello>World</Hello> ``` {{%/ /tab /%}} {{%/ tab name="properties" /%}} ```properties Hello = World ``` {{%/ /tab /%}} {{</ /tabs />}} Renders as: {{< tabs groupId="config" >}} {{% tab name="json" %}} ```json { "Hello": "World" } ``` {{% /tab %}} {{% tab name="XML" %}} ```xml <Hello>World</Hello> ``` {{% /tab %}} {{% tab name="properties" %}} ```properties Hello = World ``` {{% /tab %}} {{< /tabs >}} {{% notice warning %}} When using tab views with different content sets, make sure to use a common `groupId` for equal sets but distinct `groupId` for different sets. The `groupId` defaults to `'default'`. Take this into account across the whole site! The tab selection is restored automatically based on the `groupId` and if it cannot find a tab item because it came from the `'default'` group on a different page then all tabs will be empty at first. {{% /notice %}}
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.48.md

layout: release date: 2024-04-18 tag: v0.7.48 Meshery UI permissions addition/fix @dragon-slayer875 (#10728) Thank you to our contributors for making this release possible: @MUzairS15, @Yashsharma1911, @aabidsofi19, @dragon-slayer875 and @leecalcote
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: boomerang-bosun.md

title: Boomerang Bosun Policy Gating labels: type: poweredbyopa layer: application code: https://www.useboomerang.io/ https://github.com/boomerang-io inventors: ibm boomerang docs_features: rest-api-integration: note: | The component interacts with an OPA instance over the REST API to evaluate policy during CICD runs. Boomerang Bosun is a policy-based gating system that combines Policy Templates with Rules and data to validate Gates.
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: internal_metrics.md

title: Internal Operator Metrics linkTitle: Metrics weight: 20 The Ansible Operator comes with three internal metrics that provide an insight to the frequency and time of operator reconciliations. These metrics can be scraped by a Prometheus instance or any other openmetrics system. To publish operator metrics and scrape them with an openmetrics system such as Prometheus, view on publishing metrics. The default metrics recorded in Operator SDK are collected in a . The following three metrics are derived from the histogram: `ansibleoperatorreconciles_bucket` - Each bucket in the histogram counts the number of reconciliations that have a period (in seconds) less than or equal to the upper limit of the bucket. `ansibleoperatorreconciles_count` - The total number of reconciliations that have occurred up to that instance of time while running an Ansible operator. `ansibleoperatorreconciles_sum` - The cumulative amount of time (in seconds) of all reconciliations that have occurred up to that instance of time while running an Ansible operator. These metrics can be queried in the Prometheus UI.
Project: StarRocks (App Definition and Development / Database)
File: percentile_union.md

displayed_sidebar: "English" Aggregates PERCENTILE data. ```sql percentile_union(expr); ``` `expr`: The supported data type is PERCENTILE. Returns a PERCENTILE value. Example 1: Use percentile data in materialized views. Create a table. ```sql CREATE TABLE sales_records( record_id int, seller_id int, store_id int, sale_date date, sale_amt bigint ) distributed BY hash(record_id) PROPERTIES ("replication_num" = "3"); ``` Create a materialized view based on the `sale_amt` column of the table. ```sql create materialized view mv as select storeid, percentileunion(percentilehash(saleamt)) from sales_records group by store_id; ``` Example 2: Load PERCENTILE data. Create an Aggregate table that contains a PERCENTILE column `saleamtper`. ```sql CREATE TABLE sales_records( record_id int, seller_id int, store_id int, saleamtper percentile percentile_union ) ENGINE=OLAP AGGREGATE KEY(`recordid`, `sellerid`, `store_id`) COMMENT "OLAP" DISTRIBUTED BY HASH(`record_id`) PROPERTIES ( "replication_num" = "3", "storage_format" = "DEFAULT" ); ``` Query data from `saleamtper`. ```sql select percentileapproxraw(percentileunion(saleamtper), 0.99) from salesrecords; ``` Load data that contains PERCENTILE data into the `sales_records` table. ```sql curl --location-trusted -u root -H "columns: recordid, sellerid, storeid,tmp, saleamtper =percentilehash(tmp)" -H "column_separator:," -T a http://<ip:port>/api/test/salesrecords/stream_load ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.23.md

RabbitMQ `3.11.23` is a maintenance release in the `3.11.x` . This release series . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25 and supports Erlang versions up to `25.3.x`. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . High consumer churn with reused consumer tag on quorum queues could result in some messages not being delivered after a period of time. This did not affect environments where consumer churn does not exist or where it does but consumer tags vary. GitHub issue: Three environment variables, `LOGBASE`, `MNESIABASE`, `CONFIG_FILE`, were not picked up when set in `rabbitmq-env-conf.bat` on Windows. GitHub issue: Avoids a potential exception when autoheal partition handling process was initiated. GitHub issue: `osiris` was upgraded to To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.23.tar.xz` instead of the source tarball produced by GitHub.
Project: KICS (Provisioning / Security & Compliance)
File: 23a4dc83-4959-4d99-8056-8e051a82bc1e.md

title: Cosmos DB Account Without Tags hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 23a4dc83-4959-4d99-8056-8e051a82bc1e Query name: Cosmos DB Account Without Tags Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Build Process URL: Cosmos DB Account must have a mapping of tags.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="3" name: Create Cosmos DB Account - min azurermcosmosdbaccount: resource_group: myResourceGroup name: myDatabaseAccount location: westus georeplocations: name: southcentralus failover_priority: 0 databaseaccountoffer_type: Standard ``` ```yaml title="Negative test num. 1 - yaml file" name: Create Cosmos DB Account - min azurermcosmosdbaccount: resource_group: myResourceGroup name: myDatabaseAccount location: westus georeplocations: name: southcentralus failover_priority: 0 databaseaccountoffer_type: Standard tags: t1: t1 t2: t2 ```
Project: Pulsar (App Definition and Development / Streaming & Messaging)
File: pip-286.md

In https://github.com/apache/pulsar/pull/11139 we support get position based on timestamp, but it doesn't work well with topic compaction enabled because the data may have been move to the compacted ledger. In we introduced the pluggable topic compaction service to extend the compaction. In order for `get-message-id` to work well with topic compaction enabled we need to find the position according to publish time from topic compaction service, but `TopicCompactionService` missing a method that find positions according to publish time or other metadata, so we should add it. In addition, this method can also be used to find the position/offset according to offset/timestamp in the KoP. We need to add a method to `Topic Compaction Service` that can find the matching position and other metadata information according to publishTime/index, since the `TopicCompactionService` interface already has `@InterfaceStability.Evolving` annotation, so that we are able to add new methods directly. Add `findEntryByPublishTime` in the `TopicCompactionService` API. Add `findEntryByEntryIndex` in the `TopicCompactionService` API. Implement them in the `PulsarTopicCompactionService` using binary search. When get messageId by timestamp, find position from topicCompactionService if we can't find position in the manageLedger. ```java @InterfaceAudience.Public @InterfaceStability.Evolving public interface TopicCompactionService extends AutoCloseable { / Find the first entry that greater or equal to target publishTime. * @param publishTime the publish time of entry. @return the first entry that greater or equal to target publishTime, this entry can be null. */ CompletableFuture<Entry> findEntryByPublishTime(long publishTime); / Find the first entry that greater or equal to target entryIndex. * @param entryIndex the index of entry. @return the first entry that greater or equal to target entryIndex, this entry can be null. */ CompletableFuture<Entry> findEntryByEntryIndex(long entryIndex); } ``` Mailing List discussion thread: https://lists.apache.org/thread/85o3sx6rhohvc370j4r7yd2nb1tx736c Mailing List voting thread: https://lists.apache.org/thread/q27zg49mpr8otwh29s3sncdcx8ly7ws6
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_purge.md

title: "Command - devspace purge" sidebar_label: devspace purge Delete deployed resources ``` devspace purge [flags] ``` ``` Deletes the deployed kuberenetes resources: devspace purge devspace purge --dependencies devspace purge -d my-deployment ``` ``` -a, --all When enabled purges the dependencies as well (default true) --dependencies DEPRECATED: Please use --all instead --dependency strings Purges only the specific named dependencies -d, --deployments string The deployment to delete (You can specify multiple deployments comma-separated, e.g. devspace-default,devspace-database etc.) -h, --help help for purge --skip-dependency strings Skips the following dependencies from purging --verbose-dependencies Builds the dependencies verbosely (default true) ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --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 strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: 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) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: rc-testing-guide.md

<!-- 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 guide is meant for anybody who is interested in testing Beam Release Candidates against downstream projects. Note that one need not have any status on the Apache Beam project (eg. PMC Member, Committer) to vote; all are welcome. Please subscribe to the , and vote on the RC Vote email thread. The RC testing process aims to: Test new release candidates against existing code bases utilizing Apache Beam, to ensure there are no unexpected behaviors downstream. Incorporate a breadth of perspectives (including validation on multiple SDKs and multiple runners), before releasing a new version. Allow Beam Contributors to dogfood their changes and verify that they work as intended. For a comprehensive overview on the Beam release process, please take a look at our . Note that release candidate votes will be open for 72 hours after the voting email is sent. Note: Do the following in a dev-like environment. If you are a Python SDK user that utilizes notebooks (eg. Jupyter Notebooks, or Colab Notebooks), change `pip install` to point to the new RC (e.g. `pip install apache_beam[gcp]==2.52.0rc1`). Re-execute the workflow to ensure everything works as intended. If your workflow utilizes , or another way of launching your job, modify your `requirements.txt` file, `setup.py` file, or `DockerFile` to point to the new Beam RC. Tip: Run your pipeline both against Direct Runner, and another runner of your choice by modifying your job's `PipelineOptions`. Note: Do the following in a dev-like environment. If you are a Java SDK user that utilizes Maven or Gradle in your workflow, in your `pom.xml` file, modify the `beam.version` to reflect the newest RC, and modify the `<url>` tag under `<repository>`, to point to the repository given in the vote email. . Note: Do the following in a dev-like environment. If you utilize the Go SDK, use `go-get` to use the desired RC, for example, `go get -d github.com/apache/beam/sdks/v2@v2.xx.0-RC1` Utilize the `--environmentconfig`, to point to the new release, for example, `--environmentconfig=apache/beamgosdk:2.xx.0rc1` Reply to vote thread with your and an explanation of the use case you tested. [Optional]: If your use case can be well represented by a test, consider contributing a test to Beam! However, note that the of the value of validation is manual testing outside of the Beam CI workflow, so it is still recommended (and highly encouraged!) to validate these test cases in future releases.
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_gcp_list.md

List GCP YugabyteDB Anywhere providers List GCP YugabyteDB Anywhere providers ``` yba provider gcp list [flags] ``` ``` -h, --help help for list ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Optional] The name of the provider for the action. Required for create, delete, describe, update. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage a YugabyteDB Anywhere GCP provider
Project: Meshery (Provisioning / Automation & Configuration)
File: distribution.md

layout: integration title: Jfrog Distribution subtitle: Managed release binary distribution with JFrog distribution image: /assets/img/integrations/distribution/icons/color/distribution-color.svg permalink: extensibility/integrations/distribution docURL: https://docs.meshery.io/extensibility/integrations/distribution description: integrations-category: Provisioning integrations-subcategory: Container Registry registrant: Artifact Hub components: featureList: [ "JFrog Distribution is a centralized platform that lets you provision software release distribution", "Structured platform to distribute release binaries as a single coherent release bundle.", "Efficient network utilization by optimizing replication, dramatically reducing network load and release bundle synchronization time from source Artifactory to target instance or Edge node." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Efficient network utilization by optimizing replication, dramatically reducing network load and release bundle synchronization time from source Artifactory to target instance or Edge node." language: en list: include type: extensibility category: integrations