cwielenb/CNCF-Dataset huggingface dataset:
Project: Pulsar (App Definition and Development / Streaming & Messaging)
File: pip-329.md

<!-- RULES Never place a link to an external site like Google Doc. The proposal should be in this issue entirely. Use a spelling and grammar checker tools if available for you (there are plenty of free ones). PROPOSAL HEALTH CHECK I can read the design document and understand the problem statement and what you plan to change without resorting to a couple of hours of code reading just to start having a high level understanding of the change. IMAGES If you need diagrams, avoid attaching large files. You can use ) as a simple language to describe many types of diagrams. THIS COMMENTS Please remove them when done. --> There is a gap in our current release process concerning the pushing of the latest tag to our Docker images. Specifically, we need to decide which version of Pulsar the latest tag should point to. We've had initial agreement from previous discussions, found here: https://lists.apache.org/thread/h4m90ff7dgx0110onctf5ntq0ktydzv1. Now, we need to formally propose a PIP to address this. Define the strategy for maintaining the latest tag to Pulsar docker images in the release process None Refine the release process to clearly demonstrate the strategy for managing the 'latest' tag for Pulsar Docker images: The 'latest' tag should be pointed to the most recent feature release or any subsequent patch of that feature release. For instance, if the most recent feature release is version 3.1, and it has been updated with patches, the ' latest' tag could point to version 3.1.2, assuming this is the latest patch for the 3.1 feature. Alternatively, if a new feature release, say 3.2.0, is introduced, the 'latest' tag would then point to this new version. In simpler terms, the `latest` tag will always point to the newest version of a feature. An alternative strategy is The latest tag could point to the most recent feature release or the subsequent patch of that feature release. For instance, it could currently point to 3.1.1, and in the future, it could point to 3.1.2 or 3.2.0. Feedback from the community indicates a preference for the solution proposed by this PIP. Discussion of `Strategy for pushing the latest tag to Pulsar docker images`: https://lists.apache.org/thread/h4m90ff7dgx0110onctf5ntq0ktydzv1 The implementation PR for this PIP: https://github.com/apache/pulsar-site/pull/745 Mailing List discussion thread: https://lists.apache.org/thread/x7r1f2vgmowykwdcb3mmrv0d8lj4y1t9 Mailing List voting thread: https://lists.apache.org/thread/f9j0xjjlyz54880zyzon3xm5y0zn37xb
Project: KICS (Provisioning / Security & Compliance)
File: c3831315-5ae6-4fa8-b458-3d4d5ab7a3f6.md

title: Certificate Has Expired hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c3831315-5ae6-4fa8-b458-3d4d5ab7a3f6 Query name: Certificate Has Expired Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Expired SSL/TLS certificates should be removed<br> ```tf title="Positive test num. 1 - tf file" hl_lines="2" resource "awsapigatewaydomainname" "example2" { certificate_body = file("expiredCertificate.pem") domain_name = "api.example.com" } ``` ```tf title="Negative test num. 1 - tf file" resource "awsapigatewaydomainname" "example" { certificate_body = file("validCertificate.pem") domain_name = "api.example.com" } ``` ```yaml title="Negative test num. 2 - yaml file" name: upload a self-signed certificate2 community.aws.aws_acm: certificate: "{{ lookup('file', 'validCertificate.pem' ) }}" privateKey: "{{ lookup('file', 'key.pem' ) }}" nametag: mycert region: ap-southeast-2 ```
Project: KICS (Provisioning / Security & Compliance)
File: 45cff7b6-3b80-40c1-ba7b-2cf480678bb8.md

title: Neptune Logging Is Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 45cff7b6-3b80-40c1-ba7b-2cf480678bb8 Query name: Neptune Logging Is Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Neptune logging should be enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsneptunecluster" "postive1" { cluster_identifier = "neptune-cluster" engine = "neptune" backupretentionperiod = 5 preferredbackupwindow = "10:10-11:11" skipfinalsnapshot = true iamdatabaseauthentication_enabled = true apply_immediately = true } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="9" resource "awsneptunecluster" "postive2" { cluster_identifier = "neptune-cluster" engine = "neptune" backupretentionperiod = 5 preferredbackupwindow = "10:10-11:11" skipfinalsnapshot = true iamdatabaseauthentication_enabled = true apply_immediately = true enablecloudwatchlogs_exports = [] } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="9" resource "awsneptunecluster" "postive3" { cluster_identifier = "neptune-cluster" engine = "neptune" backupretentionperiod = 5 preferredbackupwindow = "10:10-11:11" skipfinalsnapshot = true iamdatabaseauthentication_enabled = true apply_immediately = true enablecloudwatchlogs_exports = ["error"] } ``` ```tf title="Negative test num. 1 - tf file" resource "awsneptunecluster" "negative1" { cluster_identifier = "neptune-cluster" engine = "neptune" backupretentionperiod = 5 preferredbackupwindow = "10:10-11:11" skipfinalsnapshot = true iamdatabaseauthentication_enabled = true apply_immediately = true enablecloudwatchlogs_exports = ["audit"] } resource "awsneptunecluster" "negative2" { cluster_identifier = "neptune-cluster" engine = "neptune" backupretentionperiod = 5 preferredbackupwindow = "10:10-11:11" skipfinalsnapshot = true iamdatabaseauthentication_enabled = true apply_immediately = true enablecloudwatchlogs_exports = ["audit", "error"] } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.182.md

layout: release date: 2023-11-28 tag: v0.6.182 [CI] fix eslint issue failing lint check by @sudhanshutech in https://github.com/meshery/meshery/pull/9454 [dashboard] fix opacity for `view all` span by @sudhanshutech in https://github.com/meshery/meshery/pull/9455 [UI] Add hide/unhide support in search for mobile compatible by @sudhanshutech in https://github.com/meshery/meshery/pull/9456 [UI] fix zindex issues by @sudhanshutech in https://github.com/meshery/meshery/pull/9462 [Server] Update MeshModel components API. by @MUzairS15 in https://github.com/meshery/meshery/pull/9464 [UI] Enhance Meshmodel Registry UI by @sudhanshutech in https://github.com/meshery/meshery/pull/9465 [Server] MeshSync fingerprinting support. by @MUzairS15 in https://github.com/meshery/meshery/pull/9442 [utility] Custom infiniteScroll utility function by @sudhanshutech in https://github.com/meshery/meshery/pull/9466 [FIXED] mesheryctl golangci_lint failure by @zakisk in https://github.com/meshery/meshery/pull/9468 Added feature: `mesheryctl exp model search [query-text]` command by @zakisk in https://github.com/meshery/meshery/pull/9436 [Feature] Model: aws shape components by @leecalcote in https://github.com/meshery/meshery/pull/9457 Add Config Map Icon by @ShatilKhan in https://github.com/meshery/meshery/pull/8829 Add pod metrics icons by @Akshun-01 in https://github.com/meshery/meshery/pull/9330 add list item hover in theme by @aabidsofi19 in https://github.com/meshery/meshery/pull/9475 [Meshmodel] Use capabilites by @aabidsofi19 in https://github.com/meshery/meshery/pull/9474 [UI] FIx UI Dashboard Crash by @MUzairS15 in https://github.com/meshery/meshery/pull/9477 Meshmodel capabilites by @aabidsofi19 in https://github.com/meshery/meshery/pull/9478 [Meshmodel] meshery operator by @aabidsofi19 in https://github.com/meshery/meshery/pull/9480 [Meshmodel] remove ellipse and roundbarrel by @aabidsofi19 in https://github.com/meshery/meshery/pull/9481 Full Changelog: https://github.com/meshery/meshery/compare/v0.6.181...v0.6.182
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: commons.md

The . Based on . This image has no functionality itself, but is instead a base image, intended to be extended and utilized to build other images. All the alpine-based images in Lagoon inherit components from commons. `docker-sleep` - standardized one-hour sleep `fix-permissions` - automatically fixes permissions on a given directory to all group read-write `wait-for` - a small script to ensure that services are up and running in the correct order - based off https://github.com/eficode/wait-for `entrypoint-readiness` - checks to make sure that long-running entrypoints have completed `entrypoints` - a script to source all entrypoints under /lagoon/entrypoints/* in an alphabetical/numerical order The list of default entrypoints in this image is found at . Subsequent downstream images will also contribute entrypoints under `/lagoon` that are run in the eventual image.
Project: KICS (Provisioning / Security & Compliance)
File: faaefc15-51a5-419e-bb5e-51a4b5ab3485.md

title: RDS DB Instance Publicly Accessible hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: faaefc15-51a5-419e-bb5e-51a4b5ab3485 Query name: RDS DB Instance Publicly Accessible Platform: Terraform Severity: <span style="color:#ff0000">Critical</span> Category: Insecure Configurations URL: The field 'address' should not be set to '0.0.0.0/0'<br> ```tf title="Positive test num. 1 - tf file" hl_lines="10" resource "aliclouddbinstance" "example" { engine = "MySQL" engine_version = "5.6" instance_type = "rds.mysql.s2.large" instance_storage = "30" instancechargetype = "Postpaid" instance_name = var.name vswitchid = alicloudvswitch.example.id monitoring_period = "60" address = "0.0.0.0/0" } ``` ```tf title="Negative test num. 1 - tf file" resource "aliclouddbinstance" "example" { engine = "MySQL" engine_version = "5.6" instance_type = "rds.mysql.s2.large" instance_storage = "30" instancechargetype = "Postpaid" instance_name = var.name vswitchid = alicloudvswitch.example.id monitoring_period = "60" address = "10.23.12.24/24" } ``` ```tf title="Negative test num. 2 - tf file" resource "aliclouddbinstance" "example" { engine = "MySQL" engine_version = "5.6" instance_type = "rds.mysql.s2.large" instance_storage = "30" instancechargetype = "Postpaid" instance_name = var.name vswitchid = alicloudvswitch.example.id monitoring_period = "60" } ```
Project: YugabyteDB (App Definition and Development / Database)
File: 02-fundamentals.md

title: "Fundamentals" metaTitle: "Fundamentals | YugabyteDB Tutorials" description: "Step by step to learn how to install and use Yugabyte SQL." In this tutorial youll learn how to use YugabyteDBs PostgreSQL-compatible YSQL interface to query data from the Northwind sample database using SELECT, FROM, ORDER BY, LIMIT and other basic clauses and operators. For detailed information concerning specific clauses or operators, please refer to the official . To start, make sure you have all the necessary and have logged into the YSQL shell.fetch **Note:** These instructions last tested with YugabyteDB 1.3 Let's begin!
Project: ArangoDB (App Definition and Development / Database)
File: streaming_api_basics.md

by Takayuki Matsuoka LZ4 has the following API sets : "Auto Framing" API (lz4frame.h) : This is most recommended API for usual application. It guarantees interoperability with other LZ4 framing format compliant tools/libraries such as LZ4 command line utility, node-lz4, etc. "Block" API : This is recommended for simple purpose. It compress single raw memory block to LZ4 memory block and vice versa. "Streaming" API : This is designed for complex things. For example, compress huge stream data in restricted memory environment. Basically, you should use "Auto Framing" API. But if you want to write advanced application, it's time to use Block or Streaming APIs. Block API (de)compresses a single contiguous memory block. In other words, LZ4 library finds redundancy from a single contiguous memory block. Streaming API does same thing but (de)compresses multiple adjacent contiguous memory blocks. So LZ4 library could find more redundancy than Block API. The following figure shows difference between API and block sizes. In these figures, the original data is split into 4KiBytes contiguous chunks. ``` Original Data +++-+-+-+ | 4KiB Chunk A | 4KiB Chunk B | C | D |... | +++-+-+-+ Example (1) : Block API, 4KiB Block +++-+-+-+ | 4KiB Chunk A | 4KiB Chunk B | C | D |... | +++-+-+-+ | Block #1 | Block #2 | #3 | #4 |... | +++-+-+-+ (No Dependency) Example (2) : Block API, 8KiB Block +++-+-+-+ | 4KiB Chunk A | 4KiB Chunk B | C | D |... | +++-+-+-+ | Block #1 |Block #2 |... | +--+-+-+-+-+ ^ | ^ | | | | | +--+ +-+ Internal Dependency Internal Dependency Example (3) : Streaming API, 4KiB Block +++--+-+-+ | 4KiB Chunk A | 4KiB Chunk B | C | D |... | +++--+-+-+ | Block #1 | Block #2 | #3 | #4 |... | ++-+-+-++-+--+-+ ^ | ^ | ^ | | | | | | | +--+ +--+ ++ Dependency Dependency Dependency ``` In example (1), there is no dependency. All blocks are compressed independently. In example (2), naturally 8KiBytes block has internal dependency. But still block #1 and #2 are compressed independently. In example (3), block #2 has dependency to #1, also #3 has dependency to #2 and #1, #4 has #3, #2 and #1, and so on. Here, we can observe difference between example (2) and (3). In (2), there's no dependency between chunk B and C, but (3) has dependency between B and C. This dependency improves compression ratio. For efficiency, Streaming API doesn't keep a mirror copy of dependent (de)compressed memory. This means users should keep these dependent (de)compressed memory explicitly. Usually, "Dependent memory" is previous adjacent contiguous memory up to 64KiBytes. LZ4 will not access further memories.
Project: Grafeas (Provisioning / Security & Compliance)
File: CHANGELOG.md

This is the changelog of Grafeas server releases. For more information on versioning, see document. v0.2.3 SBOM enhancements. SLSA enhancements. Vex Assessment enhancements. v0.2.2 Enhanced support for Vulnerability Notes and Occurrences, with the following changes: Indicate the location at which an affected package was found in the container image. CVSS proto compatible with v2 and v3. More detailed status of language package scans in the Discovery occurrence. Added cvssversion field to indicate which version was used to populate fields: cvssscore and severity. Added support for Vex Assessments. Added support for language packages in Package Notes and Occurrences. Enhanced SLSA support. Added support for SLSA v0.2 to the intoto statement. Added SLSA v0.2 converter. Added SBOM support. Updated versions of frameworks and libraries Use ANTLR v4. Golang 1.20. v0.2.1: Update grpc-gateway v2.7.3 to generate compatible openapi spec. v0.2.0: Support for SBOM, using SPDX spec. Enhanced support for Occurrences, with the following additions (via v1beta1 API): , archival timestamp. Enhanced support for Vulnerability Notes and Occurrences, with the following additions (via v1beta1 API): per-source CVE reporting, CWEs tracking, CVSS v2 and v3 scores, improved package types support, vendor information, inclusive version ranges. Added support for ARM builds. Improved validation and permissions checks. Improved development support on Windows. Documentation and code cleanups and minor fixes. v0.1.6: Added support for in-toto. Added JWT support to attestation notes. v0.1.5: Upgraded to golang 1.14.0 Added lastscantime to discovery occurrences Added support for Windows updates v0.1.4: Support for use of existing secret and certs in Helm chart, in addition to generating them. Fix for handling http requests. Support for multi-platform protobuf compiler download. Checked in `v1beta1` go generated protos, to simplify integration downstream. v0.1.3: same as `v0.1.2`, but with generated protos uploaded with the release. v0.1.2: Support for multiple storage implementations. v0.1.1: Grafeas helm chart is compliant with stable requirements. Code cleanup. Added back `maxaffectedversion` to Vulnerability. v0.1.0: Grafeas server implements v1beta1 Grafeas API. Grafeas server can run: as standalone server, as k8s pod.
Project: Vitess (App Definition and Development / Database)
File: changelog.md

List of changes between bootstrap image versions. Update bootstrap image to build binaries using golang 1.15 Update build to golang 1.16 Update build to golang 1.17 Import new keys after Oracle rotated the PGP keys for their APT repository for MySQL 8.0+. Update build to golang 1.18 Update build to golang 1.18.1 Skipped because new images did not change `bootstrap-version` in `test.go` Update versions of zookeeper and consul Get `make tools` working on M1 mac Update build to golang 1.18.3 Update build to golang 1.18.4 Update build to golang 1.18.5 Update build to golang 1.18.7 Update build to golang 1.19.4 Update build to golang 1.20.1 Update build to golang 1.20.2 Update build to golang 1.20.3 Update build to golang 1.20.4 Update build to golang 1.20.5 Bump all images to bullseye base image Update build to golang 1.21.0 Update build to golang 1.21.1 Update build to golang 1.21.2 Update build to golang 1.21.3 Update build to golang 1.21.4 Update build to golang 1.21.5 Update build to golang 1.21.6 Update build to golang 1.22.0 Update build to golang 1.22.1 Move the bootstrap phase to the common image so other Dockerfiles don't have to rely on the version based tags. Update build to golang 1.22.2 Update build to golang 1.22.3
Project: KICS (Provisioning / Security & Compliance)
File: 8c978947-0ff6-485c-b0c2-0bfca6026466.md

title: Shared Volumes Between Containers hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8c978947-0ff6-485c-b0c2-0bfca6026466 Query name: Shared Volumes Between Containers Platform: DockerCompose Severity: <span style="color:#5bc0de">Info</span> Category: Insecure Configurations URL: Volumes shared between containers can cause data corruption or can be used to share malicious files between containers.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="16 9" version: "3" services: frontend: build: frontend ports: "8000:80" volumes: ./logic:/app backend: build: backend expose: 8080 volumes: ./logic:/app ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="8 17" version: "3" services: app: build: app ports: "0.0.0.0:80:80" volumes: shared-volume:/app/uploads depends_on: checker checker: build: checker expose: 8080 volumes: shared-volume:/uploads volumes: shared-volume: ``` ```yaml title="Negative test num. 1 - yaml file" version: "3" services: frontend: build: frontend ports: "8000:80" volumes: ./logic:/app backend: build: backend expose: 8080 volumes: ./bin:/app ```
Project: YugabyteDB (App Definition and Development / Database)
File: savepoint_rollback.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="518" height="70" viewbox="0 0 518 70"><path class="connector" d="M0 22h15m83 0h30m57 0h69m-136 25q0 5 5 5h5m106 0h5q5 0 5-5m-131-25q5 0 5 5v33q0 5 5 5h116q5 0 5-5v-33q0-5 5-5m5 0h10m36 0h30m89 0h20m-124 0q5 0 5 5v8q0 5 5 5h99q5 0 5-5v-8q0-5 5-5m5 0h10m54 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="83" height="25" rx="7"/><text class="text" x="25" y="22">ROLLBACK</text><rect class="literal" x="128" y="5" width="57" height="25" rx="7"/><text class="text" x="138" y="22">WORK</text><rect class="literal" x="128" y="35" width="106" height="25" rx="7"/><text class="text" x="138" y="52">TRANSACTION</text><rect class="literal" x="264" y="5" width="36" height="25" rx="7"/><text class="text" x="274" y="22">TO</text><rect class="literal" x="330" y="5" width="89" height="25" rx="7"/><text class="text" x="340" y="22">SAVEPOINT</text><a xlink:href="../../../syntaxresources/grammardiagrams#name"><rect class="rule" x="449" y="5" width="54" height="25"/><text class="text" x="459" y="22">name</text></a><polygon points="514,29 518,29 518,15 514,15" style="fill:black;stroke-width:0"/></svg>
Project: Meshery (Provisioning / Automation & Configuration)
File: volcano.md

layout: integration title: Volcano subtitle: Collaborative and visual infrastructure as code for Volcano image: /assets/img/integrations/volcano/icons/color/volcano-color.svg permalink: extensibility/integrations/volcano docURL: https://docs.meshery.io/extensibility/integrations/volcano description: integrations-category: Orchestration & Management integrations-subcategory: Scheduling & Orchestration registrant: Artifact Hub components: 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: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: expand-volume.md

title: Expand volume description: How to expand the volume of a Redis cluster keywords: [redis, expand volume] sidebar_position: 3 sidebar_label: Expand volume You can expand the storage volume size of each pod. :::note Volume expansion triggers a concurrent restart and the leader pod may change after the operation. ::: Check whether the cluster STATUS is `Running`. Otherwise, the following operations may fail. ```bash kbcli cluster list <name> ``` *Example* ```bash kbcli cluster list redis-cluster NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME redis-cluster default redis redis-7.0.6 Delete Running Apr 10,2023 19:00 UTC+0800 ``` Change configuration. There are 3 ways to apply volume expansion. Option 1. (Recommended) Use kbcli Configure the values of `--components`, `--volume-claim-templates`, and `--storage`, and run the command below to expand the volume. ```bash kbcli cluster volume-expand redis-cluster --components="redis" \ --volume-claim-templates="data" --storage="2Gi" ``` `--components` describes the component name for volume expansion. `--volume-claim-templates` describes the VolumeClaimTemplate names in components. `--storage` describes the volume storage size. Option 2. Create an OpsRequest Run the command below to expand the volume of a cluster. ```bash kubectl apply -f - <<EOF apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: name: ops-volume-expansion spec: clusterRef: redis-cluster type: VolumeExpansion volumeExpansion: componentName: redis volumeClaimTemplates: name: data storage: "2Gi" EOF ``` Option 3. Change the YAML file of the cluster Change the value of `spec.componentSpecs.volumeClaimTemplates.spec.resources` in the cluster YAML file. `spec.componentSpecs.volumeClaimTemplates.spec.resources` is the storage resource information of the pod and changing this value triggers the volume expansion of a cluster. ```yaml apiVersion: apps.kubeblocks.io/v1alpha1 kind: Cluster metadata: name: redis-cluster namespace: default spec: clusterDefinitionRef: redis clusterVersionRef: redis-7.0.6 componentSpecs: componentDefRef: redis name: redis replicas: 2 volumeClaimTemplates: name: data spec: accessModes: ReadWriteOnce resources: requests: storage: 1Gi # Change the volume storage size. terminationPolicy: Delete ``` Validate the volume expansion. ```bash kbcli cluster list <name> ``` *Example* ```bash kbcli cluster list redis-cluster > NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME redis-cluster default redis redis-7.0.6 Delete VolumeExpanding Apr 10,2023 16:27 UTC+0800 ``` STATUS=VolumeExpanding: it means the volume expansion is in progress. STATUS=Running: it means the volume expansion operation has been applied.