cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.3.3.4.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Hadoop - Upgrade to JQuery 3.6.0 | Major | . | Yuan Luo | Yuan Luo | | | Document how to configure NUMA in YARN | Major | documentation | Prabhu Joseph | Samrat Deb | | | Remove rs-api dependency by downgrading jackson to 2.12.7 | Major | build | PJ Fanning | PJ Fanning | | | Upgrade reload4j to 1.2.22 due to XXE vulnerability | Major | . | PJ Fanning | PJ Fanning | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | S3 SDK Upgrade causes AccessPoint ARN endpoint mistranslation | Major | fs/s3, test | Bogdan Stolojan | Bogdan Stolojan | | | Upgrade jquery ui to 1.13.1 | Major | . | D M Murali Krishna Reddy | groot | | | Upgrade okhttp from 2.7.5 to 4.9.3 | Major | hdfs-client | Ivan Viaznikov | groot | | | CS UI: queue filter and openQueues param do not work as expected | Major | capacity scheduler | Chengbing Liu | Chengbing Liu | | | Upgrade Apache Xerces Java to 2.12.2 | Major | build | groot | groot | | | Partial/Incomplete groups list can be returned in LDAP groups lookup | Major | security | Philippe Lanoe | Larry McCay | | | Upgrade Netty to 4.1.77.Final | Major | build | Renukaprasad C | Wei-Chiu Chuang | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Upgrade AWS SDK to 1.12.132 | Major | build, fs/s3 | Steve Loughran | Steve Loughran | | | remove hadoop-cos as a dependency of hadoop-cloud-storage | Major | bulid, fs | Steve Loughran | Steve Loughran | | | AWS SDK update to 1.12.262 to address jackson CVE-2018-7489 | Major | fs/s3 | Steve Loughran | Steve Loughran |
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: root-lifecycle.md

id: root-lifecycle title: Root Lifecycle Service sidebar_label: Root Lifecycle description: Documentation for the Root Lifecycle service This service is the same as the lifecycle service, but should only be used by the root services. This is also where the implementation for the actual lifecycle hooks are collected and executed, so if you want to override the implementation of how those are processed, you should override this service. The following example shows how to override the default implementation of the lifecycle service with something that listens on different process events to the original. ```ts class MyCustomLifecycleService implements RootLifecycleService { constructor(private readonly logger: LoggerService) {} hook: LifecycleServiceShutdownHook; options?: LifecycleServiceShutdownOptions; }> = []; addShutdownHook( hook: LifecycleServiceShutdownHook, options?: LifecycleServiceShutdownOptions, ): void { this.#shutdownTasks.push({ hook, options }); } async shutdown(): Promise<void> { if (this.#isCalled) { return; } this.#isCalled = true; this.logger.info(`Running ${this.#shutdownTasks.length} shutdown tasks...`); await Promise.all( this.#shutdownTasks.map(async ({ hook, options }) => { const logger = options?.logger ?? this.logger; try { await hook(); logger.info(`Shutdown hook succeeded`); } catch (error) { logger.error(`Shutdown hook failed, ${error}`); } }), ); } } const backend = createBackend(); backend.add( createServiceFactory({ service: coreServices.rootLifecycle, deps: { logger: coreServices.rootLogger, }, async factory({ logger }) { return new MyCustomLifecycleService(logger); }, }), ); ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.4.16.md

layout: release date: 2020-10-28 tag: v0.4.16 General Minor correction of words in the kinD quick start page @alonsolopezr (#1759) fix: remove the duplicate function required for version checking @kushthedude (#1767) Getting the gke quick start page, translation to es in the docs-pages @alonsolopezr (#1757) [Docs] Translate Project page to Spanish @homero304 (#1740) [mesheryctl] Add prerequisite on docker daemon running status @hexxdump (#1746) Add latest available version in the API and in the dashboard @utkarsh-pro (#1761) enh: populate loadGenerator in SMP results @kushthedude (#1765) [ImgBot] Optimize images @IMGBOT (#1764) [Docs] Section update @chandrashritii (#1726) [Docs] fixes #1748 SVG of Meshery Architecture Diagram @DanRowe1 (#1760) Updated WSL link Signed-off-by: Bart Kalanski bkalanski@gmail.com @bartkalanski (#1755) Getting the docker quick start page, translation to es in the docs-pa @alonsolopezr (#1744) Getting the aks quick start page, translation to es in the docs/pages @alonsolopezr (#1741) Getting the eks quick start page, translation to es in the docs-pages @alonsolopezr (#1743) [UI] update nginx-sm logo @leecalcote (#1750) fixes for remote provider @kumarabd (#1739) [Docs] README - Add NGINX Service Mesh adapter @UnkleTayo (#1736) reorder menu items in alphabetical order - i1735 @amanda-ariyaratne (#1737) generate default mesheryctl config if one doesn't exist or invalid on @anirudhjain75 (#1693) [Fix - #1728] - Replacing the Traefik logo to minimal-version @akashprasher (#1733) chore: upgrade nighthawk-go package version @kushthedude (#1732)
Project: ShardingSphere (App Definition and Development / Database)
File: transaction.en.md

+++ title = "Distributed Transaction" weight = 4 +++ ShardingSphere provides three modes for distributed transactions `LOCAL`, `XA`, `BASE`. ```yaml transaction: defaultType: # Transaction mode, optional value LOCAL/XA/BASE providerType: # Specific implementation of the mode ``` The content of the global.yaml configuration file is as follows: ```yaml transaction: defaultType: LOCAL ``` The content of the global.yaml configuration file is as follows: ```yaml transaction: defaultType: XA providerType: Narayana/Atomikos ``` To manually add Narayana-related dependencies: ``` jta-5.12.7.Final.jar arjuna-5.12.7.Final.jar common-5.12.7.Final.jar jboss-connector-api1.7spec-1.0.0.Final.jar jboss-logging-3.2.1.Final.jar jboss-transaction-api1.2spec-1.0.0.Alpha3.jar jboss-transaction-spi-7.6.1.Final.jar narayana-jts-integration-5.12.7.Final.jar shardingsphere-transaction-xa-narayana-x.x.x-SNAPSHOT.jar ``` The content of the global.yaml configuration file is as follows: ```yaml transaction: defaultType: BASE providerType: Seata ``` Build a Seata Server, add relevant configuration files and Seata dependencies, see
Project: Meshery (Provisioning / Automation & Configuration)
File: kubedb-ops-manager.md

layout: integration title: Kubedb Ops Manager subtitle: Collaborative and visual infrastructure as code for Kubedb Ops Manager image: /assets/img/integrations/kubedb-ops-manager/icons/color/kubedb-ops-manager-color.svg permalink: extensibility/integrations/kubedb-ops-manager docURL: https://docs.meshery.io/extensibility/integrations/kubedb-ops-manager description: integrations-category: App Definition and Development integrations-subcategory: Database registrant: Artifact Hub components: featureList: [ "KubeDB simplifies many of the difficult or tedious management tasks of running a production grade databases on private and public clouds. Maintain one stack for all your stateless and stateful applications and simplify the operational complexity.", "Standard Kubernetes is all you need. If you can run Kubernetes, you can provision and manage databases using KubeDB. Use standard Kubernetes CLI and API to provision and manage databases.", "KubeDB uses Persistent Volume Claims (PVC) to dynamically provision disks for database instances. Using appropriately defined StorageClasses, KubeDB provisioned database instances are designed to scale from small development workloads up to performance-intensive workloads on private and public cloud environments." ] 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: Meshery (Provisioning / Automation & Configuration)
File: devstream.md

layout: integration title: Devstream subtitle: Collaborative and visual infrastructure as code for Devstream image: /assets/img/integrations/devstream/icons/color/devstream-color.svg permalink: extensibility/integrations/devstream docURL: https://docs.meshery.io/extensibility/integrations/devstream description: integrations-category: Provisioning integrations-subcategory: Automation & Configuration registrant: Artifact Hub components: featureList: [ "Centrally manage your toolchain with versioned code, and keep track of every change.", "No reinvention of the wheels. Simply create a plugin, and connect any tools you like with DevStream.", "Implement inbuilt best practices and share yours with the world." ] 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: Flink (App Definition and Development / Streaming & Messaging)
File: with.md

title: "WITH clause" weight: 3 type: docs <!-- 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. --> {{< label Batch >}} {{< label Streaming >}} `WITH` provides a way to write auxiliary statements for use in a larger query. These statements, which are often referred to as Common Table Expression (CTE), can be thought of as defining temporary views that exist just for one query. The syntax of `WITH` statement is: ```sql WITH <withitemdefinition> [ , ... ] SELECT ... FROM ...; <withitemdefintion>: withitemname (columnname[, ...n]) AS ( <selectquery> ) ``` The following example defines a common table expression `orderswithtotal` and use it in a `GROUP BY` query. ```sql WITH orderswithtotal AS ( SELECT order_id, price + tax AS total FROM Orders ) SELECT order_id, SUM(total) FROM orderswithtotal GROUP BY order_id; ``` {{< top >}}
Project: Apache Heron (App Definition and Development / Streaming & Messaging)
File: getting-started-docker.md

id: version-0.20.4-incubating-getting-started-docker title: The official Apache Heron Docker Image(s) sidebar_label: Heron & Docker original_id: getting-started-docker <!-- 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. --> The current version of Heron is {{heron:version}} The official Apache Heron Docker image is located at the link below <a target="_blank" href="https://hub.docker.com/repository/docker/apache/heron">https://hub.docker.com/repository/docker/apache/heron</a> In one terminal execute to start Heron in a container ```bash $ docker run -it --rm \ -p 8889:8889 \ -p 8888:8888 \ --name local-heron \ apache/heron:0.20.4-incubating supervisord --nodaemon ``` In another terminal execute the following to deploy a job: ```bash $ docker exec -it \ local-heron \ bash -c "heron submit sandbox /heron/examples/heron-eco-examples.jar org.apache.heron.eco.Eco --eco-config-file /heron/examples/heron_wordcount.yaml" ``` View your job details by navigating to `localhost:8889` in your browser. Congratulations, you've just deployed a Heron job in Docker!
Project: Trivy (Provisioning / Security & Compliance)
File: bitnami.md

!!! warning "EXPERIMENTAL" Scanning results may be inaccurate. While it is not an OS, this page describes the details of the . Bitnami images are based on . Please see for OS packages. Trivy supports the following scanners for Bitnami packages. | Scanner | Supported | | :--: | :-: | | SBOM | | | Vulnerability | | | License | | The table below outlines the features offered by Trivy. | Feature | Supported | | :-: | :-: | | Unfixed vulnerabilities | - | | | - | Trivy analyzes the SBOM information contained within the container images provided by Bitnami. The SBOM files are located at `/opt/bitnami/<component>/.spdx-<component>.spdx`. Since Bitnami has its , it uses these for vulnerability detection of applications and packages distributed by Bitnami. !!! note Trivy does not support vulnerability detection of independently compiled binaries, so even if you scan container images like `nginx:1.15.2`, vulnerabilities in Nginx cannot be detected. This is because main applications like Nginx are . However, in the case of Bitnami images, since these SBOMs are stored within the image, scanning `bitnami/nginx:1.15.2` allows for the detection of vulnerabilities in Nginx. Trivy refers to the . Please note that these may differ from the upstream fixed versions. Similar to Fixed versions, it follows Bitnami's vulnerability database. Trivy supports the following [vulnerability statuses] for Bitnami packages. | Status | Supported | | :--: | :-: | | Fixed | | | Affected | | | Under Investigation | | | Will Not Fix | | | Fix Deferred | | | End of Life | | If licenses are included in the SBOM distributed by Bitnami, they will be used for scanning.
Project: YugabyteDB (App Definition and Development / Database)
File: select,common_table_expression,fn_over_window,ordinary_aggregate_fn_invocation,within_group_aggregate_fn_invocation,grouping_element,order_expr.grammar.md

```output.ebnf select ::= [ WITH [ RECURSIVE ] { commontableexpression [ , ... ] } ] SELECT [ ALL | DISTINCT [ ON { ( expression [ , ... ] ) } ] ] [ * | { { expression | fnoverwindow | ordinaryaggregatefn_invocation | withingroupaggregatefninvocation } [ [ AS ] name ] } [ , ... ] ] [ FROM { from_item [ , ... ] } ] [ WHERE boolean_expression ] [ GROUP BY { grouping_element [ , ... ] } ] [ HAVING boolean_expression ] [ WINDOW { { name AS window_definition } [ , ... ] } ] [ { UNION | INTERSECT | EXCEPT } [ ALL | DISTINCT ] select ] [ ORDER BY { order_expr [ , ... ] } ] [ LIMIT { integer | ALL } ] [ OFFSET integer [ ROW | ROWS ] ] [ FETCH { FIRST | NEXT } integer { ROW | ROWS } ONLY ] [ FOR { UPDATE | NO KEY UPDATE | SHARE | KEY SHARE } [ OF table_name [ , ... ] ] [ NOWAIT | SKIP LOCKED ] [ ... ] ] commontableexpression ::= name [ ( name [ , ... ] ) ] AS ( { select | values | insert | update | delete } ) fnoverwindow ::= name ( [ expression [ , ... ] | * ] [ FILTER ( WHERE boolean_expression ) ] OVER { window_definition | name } ordinaryaggregatefn_invocation ::= name ( { [ ALL | DISTINCT ] expression [ , ... ] | * } [ ORDER BY order_expr [ , ... ] ] ) [ FILTER ( WHERE boolean_expression ) ] withingroupaggregatefninvocation ::= name ( { expression [ , ... ] } ) WITHIN GROUP ( ORDER BY order_expr [ , ... ] ) [ FILTER ( WHERE boolean_expression ) ] grouping_element ::= ( ) | ( expression [ , ... ] ) | ROLLUP ( expression [ , ... ] ) | CUBE ( expression [ , ... ] ) | GROUPING SETS ( grouping_element [ , ... ] ) orderexpr ::= expression [ ASC | DESC | USING operatorname ] [ NULLS { FIRST | LAST } ] ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: kernel_parameters.md

+++ title = "kernel_parameters resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "kernel_parameters" identifier = "inspec/resources/os/kernelparameters.md kernelparameters resource" parent = "inspec/resources/os" +++ Use the `kernel_parameters` Chef InSpec audit resource to test multiple kernel parameters on Linux platforms. These parameters are located under `/proc/cmdline`. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} A `kernel_parameters` resource block uses `where` to filter entries from the systems kernel parameters. If `where` is omitted, all entries are selected. describe kernel_parameters do its('parameters') { should include "PARAMETER_NAME" } its('values') { should include 1 } end describe kernelparameters.where(parameter: "PARAMETERNAME") do its('values') { should eq [1] } end The kernel parameter to test. The value of a kernel parameter. The following examples show how to use this Chef InSpec audit resource. describe kernel_parameters.where(parameter: "net.ipv4.conf.all.forwarding") do its('values') { should eq [1] } end describe kernel_parameters.where(parameter: /^net./ ) do its('parameters') { should include 'net.ipv4.conf.all.forwarding' } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: CDK for Kubernetes (CDK8s) (Provisioning / Automation & Configuration)
File: media.md

<table> <thead> <tr> <th colspan="3"></th> </tr> <tr> <th></th> <th colspan="1">PNG</th> <th colspan="1">SVG</th> </tr> </thead> <tbody> <tr> <th>color</th> <td><img src="/assets/logos/horizontal/cdk8s.horizontal.color.png" width="150px"></td> <td><img src="/assets/logos/horizontal/cdk8s.horizontal.color.svg" width="150px"></td> </tr> <tr> <th>black</th> <td><img src="/assets/logos/horizontal/cdk8s.horizontal.black.png" width="150px"></td> <td><img src="/assets/logos/horizontal/cdk8s.horizontal.black.svg" width="150px"></td> </tr> <tr style="background-color: black; color: white;"> <th>white</th> <td><img src="/assets/logos/horizontal/cdk8s.horizontal.white.png" width="150px"></td> <td><img src="/assets/logos/horizontal/cdk8s.horizontal.white.svg" width="150px"></td> </tr> </tbody> </table> <table> <thead> <tr> <th colspan="3"></th> </tr> <tr> <th></th> <th colspan="1">PNG</th> <th colspan="1">SVG</th> </tr> </thead> <tbody> <tr> <th>color</th> <td><img src="/assets/logos/stacked/cdk8s.stacked.color.png" width="150px"></td> <td><img src="/assets/logos/stacked/cdk8s.stacked.color.svg" width="150px"></td> </tr> <tr> <th>black</th> <td><img src="/assets/logos/stacked/cdk8s.stacked.black.png" width="150px"></td> <td><img src="/assets/logos/stacked/cdk8s.stacked.black.svg" width="150px"></td> </tr> <tr style="background-color: black; color: white;"> <th>white</th> <td><img src="/assets/logos/stacked/cdk8s.stacked.white.png" width="150px"></td> <td><img src="/assets/logos/stacked/cdk8s.stacked.white.svg" width="150px"></td> </tr> </tbody> </table> <table> <thead> <tr> <th colspan="3"></th> </tr> <tr> <th></th> <th colspan="1">PNG</th> <th colspan="1">SVG</th> </tr> </thead> <tbody> <tr> <th>color</th> <td><img src="/assets/logos/icon/cdk8s.icon.color.png" width="150px"></td> <td><img src="/assets/logos/icon/cdk8s.icon.color.svg" width="150px"></td> </tr> <tr> <th>black</th> <td><img src="/assets/logos/icon/cdk8s.icon.black.png" width="150px"></td> <td><img src="/assets/logos/icon/cdk8s.icon.black.svg" width="150px"></td> </tr> <tr style="background-color: black; color: white;"> <th>white</th> <td><img src="/assets/logos/icon/cdk8s.icon.white.png" width="150px"></td> <td><img src="/assets/logos/icon/cdk8s.icon.white.svg" width="150px"></td> </tr> </tbody> </table>
Project: SlimToolkit (Provisioning / Security & Compliance)
File: WISHLIST.md

If you want to help feel free to submit a PR! You can also open an issue to track the work and to have a place to talk about it. Docker image flattening OS specific cleanup commands (optional) Original issue: <https://github.com/docker-slim/docker-slim/issues/57> Original issue: <https://github.com/docker-slim/docker-slim/issues/67> Dockerizing local applications and creating minified images for them. Original issue: <https://github.com/docker-slim/docker-slim/issues/60> Original issues: <https://github.com/docker-slim/docker-slim/issues/91> <https://github.com/docker-slim/docker-slim/issues/99> Original issues: <https://github.com/docker-slim/docker-slim/issues/77>
Project: KICS (Provisioning / Security & Compliance)
File: f861041c-8c9f-4156-acfc-5e6e524f5884.md

title: S3 Bucket Logging Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: f861041c-8c9f-4156-acfc-5e6e524f5884 Query name: S3 Bucket Logging Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable<br> ```tf title="Positive test num. 1 - tf file" hl_lines="14" provider "aws" { region = "us-east-1" } terraform { required_providers { aws = { source = "hashicorp/aws" version = "~> 3.0" } } } resource "awss3bucket" "positive1" { bucket = "my-tf-test-bucket" acl = "private" tags = { Name = "My bucket" Environment = "Dev" } versioning { mfa_delete = true } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" versioning = { enabled = true } } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="14" terraform { required_providers { aws = { source = "hashicorp/aws" version = "4.2.0" } } } provider "aws" { } resource "awss3bucket" "examplee" { bucket = "my-tf-example-bucket" } ``` ```tf title="Negative test num. 1 - tf file" provider "aws" { region = "us-east-1" } terraform { required_providers { aws = { source = "hashicorp/aws" version = "~> 3.0" } } } resource "awss3bucket" "negative1" { bucket = "my-tf-test-bucket" acl = "private" tags = { Name = "My bucket" Environment = "Dev" } logging { target_bucket = "logs" } versioning { mfa_delete = true } } ``` ```tf title="Negative test num. 2 - tf file" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" versioning = { enabled = true } logging { target_bucket = "logs" } } ``` ```tf title="Negative test num. 3 - tf file" terraform { required_providers { aws = { source = "hashicorp/aws" version = "4.2.0" } } } provider "aws" { } resource "awss3bucket" "example" { bucket = "my-tf-example-bucket" } resource "awss3bucket_logging" "example" { bucket = awss3bucket.example.id targetbucket = awss3bucket.logbucket.id target_prefix = "log/" } ```
Project: VoltDB (App Definition and Development / Database)
File: CONTRIBUTING.md

Thank you for your interest in contributing. VoltDB uses GitHub to manage reviews of pull requests. We welcome your contributions to VoltDB or to any of the related libraries and tools. VoltDB uses the standard github workflow, meaning we make use of forking and pull requests. If you have a trivial fix or improvement, go ahead and create a pull request. If you are interested in contributing something more involved, feel free to discuss your ideas in on Slack. In order to contribute code to VoltDB, you must first sign the and email an image or PDF of the document including your hand-written signature to . VoltDB will sign and return the final copy of the agreement for your records. The workflow is essentially the following: Fork the VoltDB project Make a branch. Commit your changes to this branch. (See note below) Issue a pull request on the VoltDB repository. Once you have signed the CLA, a VoltDB engineer will review your pull request. Note: It will be easier to keep your work merge-able (conflict-free) if you don't work directly on your master branch in your VoltDB fork. Rather, keep your master branch in sync with the VoltDB repository and apply your changes on a branch of your fork. For further reading: on Github on Slack