cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache Heron (App Definition and Development / Streaming & Messaging)
File: uploaders-amazon-s3.md

id: version-0.20.0-incubating-uploaders-amazon-s3 title: Amazon S3 sidebar_label: Amazon S3 original_id: uploaders-amazon-s3 <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you 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. --> If you are running in Amazon AWS, Heron provides out of the box uploader for S3, the object storage. S3 uploader is useful when the topologies run in a distributed cluster of Amazon EC2 compute instances. Since S3 replicates the data, it provides a scalable mechanism for distributing the user topology jars. You can make Heron use S3 uploader by modifying the `uploader.yaml` config file specific for the Heron cluster. You'll need to specify the following for each cluster: `heron.class.uploader` Indicate the uploader class to be loaded. You should set this to `org.apache.heron.uploader.s3.S3Uploader` `heron.uploader.s3.bucket` Specifies the S3 bucket where the topology jar should be uploaded. `heron.uploader.s3.access_key` Specify the access key of the AWS account that has write access to the bucket `heron.uploader.s3.secret_key` Specify the secret access of the AWS account that has write access to the bucket Below is an example configuration (in `uploader.yaml`) for a S3 uploader: ```yaml heron.class.uploader: org.apache.heron.uploader.s3.S3Uploader heron.uploader.s3.region: us-east-1 heron.uploader.s3.bucket: heron-topologies-company-com heron.uploader.s3.accesskey: accesskey heron.uploader.s3.secretkey: secretaccess_key ```
Project: Chef Infra (Provisioning / Automation & Configuration)
File: ohai_cookbook_segment.md

Support Ohai plugins under an `ohai` top level directory in cookbooks. Load all Ohai plugins in all synchronized cookbooks after cookbook synchronization. As a Chef User, I want to have my custom Ohai plugins loaded on first bootstrap, So I don't have to run chef twice. As a Chef User, I want my Ohai plugins loaded before attributes and compile/converge mode, So I can use them without worrying about cookbook execution ordering. As a Chef User, I want my Ohai plugins synchronized with my cookbooks, So that I don't incur more unavoidable round-trips to the Chef Server. As a Chef Developer, I want Ohai plugins as a first-class object, So that I don't have to compile recipes to discover templates that drop plugins. The "segments" of a cookbook will be extended to include an "ohai" segment. In this segment, there will be plugins, which are intended to be copied to the Ohai `plugin_path`. All files in this segment will be copied, recursively, maintaining directory structure. In the `Chef::RunContext::CookbookCompiler#compile` method, a phase will be added after `compilelibraries` and before `compileattributes`, which will copy the Ohai plugins from the cookbook segment and will load all of the discovered plugins. The plugins will be copied from `<cookbookname>/ohai` into `/etc/chef/ohai/cookbook-plugins/<cookbookname>` as their top level directory (recursively). The state of the entire subdirectory tree under `/etc/chef/ohai/cookbook-plugins` will be managed fully by chef-client so that any files which are not synchronized by chef-client will be removed, so that removal of a plugin from a cookbook or removal of the cookbook from `run_list` will result in the plugin being removed on the target host. The plugins directory will work similarly to libraries and other directions, in that there will be no control over the inclusion of plugins below the level of the inclusion of the cookbook itself in the `run_list`. When plugins override other plugins on loading, and in particular when cookbook plugins override core plugins, they should WARN the user. This will address the case where a user has included a custom plugin and Ohai is later extended with similar functionality in the same namespace. The custom plugin should take precedence for backwards compatibility. There should be a way to silence the warning with a DSL method added to the custom plugin.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: beam-2.41.0.md

title: "Apache Beam 2.41.0" date: 2022-08-23 9:00:00 -0700 categories: blog release authors: kileysok <!-- 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. --> We are happy to present the new 2.41.0 release of Beam. This release includes both improvements and new functionality. See the for this release. <!--more--> For more information on changes in 2.41.0, check out the . Projection Pushdown optimizer is now on by default for streaming, matching the behavior of batch pipelines since 2.38.0. If you encounter a bug with the optimizer, please file an issue and disable the optimizer using pipeline option `--experiments=disableprojectionpushdown`. Previously available in Java sdk, Python sdk now also supports logging level overrides per module. (). Projection Pushdown optimizer may break Dataflow upgrade compatibility for optimized pipelines when it removes unused fields. If you need to upgrade and encounter a compatibility issue, disable the optimizer using pipeline option `--experiments=disableprojectionpushdown`. Support for Spark 2.4.x is deprecated and will be dropped with the release of Beam 2.44.0 or soon after (Spark runner) (). The modules and for AWS Java SDK v1 are deprecated in favor of and will be eventually removed after a few Beam releases (Java) (). Fixed a condition where retrying queries would yield an incorrect cursor in the Java SDK Firestore Connector (). Fixed plumbing allowed lateness in Go SDK. It was ignoring the user set value earlier and always used to set to 0. (). See a full list of open this version. According to git shortlog, the following people contributed to the 2.41.0 release. Thank you to all contributors! Ahmed Abualsaud Ahmet Altay akashorabek Alexey Inkin Alexey Romanenko Anand Inguva andoni-guzman Andrew Pilloud Andrey Andy Ye Balzs Nmeth Benjamin Gonzalez BjornPrime Brian Hulette bulat safiullin bullet03 Byron Ellis Chamikara Jayalath Damon Douglas Daniel Oliveira Daniel Thevessen Danny McCormick David Huntsperger Dheeraj Gharde Etienne Chauchot Evan Galpin Fernando Morales Heejong Lee Jack McCluskey johnjcasey Kenneth Knowles Ke Wu Kiley Sok Liam Miller-Cushon Lucas Nogueira Luke Cwik MakarkinSAkvelon Manu Zhang Minbo Bae Moritz Mack Naireen Hussain Ning Kang Oleh Borysevych Pablo Estrada pablo rodriguez defino Pranav Bhandari Rebecca Szper Red Daly Reuven Lax Ritesh Ghorse Robert Bradshaw Robert Burke Ryan Thompson Sam Whittle Steven Niemitz Valentyn Tymofieiev Vincent Marquez Vitaly Terentyev Vlad Vladislav Chunikhin Yichi Zhang Yi Hu yirutang Yixiao Shen Yu Feng
Project: ArangoDB (App Definition and Development / Database)
File: set_has_value.md

+++ title = "`static void sethas_value(Impl &&, bool) noexcept`" description = "Sets whether the implementation has a value. Constexpr, never throws." categories = ["modifiers"] weight = 300 +++ Sets whether the implementation has a value by setting or clearing the relevant bit in the flags. Constexpr where possible. Requires: Always available. Complexity: Constant time. Guarantees: Never throws an exception.
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: read-only.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: read-only spec: components: name: busybox type: worker properties: image: busybox cmd: sleep '1000000' policies: type: read-only name: read-only properties: rules: selector: resourceTypes: ["Deployment"] ```
Project: KICS (Provisioning / Security & Compliance)
File: 9b18fc19-7fb8-49b1-8452-9c757c70f926.md

title: ElastiCache Nodes Not Created Across Multi AZ hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9b18fc19-7fb8-49b1-8452-9c757c70f926 Query name: ElastiCache Nodes Not Created Across Multi AZ Platform: Pulumi Severity: <span style="color:#ff7213">Medium</span> Category: Availability URL: ElastiCache Nodes should be created across multi az, which means 'AZMode' should be set to 'cross-az' in multi nodes cluster<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10 18" name: aws-eks runtime: yaml description: An EKS cluster resources: example: type: aws:elasticache:Cluster properties: engine: memcached numCacheNodes: 2 azMode: single-az name: aws-eks runtime: yaml description: An EKS cluster resources: example: type: aws:elasticache:Cluster properties: engine: memcached numCacheNodes: 2 ``` ```yaml title="Negative test num. 1 - yaml file" name: aws-eks runtime: yaml description: An EKS cluster resources: example: type: aws:elasticache:Cluster properties: engine: memcached numCacheNodes: 2 azMode: cross-az name: aws-eks runtime: yaml description: An EKS cluster resources: example: type: aws:elasticache:Cluster properties: engine: memcached numCacheNodes: 1 ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.72.md

layout: release date: 2021-11-14 tag: v0.5.72 Fixed database error on reading performance test @Revolyssup (#4625) [Chore] adding go1.16.4 make command @leecalcote (#4583) [mesheryctl] `perf apply` add support for overriding values set in the test configuration file with flags @navendu-pottekkat (#4590) Fix running tests with saved profile `mesheryctl perf apply [profile-name]` @piyushsingariya (#4547) [Security] Fix CVE 2020 28469 @s1ntaxe770r (#4588) [Security] Fix CVE-2021-29060 @s1ntaxe770r (#4587) [SECURTIY] fix GHSA-r628-mhmh-qjhw @s1ntaxe770r (#4591) [UI] mapped event_type null to success notification @manav1403 (#4599) fix CVE-2021-23440 @s1ntaxe770r (#4585) [Dashboard] Fix DB mutex from concurrent read/write and refactoring gql subs @bariqhibat (#4439) [Docs] Add 'Connecting to Remote Providers' section in Troubleshooting Guide @gyohuangxin (#4623) [Chore] Updating security report mailing list @leecalcote (#4600) [docs] note on using meshkit logger and an elaborate example @DelusionalOptimist (#4594) [doc] fix routing for command-reference redirects @Et-008 (#4593) [mesheryctl] `perf apply` add support for overriding values set in the test configuration file with flags @navendu-pottekkat (#4590) [Security] Fix "Zip Slip" vulnerability with meshery's remote provider @s1ntaxe770r (#4601) [Security] Fix CVE 2020 28469 @s1ntaxe770r (#4588) [Security] Fix CVE-2021-29060 @s1ntaxe770r (#4587) [SECURTIY] fix GHSA-r628-mhmh-qjhw @s1ntaxe770r (#4591) [Chore] Updating security report mailing list @leecalcote (#4600) fix CVE-2021-23440 @s1ntaxe770r (#4585) Thank you to our contributors for making this release possible: @DelusionalOptimist, @Et-008, @Revolyssup, @bariqhibat, @gyohuangxin, @leecalcote, @manav1403, @navendu-pottekkat, @piyushsingariya, @s1ntaxe770r, @sudo-NithishKarthik, @utkarsh-pro and @warunicorn19
Project: Meshery (Provisioning / Automation & Configuration)
File: pgo.md

layout: integration title: PGO (CrunchyData) subtitle: Collaborative and visual infrastructure as code for PGO (CrunchyData) image: /assets/img/integrations/pgo/icons/color/pgo-color.svg permalink: extensibility/integrations/pgo docURL: https://docs.meshery.io/extensibility/integrations/pgo description: integrations-category: Database integrations-subcategory: App Definition and Development registrant: Artifact Hub components: name: pg-upgrade colorIcon: assets/img/integrations/pgo/components/pg-upgrade/icons/color/pg-upgrade-color.svg whiteIcon: assets/img/integrations/pgo/components/pg-upgrade/icons/white/pg-upgrade-white.svg description: name: postgres-cluster colorIcon: assets/img/integrations/pgo/components/postgres-cluster/icons/color/postgres-cluster-color.svg whiteIcon: assets/img/integrations/pgo/components/postgres-cluster/icons/white/postgres-cluster-white.svg description: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: kpt (Provisioning / Automation & Configuration)
File: releasing.md

The current release process for Rollouts is manual and subject to change. Here are the steps. First, go to the to view existing rollouts controller images. Note the previous released version so that you can decide what the next release version should be. For example, if the previous released version is `v0.0.2`, you will most likely want to do `v0.0.3` next. Set the next release version: ```sh export VERSION=<version> ``` Build the docker image: ```sh IMG=gcr.io/kpt-dev/rollouts-controller:$VERSION make docker-build ``` Make sure you are connected to the kpt-dev project, and then push the image: ```sh gcloud config set project kpt-dev IMG=gcr.io/kpt-dev/rollouts-controller:$VERSION make docker-push ``` Run the `create-manifests` script to update the manifests: ```sh ./scripts/create-manifests.sh --controller-image gcr.io/kpt-dev/rollouts-controller:$VERSION ``` Create a pull request with the generated changes. Users can now use `kpt pkg get` to pull the new Rollout manifests with the updated image.
Project: Harbor (Provisioning / Container Registry)
File: 3-03-DB-user-search-project-members.md

Test 3-03 - Search Project Members (DB Mode) ======= To verify that a non system admin user can search members of a project when users are managed locally by Harbor (DB mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database. ( auth_mode is set to db_auth* .) The user data is stored in a local database. A linux host with Docker CLI installed (Docker client). At least five(5) non-admin users are in Harbor. NOTE: In below test, user A, B are non system admin users. User A, B and project X should be replaced by longer and meaningful names. MUST use two kinds of browsers at the same time to ensure independent sessions. For example, use Chrome and Firefox, or Chrome and Safari. DO NOT use the same browser to log in two users at the same time in different windows(tabs). Log in to UI as user A (non-admin). Create a new project X. Add user B as a project admin role of project X. Add 3 more members to project X with various roles, such as developer, guest. Keeps user A's UI session logging on, in a different browser log in as user B. In user B's UI, search members of project X using different criteria (keywords). In user A's UI, change user B's role to developer of project X. In user B's UI, search members of project X using different criteria. In user A's UI, change user B's role to guest of project X. In user B's UI, search members of project X using different criteria. Step 6,8,10, user B should see results based on search keywords. None
Project: StarRocks (App Definition and Development / Database)
File: array_generate.md

displayed_sidebar: "English" Returns an array of distinct values within the range specified by `start` and `end`, with an increment of `step`. This function is supported from v3.1. ```Haskell ARRAY array_generate([start,] end [, step]) ``` `start`: optional, the start value. It must be a constant or a column that evaluates to TINYINT, SMALLINT, INT, BIGINT, or LARGEINT. The default value is 1. `end`: required, the end value. It must be a constant or a column that evaluates to TINYINT, SMALLINT, INT, BIGINT, or LARGEINT. `step`: optional, the increment. It must be a constant or a column that evaluates to TINYINT, SMALLINT, INT, BIGINT, or LARGEINT. When `start` is less than `end`, the default value is 1. When `start` is greater than `end`, the default value is -1. Returns an array whose elements have the same data type as the input parameters. If any input parameter is a column, you must specify the table to which the column belongs. If any input parameter is a column, you must specify other parameters. Default values are not supported. If any input parameter is NULL, NULL is returned. If `step` is 0, an empty array is returned. If `start` equals to `end`, the value is returned. ```Plain Text mysql> select array_generate(9); ++ | array_generate(9) | ++ | [1,2,3,4,5,6,7,8,9] | ++ select array_generate(9,12); +--+ | array_generate(9, 12) | +--+ | [9,10,11,12] | +--+ select array_generate(9,6); +-+ | array_generate(9, 6) | +-+ | [9,8,7,6] | +-+ select array_generate(9,6,-1); +--+ | array_generate(9, 6, -1) | +--+ | [9,8,7,6] | +--+ select array_generate(3,3); +-+ | array_generate(3, 3) | +-+ | [3] | +-+ ``` ```sql CREATE TABLE `array_generate` ( `c1` TINYINT, `c2` SMALLINT, `c3` INT ) ENGINE = OLAP DUPLICATE KEY(`c1`) DISTRIBUTED BY HASH(`c1`); INSERT INTO `array_generate` VALUES (1, 6, 3), (2, 9, 4); ``` ```Plain Text mysql> select arraygenerate(1,c2,2) from `arraygenerate`; +--+ | array_generate(1, c2, 2) | +--+ | [1,3,5] | | [1,3,5,7,9] | +--+ ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.143.md

layout: release date: 2023-09-20 tag: v0.6.143 Update messages and logs to designs from patterns @Chadha93 (#8800) handle nil checks @MUzairS15 (#8844) watchtower label is added @zakisk (#8789) run error util for mesheryctl error codes replacement @MUzairS15 (#8846) [chore] Make MeshSyncEvents GraphQL Subscription Configurable @theBeginner86 (#8841) [Servre] Graphql/directives @MUzairS15 (#8836) [UI] Add Validation and Error Boundaries @aabidsofi19 (#8833) Added Debug log for extension component @senali-d (#8845) fix pagination in meshmodel browser @sudhanshutech (#8838) converted class based dashboard component to functional component @EraKin575 (#8724) [bug] Fix failing API docs build @theBeginner86 (#8850) [bug] Fix failing API docs build @theBeginner86 (#8850) [Server] Added environments in Meshery @Yashsharma1911 (#8723) Thank you to our contributors for making this release possible: @Chadha93, @EraKin575, @MUzairS15, @Yashsharma1911, @aabidsofi19, @leecalcote, @senali-d, @sudhanshutech, @theBeginner86 and @zakisk
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_project_alert_policy_condition.md

+++ title = "googleprojectalertpolicycondition resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleprojectalertpolicycondition" identifier = "inspec/resources/gcp/googleprojectalertpolicycondition.md googleprojectalertpolicycondition resource" parent = "inspec/resources/gcp" +++ Use the `googleprojectalertpolicycondition` InSpec audit resource to test properties of a single GCP project alert policy condition. A `googleprojectalertpolicycondition` resource block declares the tests for a single GCP project alert policy condition by name and filter. describe googleprojectalertpolicycondition(name: 'projects/spaterson-project/alertPolicies/9271751234503117449', filter 'project=\"spaterson-project\"') do it { should exist } end The following examples show how to use this InSpec audit resource. describe googleprojectalertpolicycondition(name: 'projects/spaterson-project/alertPolicies/9271751234503117449', filter 'project=\"spaterson-project\"') do its('conditionthresholdvalue'){ should eq 0.001 } end describe googleprojectalertpolicycondition(name: 'projects/spaterson-project/alertPolicies/9271751234503117449', filter 'project=\"spaterson-project\"') do its('aggregationalignmentperiod'){ should eq '60s' } end `conditionthresholdvalue`, `aggregationalignmentperiod`, `aggregationperseriesaligner`, `aggregationcrossseriesreducer` Ensure the is enabled for the project.
Project: Sonobuoy (Provisioning / Security & Compliance)
File: sonobuoy_images.md

Manage images used in a plugin to facilitate running them in airgapped (or similar) environments. Supported plugins are: 'e2e' ``` sonobuoy images [flags] ``` ``` --context string Context in the kubeconfig to use. --dry-run If true, only print the image operations that would be performed. -h, --help help for images --kubeconfig Kubeconfig Path to explicit kubeconfig file. --kubernetes-version string Use default E2E image, but override the version. Default is 'auto', which will be set to your cluster's version if detected, erroring otherwise. 'ignore' will try version resolution but ignore errors. 'latest' will find the latest dev image/version upstream. -p, --plugin strings Describe which plugin's images to interact with (Valid plugins are 'e2e', 'systemd-logs'). (default [e2e,systemd-logs]) --plugin-env pluginenvvar Set env vars on plugins. Values can be given multiple times and are in the form plugin.env=value (default map[]) ``` ``` --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) ``` - Generate reports on your Kubernetes cluster by running plugins - Deletes all images downloaded to local docker client - Saves downloaded images from local docker client to a tar file - Inspect images - List images - Pulls images to local docker client for a specific plugin - Pushes images to docker registry for a specific plugin
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-error-conditions-unsupported-collation-error-class.md

layout: global title: UNSUPPORTED_COLLATION error class displayTitle: UNSUPPORTED_COLLATION error class license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You 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. <!-- DO NOT EDIT THIS FILE. It was generated automatically by `org.apache.spark.SparkThrowableSuite`. --> Collation `<collationName>` is not supported for: This error class has the following derived error classes: function `<functionName>`. Please try to use a different collation.