cwielenb/CNCF-Dataset huggingface dataset:
Project: Beam (App Definition and Development / Streaming & Messaging)
File: beam-2.37.0.md

title: "Apache Beam 2.37.0" date: 2022-03-04 08:30:00 -0800 categories: blog release authors: bhulette <!-- 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.37.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.37.0 check out the . Java 17 support for Dataflow (). Users using Dataflow Runner V2 may see issues with state cache due to inaccurate object sizes (). ZetaSql is currently unsupported (). Python 3.9 support in Apache Beam (). Dataflow support for Python 3.9 is expected to be available with 2.37.0, but may not be fully available yet when the release is announced (). Users of Dataflow Runner V2 can run Python 3.9 pipelines with 2.37.0 release right away. Go SDK now has wrappers for the following Cross Language Transforms from Java, along with automatic expansion service startup for each. JDBCIO (). Debezium (). BeamSQL (). BiqQuery (). KafkaIO now also has automatic expansion service startup. (). DataFrame API now supports pandas 1.4.x (). Go SDK DoFns can now observe trigger panes directly (). See a full list of open this version. According to git shortlog, the following people contributed to the 2.37.0 release. Thank you to all contributors! Aizhamal Nurmamat kyzy Alexander Alexander Chermenin Alexandr Zhuravlev Alexey Romanenko Anand Inguva andoni-guzman andreukus Andy Ye Artur Khanin Aydar Farrakhov Aydar Zainutdinov AydarZaynutdinov Benjamin Gonzalez Brian Hulette Chamikara Jayalath Daniel Oliveira Danny McCormick daria-malkova daria.malkova darshan-sj David Huntsperger dprieto91 emily Etienne Chauchot Fernando Morales Heejong Lee Ismal Meja Jack McCluskey Jan Lukavsk johnjcasey Kamil Bregua kellen Kenneth Knowles kileys Kyle Weaver Luke Cwik Marcin Kuthan Marco Robles Matt Rudary Miguel Hernandez Milena Bukal Moritz Mack Mostafa Aghajani Ning Kang Pablo Estrada Pavel Avilov Reuven Lax Ritesh Ghorse Robert Bradshaw Robert Burke Sam Whittle Sandy Chapman Sergey Kalinin Thiago Nunes thorbjorn444 Tim Robertson Tomo Suzuki Valentyn Tymofieiev Victor Victor Chen Vitaly Ivanov Yichi Zhang
Project: Meshery (Provisioning / Automation & Configuration)
File: coredns.md

layout: integration title: Coredns subtitle: Collaborative and visual infrastructure as code for Coredns image: /assets/img/integrations/coredns/icons/color/coredns-color.svg permalink: extensibility/integrations/coredns docURL: https://docs.meshery.io/extensibility/integrations/coredns description: integrations-category: Orchestration & Management integrations-subcategory: Coordination & Service Discovery registrant: Artifact Hub components: featureList: [ "Serves zone data from a file; both DNSSEC (NSEC only) and DNS are supported (file and auto).", "Retrieves zone data from primaries, i.e., act as a secondary server (AXFR only) (secondary).", "Signs zone data on-the-fly (dnssec)." ] 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: Backstage (App Definition and Development / Application Definition & Image Build)
File: 04-built-in-data-refs.md

id: built-in-data-refs title: Built-in data refs sidebar_label: Built-in data refs description: Configuring or overriding built-in extension data references NOTE: The new frontend system is in alpha and is only supported by a small number of plugins. To have a better understanding of extension data references please read first. Data references help to define the inputs and outputs of an extension. A data ref is uniquely identified through its `id`. Through the data ref, strong typing is enforced for the input/output of the extension. | id | type | | :--: | :--: | | `core.reactElement` | `JSX.Element` | The `reactElement` data reference can be used for defining the extension input/output of React elements. Example usage could be something like this: ```tsx import { coreExtensionData, createExtensionInput, createPageExtension, } from '@backstage/frontend-plugin-api'; const homePage = createPageExtension({ defaultPath: '/home', routeRef: rootRouteRef, inputs: { props: createExtensionInput({ children: coreExtensionData.reactElement.optional(), }), }, }); ``` | id | type | | :--: | :: | | `core.routing.path` | `string` | The `routePath` data reference can be used for defining the extension input/output of string paths. | id | type | | :-: | :--: | | `core.routing.ref` | `RouteRef` | The `routeRef` data reference can be used for defining the extension input/output of route references. There are other data refs in the frontend system you might stumble upon while building your plugin. Most of them were created for use cases inside the core of the system, but they can be used also in your plugin.
Project: Paralus (Provisioning / Security & Compliance)
File: CODE_OF_CONDUCT.md

This is Code of Conduct is based on the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md). See the referred document for translated versions into different languages. As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities. We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality. Examples of unacceptable behavior by participants include: The use of sexualized language or imagery Personal attacks Trolling or insulting/derogatory comments Public or private harassment Publishing others' private information, such as physical or electronic addresses, without explicit permission Other unethical or unprofessional conduct. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, issues, and other contributions that are not aligned to this Code of Conduct. By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project. Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team. This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to . This Code of Conduct is adapted from the .
Project: ClickHouse (App Definition and Development / Database)
File: v21.7.9.7-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Allow symlinks for library dictionaty path. (). Backported in : Use Multipart copy upload for large S3 objects. (). Backported in : Bugfix for windowFunnel's "strict" mode. This fixes . (). Backported in : Fix column filtering with union distinct in subquery. Closes . (). Backported in : Prevent crashes for some formats when NULL (tombstone) message was coming from Kafka. Closes . (). Backported in : Fix a rare bug in `DROP PART` which can lead to the error `Unexpected merged part intersects drop range`. (). Backported in : Fix selecting with extremes from a column of the type `LowCardinality(UUID)`. (). Backported in : Check cluster name before creating Distributed table, do not allow to create a table with incorrect cluster name. Fixes . (). Backported in : Fix cases, when read buffer fails with 'attempt to read after end of file'. Closes . (). Backported in : Temporarily switched ubuntu apt repository to mirror ru.archive.ubuntu.com as default one(archive.ubuntu.com) is not responding from our CI. (). Backported in : Fix extremely rare segfaults on shutdown due to incorrect order of context/config reloader shutdown. (). Backported in : Fixed possible excessive number of conditions moved from `WHERE` to `PREWHERE` (optimization controlled by settings `optimizemoveto_prewhere`). (). Backported in : Fix incorrect behavior in `clickhouse-keeper` when list watches (`getChildren`) triggered with `set` requests for children. (). Backported in : Fix possible read of uninitialized memory for queries with `Nullable(LowCardinality)` type and extremes. Fixes . (). Backported in : Fix reading of custom TLD w/o new line at EOF. (). Backported in : Fix inconsistent result in queries with `ORDER BY` and `Merge` tables with enabled setting `optimizereadin_order`. (). Fix prometheus metric name (). Fix flacky test (). Fix throw without exception in MySQL source. (). Fix race between REPLACE PARTITION and MOVE PARTITION (). Follow-up to (). Set version of tzlocal to 2.1 (). ODBC connection holder fix dangling reference (). Another try to fix BackgroundPoolTask decrement. (). More accurate check that zk root exists. ().
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk_create_api.md

title: "operator-sdk create api" Scaffold a Kubernetes API Scaffold a Kubernetes API by writing a Resource definition and/or a Controller. If information about whether the resource and controller should be scaffolded was not explicitly provided, it will prompt the user if they should be. After the scaffold is written, the dependencies will be updated and make generate will be run. ``` operator-sdk create api [flags] ``` ``` operator-sdk create api --group ship --version v1beta1 --kind Frigate nano api/v1beta1/frigate_types.go nano internal/controller/frigate/frigate_controller.go nano internal/controller/frigate/frigatecontrollertest.go make manifests make install make run ``` ``` --controller if set, generate the controller without prompting the user (default true) --force attempt to create resource even if it already exists --group string resource Group -h, --help help for api --kind string resource Kind --make make generate if true, run make generate after generating files (default true) --namespaced resource is namespaced (default true) --plural string resource irregular plural form --resource if set, generate the resource without prompting the user (default true) --version string resource Version ``` ``` --plugins strings plugin keys to be used for this subcommand execution --verbose Enable verbose logging ``` - Scaffold a Kubernetes API or webhook
Project: KICS (Provisioning / Security & Compliance)
File: 48f100d9-f499-4c6d-b2b8-deafe47ffb26.md

title: S3 Bucket Allows Public ACL hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 48f100d9-f499-4c6d-b2b8-deafe47ffb26 Query name: S3 Bucket Allows Public ACL Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: S3 bucket allows public ACL<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10 4 20" Resources: Bucket11: Type: AWS::S3::Bucket Properties: Resources: Bucket12: Type: AWS::S3::Bucket Properties: PublicAccessBlockConfiguration: BlockPublicPolicy : true IgnorePublicAcls : true RestrictPublicBuckets : true Resources: Bucket13: Type: AWS::S3::Bucket Properties: PublicAccessBlockConfiguration: BlockPublicAcls: false BlockPublicPolicy : true IgnorePublicAcls : true RestrictPublicBuckets : true ``` ```json title="Positive test num. 2 - json file" hl_lines="7" { "Resources": { "Bucket1": { "Type": "AWS::S3::Bucket", "Properties": { "PublicAccessBlockConfiguration": { "BlockPublicAcls": false, "BlockPublicPolicy": true, "IgnorePublicAcls": true, "RestrictPublicBuckets": true }, "AccessControl": "Private" } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: Bucket1: Type: AWS::S3::Bucket Properties: PublicAccessBlockConfiguration: BlockPublicAcls : true BlockPublicPolicy : true IgnorePublicAcls : true RestrictPublicBuckets : true ``` ```json title="Negative test num. 2 - json file" { "Resources": { "Bucket1": { "Type": "AWS::S3::Bucket", "Properties": { "PublicAccessBlockConfiguration": { "BlockPublicAcls": true, "BlockPublicPolicy": true, "IgnorePublicAcls": true, "RestrictPublicBuckets": true }, "AccessControl": "Private" } } } } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.43.md

layout: release date: 2021-08-07 tag: v0.5.43 fixed the chevron problem @warunicorn19 (#3794) [DashboardComponent] Changes settings button styling in notification bar @CipherGirl (#3801) made changes to the performance calender @warunicorn19 (#3808) Fix Data Fetch and Logic from the server causing problems with pattern deployment @Abhishek-kumar09 (#3809) Remove cypress test spec for dashboard button @sudo-NithishKarthik (#3803) [UI] [Connection wizard] Fix the meshery operator step connection status @sudo-NithishKarthik (#3806) Updated the Maintainers.md file @debjani1413 (#3802) Added custom context support in installer @devansh42 (#3498) [mesheryctl] Unit Tests for `system token` @Revolyssup (#3737) [UI] Meshery Navigator Menu Re-iteration @Abhishek-kumar09 (#3779) [GraphQL] Query Performance fetch all results based on Performance Profile ID @bariqhibat (#3783) Changed docker compose default location @metonymic-smokey (#3788) [mesheryctl] Delete older application command @piyushsingariya (#3786) [meshery] changes to installer script for missing utilities @hexxdump (#3789) Refactor connection wizard @sudo-NithishKarthik (#3790) Open API docs for application endpoint @sayantan1413 (#3643) Added a save icon in the save button @sayantan1413 (#3687) Added MeshSync Chip, Snackbar and Toolbar @Meghana-12 (#3698) [mesheryctl] Tests for `mesheryctl pattern` commands @piyushsingariya (#3714) [CI] use access token in release notes publisher @DelusionalOptimist (#3777) [Docs] Add notes to fix Ruby version problems in Meshery docs @alphaX86 (#3773) updated the contributing docs @warunicorn19 (#3757) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @CipherGirl, @DelusionalOptimist, @Meghana-12, @Revolyssup, @adithyaakrishna, @alphaX86, @bariqhibat, @debjani1413, @devansh42, @hexxdump, @leecalcote, @metonymic-smokey, @navendu-pottekkat, @piyushsingariya, @sayantan1413, @sudo-NithishKarthik, @warunicorn19 and l5io
Project: KICS (Provisioning / Security & Compliance)
File: ec62a32c-a297-41ca-a850-cab40b42094a.md

title: OSS Bucket Allows All Actions From All Principals hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ec62a32c-a297-41ca-a850-cab40b42094a Query name: OSS Bucket Allows All Actions From All Principals Platform: Terraform Severity: <span style="color:#ff0000">Critical</span> Category: Access Control URL: OSS Buckets should not allow all actions (wildcard) from all principals, as to prevent leaking private information to the entire internet or allow unauthorized data tampering/deletion. This means the 'Effect' must not be 'Allow' when the 'Action' is *, for all Principals.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="5" resource "alicloudossbucket" "bucket-policy1" { bucket = "bucket-1-policy" acl = "private" policy = <<POLICY {"Statement": [ { "Action": [ "oss:*" ], "Effect": "Allow", "Principal": [ "*" ], "Resource": [ "acs:oss:*:174649585760xxxx:examplebucket" ] } ], "Version":"1"} POLICY } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudossbucket" "bucket-policy1" { bucket = "bucket-1-policy" acl = "private" policy = <<POLICY {"Statement": [ { "Action": [ "oss:*" ], "Effect": "Deny", "Principal": [ "*" ], "Resource": [ "acs:oss:*:174649585760xxxx:examplebucket" ] } ], "Version":"1"} POLICY } ``` ```tf title="Negative test num. 2 - tf file" resource "alicloudossbucket" "bucket-policy1" { bucket = "bucket-1-policy" acl = "private" policy = <<POLICY {"Statement": [ { "Action": [ "oss:ListObjects" ], "Effect": "Allow", "Principal": [ "*" ], "Resource": [ "acs:oss:*:174649585760xxxx:examplebucket" ] } ], "Version":"1"} POLICY } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.172.md

layout: release date: 2023-11-06 tag: v0.6.172 [Server] K8s connection management @MUzairS15 (#9170) Meshmodel new UI @ptdatta (#9184) Bump billboard.js from 3.9.0 to 3.10.2 in /ui @dependabot (#9269) Bump eslint-config-next from 13.5.3 to 14.0.1 in /provider-ui @dependabot (#9277) Bump cypress from 13.3.0 to 13.4.0 in /provider-ui @dependabot (#9279) Add sidecar icon @ShatilKhan (#9291) [UI] Expose generic RJSF modal to meshery extension @Yashsharma1911 (#9304) Bump billboard.js from 3.9.0 to 3.10.2 in /ui @dependabot (#9269) Bump fortio.org/fortio from 1.57.5 to 1.60.3 @dependabot (#9272) Bump eslint-config-next from 13.5.3 to 14.0.1 in /provider-ui @dependabot (#9277) Bump cypress from 13.3.0 to 13.4.0 in /provider-ui @dependabot (#9279) added some svgs in docs @iArchitSharma (#9312) [Docs] Exclude old versions from rendering in local builds @leecalcote (#9310) Added description of Docs capability for "alerts" @Debaditya-Som (#9226) [docs] Add docs for notification center @aabidsofi19 (#9303) Thank you to our contributors for making this release possible: @Aisuko, @Debaditya-Som, @MUzairS15, @ShatilKhan, @Yashsharma1911, @aabidsofi19, @dependabot, @dependabot[bot], @iArchitSharma, @l5io, @leecalcote, @ptdatta, @theBeginner86 and l5io
Project: KubeMQ (App Definition and Development / Streaming & Messaging)
File: kubemq_events_store_send.md

Events-Store send messages to an 'events store' channel command Events-Store send command allows to send (publish) one or many messages to an 'events store' channel ``` kubemq events_store send [flags] ``` ``` kubemq events_store send some-channel some-body kubemq events_store send some-channel some-body --metadata some-metadata kubemq events_store send some-channel some-body -m 10 kubemq events_store send some-channel some-body -m 100 -s ``` ``` -h, --help help for send -m, --messages int set how many 'events store' messages to send (default 1) --metadata string set body metadata field ``` - Execute Kubemq 'Events-Store' Pub/Sub commands
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: policy.md

Our general policy is that you should upgrade to the latest version of each minor version before you upgrade to the latest version. You should check all upgrade requirements and deprecation notices for all versions as you upgrade. An example of this policy is as follows Currently installed v2.13.0, planning to upgrade to v2.16.0 Upgrade to v2.14.2 (the latest 2.14.x release) Upgrade to v2.15.4 (the latest 2.15.x release) Upgrade to v2.16.0 We may, from time to time, provide additional context to the upgrades listed in these pages. As Lagoon continues to evolve, we occasionally need to replace, rename or retire existing processes, tools or configuration. Where this may impact a user's processes or procedures, we intend to outline a timeframe to allow any necessary changes to be made. Deprecations will be tracked by the release they are announced in, and then updated when the actual deprecation occurs. All deprecations should provide a rough timeline (in months or releases). We may, from time to time, provide additional context to the deprecations listed in these pages.
Project: ClickHouse (App Definition and Development / Database)
File: v21.5.8.21-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : `CAST` from `Date` to `DateTime` (or `DateTime64`) was not using the timezone of the `DateTime` type. It can also affect the comparison between `Date` and `DateTime`. Inference of the common type for `Date` and `DateTime` also was not using the corresponding timezone. It affected the results of function `if` and array construction. Closes . (). Backported in : Fixed bug in deserialization of random generator state with might cause some data types such as `AggregateFunction(groupArraySample(N), T))` to behave in a non-deterministic way. (). Backported in : Fix potential crash when calculating aggregate function states by aggregation of aggregate function states of other aggregate functions (not a practical use case). See . (). Backported in : Fix assertion in PREWHERE with non-uint8 type, close . (). Backported in : Fix wrong totals for query `WITH TOTALS` and `WITH FILL`. Fixes . (). Backported in : Fix null pointer dereference in `EXPLAIN AST` without query. (). Backported in : `REPLACE PARTITION` might be ignored in rare cases if the source partition was empty. It's fixed. Fixes . (). Backported in : Fixed `No such file or directory` error on moving `Distributed` table between databases. Fixes . (). Backported in : Fix data race when querying `system.clusters` while reloading the cluster configuration at the same time. (). Backport unrelated changes, which fixes aliases bug (). ExpressionCache destruction fix ().