cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 9296f1cc-7a40-45de-bd41-f31745488a0e.md

title: SQS With SSE Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9296f1cc-7a40-45de-bd41-f31745488a0e Query name: SQS With SSE Disabled Platform: Crossplane Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: Amazon Simple Queue Service (SQS) queue should protect the contents of their messages using Server-Side Encryption (SSE)<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="40 6" apiVersion: sqs.aws.crossplane.io/v1beta1 kind: Queue metadata: name: test-queue3 spec: forProvider: region: us-east-1 delaySeconds: 4 redrivePolicy: deadLetterTargetArnRef: name: test-queue2 maxReceiveCount: 1 providerConfigRef: name: example apiVersion: apiextensions.crossplane.io/v1 kind: Composition metadata: name: cluster-aws labels: provider: aws cluster: eks spec: compositeTypeRef: apiVersion: mydev.org/v1alpha1 kind: CompositeCluster writeConnectionSecretsToNamespace: crossplane-system patchSets: name: metadata patches: fromFieldPath: metadata.labels resources: name: sample-ec2 base: apiVersion: sqs.aws.crossplane.io/v1beta1 kind: Queue metadata: name: test-queue4 spec: forProvider: region: us-east-1 delaySeconds: 4 redrivePolicy: deadLetterTargetArnRef: name: test-queue2 maxReceiveCount: 1 providerConfigRef: name: example ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: sqs.aws.crossplane.io/v1beta1 kind: Queue metadata: name: test-queue spec: forProvider: region: us-east-1 kmsMasterKeyId: KMS-KEY-ARN delaySeconds: 4 redrivePolicy: deadLetterTargetArnRef: name: test-queue2 maxReceiveCount: 1 providerConfigRef: name: example apiVersion: apiextensions.crossplane.io/v1 kind: Composition metadata: name: cluster-aws labels: provider: aws cluster: eks spec: compositeTypeRef: apiVersion: mydev.org/v1alpha1 kind: CompositeCluster writeConnectionSecretsToNamespace: crossplane-system patchSets: name: metadata patches: fromFieldPath: metadata.labels resources: name: sample-ec2 base: apiVersion: sqs.aws.crossplane.io/v1beta1 kind: Queue metadata: name: test-queue2 spec: forProvider: region: us-east-1 kmsMasterKeyId: KMS-KEY-ARN delaySeconds: 4 redrivePolicy: deadLetterTargetArnRef: name: test-queue2 maxReceiveCount: 1 providerConfigRef: name: example ```
Project: Vault (Provisioning / Key Management)
File: plugin-submission.md

name: Plugin Submission about: Submit a community Vault plugin! title: "[Plugin Portal] Plugin Submission - <PLUGIN NAME>" labels: ecosystem/plugin assignees: '' Please provide details for the plugin to be listed. All fields are required for a submission to be included in the page. Plugin Information Name as it would appear listed: Plugin type (secrets/auth/database): Repository link:
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: adr007-use-msw-to-mock-service-requests.md

id: adrs-adr007 title: 'ADR007: Use MSW to mock http requests' description: Architecture Decision Record (ADR) log on Use MSW to mock http requests Network request mocking can be a total pain sometimes, in all different types of tests, unit tests to e2e tests always have their own implementation of mocking these requests. There's been traction in the outer community towards using this library to mock network requests by using an express style declaration for routes. react-testing-library suggests using this library instead of mocking fetch directly whether this be in a browser or in node. https://github.com/mswjs/msw Moving forward, we have decided that any `fetch` or `XMLHTTPRequest` that happens, should be mocked by using `msw`. Here is an example: ```ts import { setupWorker, rest } from 'msw'; const worker = setupWorker( rest.get('*/user/:userId', (req, res, ctx) => { return res( ctx.json({ firstName: 'John', lastName: 'Maverick', }), ); }), ); // Start the Mock Service Worker worker.start(); ``` and in a more real life scenario, taken from ```ts beforeEach(() => { server.use( rest.get(`${mockApiOrigin}${mockBasePath}/entities`, (_, res, ctx) => { return res(ctx.json(defaultResponse)); }), ); }); it('should entities from correct endpoint', async () => { const entities = await client.getEntities(); expect(entities).toEqual(defaultResponse); }); ``` A little more code to write Gradually will replace the codebase with `msw`
Project: StarRocks (App Definition and Development / Database)
File: add_months.md

displayed_sidebar: "English" Adds a specified number of months to a given date (DATE or DATETIME). The function provides similar functionalities. The day component in the resulting month remains the same as that specified in `date`, unless the resulting month has fewer days than the day component of the given date, in which case the day will be the last day of the resulting month. For example, `select addmonths('2022-01-31', 1);` returns `2022-02-28 00:00:00`. If the resulting month has more days than the day component of the given date, the result has the same day component as `date`. For example, `select addmonths('2022-02-28', 1)` returns `2022-03-28 00:00:00`. Difference with Oracle: In Oracle, if `date` is the last day of the month, then the result is the last day of the resulting month. Returns NULL if an invalid date or a NULL argument is passed in. ```Haskell ADD_MONTH(date, months) ``` `date`: It must be a valid date or datetime expression. `months`: the months you want to add. It must be an integer. A positive integer adds months to `date`. A negative integer subtracts months from `date`. Returns a DATETIME value. If the date does not exist, for example, `2020-02-30`, NULL is returned. If the date is a DATE value, it will be converted into a DATETIME value. ```Plain Text select add_months('2022-01-01', 2); +--+ | add_months('2022-01-01', 2) | +--+ | 2022-03-01 00:00:00 | +--+ select add_months('2022-01-01', -5); ++ | add_months('2022-01-01', -5) | ++ | 2021-08-01 00:00:00 | ++ select add_months('2022-01-31', 1); +--+ | add_months('2022-01-31', 1) | +--+ | 2022-02-28 00:00:00 | +--+ select add_months('2022-01-31 17:01:02', -2); ++ | add_months('2022-01-31 17:01:02', -2) | ++ | 2021-11-30 17:01:02 | ++ select add_months('2022-02-28', 1); +--+ | add_months('2022-02-28', 1) | +--+ | 2022-03-28 00:00:00 | +--+ ```
Project: ClickHouse (App Definition and Development / Database)
File: merges.md

slug: /en/operations/system-tables/merges Contains information about merges and part mutations currently in process for tables in the MergeTree family. Columns: `database` (String) The name of the database the table is in. `table` (String) Table name. `elapsed` (Float64) The time elapsed (in seconds) since the merge started. `progress` (Float64) The percentage of completed work from 0 to 1. `num_parts` (UInt64) The number of pieces to be merged. `resultpartname` (String) The name of the part that will be formed as the result of merging. `is_mutation` (UInt8) 1 if this process is a part mutation. `totalsizebytes_compressed` (UInt64) The total size of the compressed data in the merged chunks. `totalsizemarks` (UInt64) The total number of marks in the merged parts. `bytesreaduncompressed` (UInt64) Number of bytes read, uncompressed. `rows_read` (UInt64) Number of rows read. `byteswrittenuncompressed` (UInt64) Number of bytes written, uncompressed. `rows_written` (UInt64) Number of rows written. `memory_usage` (UInt64) Memory consumption of the merge process. `thread_id` (UInt64) Thread ID of the merge process. `merge_type` The type of current merge. Empty if it's an mutation. `merge_algorithm` The algorithm used in current merge. Empty if it's an mutation.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: build-arg-file.md

Specifies a file containing lines of build arguments of the form `arg=value`. The suggested file name is `argfile.conf`. Comment lines beginning with `#` are ignored, along with blank lines. All others must be of the `arg=value` format passed to `--build-arg`. If several arguments are provided via the `--build-arg-file` and `--build-arg` options, the build arguments are merged across all of the provided files and command line arguments. Any file provided in a `--build-arg-file` option is read before the arguments supplied via the `--build-arg` option. When a given argument name is specified several times, the last instance is the one that is passed to the resulting builds. This means `--build-arg` values always override those in a `--build-arg-file`.
Project: kpt (Provisioning / Automation & Configuration)
File: bug.md

name: Bug Report about: Report an issue with kpt title: "" labels: bug assignees: "" <!-- Please include any additional information related to your issue --> <!-- EX: --> <!-- Kpt Version (you may find this by running `kpt version` in your shell) --> <!-- Kpt Package that can demonstrate the error. Ex: https://github.com/kubernetes/examples/staging/cockroachdb -->
Project: KICS (Provisioning / Security & Compliance)
File: a6a4d4fc-4e8f-47d1-969f-e9d4a084f3b9.md

title: PSP Set To Privileged hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a6a4d4fc-4e8f-47d1-969f-e9d4a084f3b9 Query name: PSP Set To Privileged Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: Do not allow pod to request execution as privileged.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="6" resource "kubernetespodsecurity_policy" "example" { metadata { name = "terraform-example" } spec { privileged = true allowprivilegeescalation = false volumes = [ "configMap", "emptyDir", "projected", "secret", "downwardAPI", "persistentVolumeClaim", ] runasuser { rule = "MustRunAsNonRoot" } se_linux { rule = "RunAsAny" } supplemental_groups { rule = "MustRunAs" range { min = 1 max = 65535 } } fs_group { rule = "MustRunAs" range { min = 1 max = 65535 } } readonlyroot_filesystem = true } } ``` ```tf title="Negative test num. 1 - tf file" resource "kubernetespodsecurity_policy" "example2" { metadata { name = "terraform-example" } spec { privileged = false allowprivilegeescalation = false volumes = [ "configMap", "emptyDir", "projected", "secret", "downwardAPI", "persistentVolumeClaim", ] runasuser { rule = "MustRunAsNonRoot" } se_linux { rule = "RunAsAny" } supplemental_groups { rule = "MustRunAs" range { min = 1 max = 65535 } } fs_group { rule = "MustRunAs" range { min = 1 max = 65535 } } readonlyroot_filesystem = true } } ```
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_plugin_kubectl.KubeOptions.md

/ / KubeOptions .KubeOptions An incomplete set of kubectl options `ParsedOptions` `KubeOptions` `Optional` A: `boolean` `Optional` \_: `string`[] ParsedOptions.\_ packages/core/mdist/models/command.d.ts:79 `Optional` all-namespaces: `boolean` `Optional` c: `string` `Optional` cluster: `string` `Optional` container: `string` `Optional` context: `string` `Optional` dry-run: `string` \| `boolean` `Optional` f: `string` \| `string`[] `Optional` filename: `string` \| `string`[] `Optional` h: `boolean` `Optional` help: `boolean` `Optional` k: `string` `Optional` kubeconfig: `string` `Optional` kustomize: `string` `Optional` l: `string` `Optional` label: `string` `Optional` limit: `number` `Optional` n: `string` \| `string`[] `Optional` namespace: `string` \| `string`[] `Optional` o: `string` `Optional` output: `string` `Optional` p: `boolean` `Optional` previous: `boolean` `Optional` sort-by: `string` `Optional` w: `boolean` `Optional` wait: `boolean` `Optional` watch: `boolean` `Optional` watch-only: `boolean`
Project: SuperEdge (Provisioning / Automation & Configuration)
File: CHANGELOG-0.1.md

- First Release! This is the first release of SuperEdge, which includes a series of features to transform a Kubernetes cluster to an edge-native container management system for edge computing. Tunnel Proxies requests from master nodes to edge worker nodes, which allows accessing edge nodes with no public IP address. It is enabled by default for request from kube-apiserver to Kubelet on the Edge Worker nodes. Supports TCP/HTTP/HTTPS. ServiceGroup Enhanced application management on the edge by grouping related applications and edge worker nodes. Offers two new CRDs for managing serviceGroup - DeploymentGrid & ServiceGrid. Provides isolated internal network for applications inside the same serviceGroup. Edge Autonomy Keeps services on the edge nodes up and running stably despite of network disconnection between edge and cloud. Allows pods on the edge to restart correctly even though losing connection to the master kube-apiserver. EdgeHealth Enhanced monitoring of edge worker nodes. Distributed health check on groups of edge nodes. Determines status of the node based on the status checks from nodes within the same health check group. Eliminates false alert in case of losing cloud-to-edge network connection. EdgeAdm EdgeAdm is a command-line tool to help users to deploy SuperEdge to native Kubernetes in 1-click.
Project: ShardingSphere (App Definition and Development / Database)
File: LICENSE.md

The MIT License (MIT) Copyright (c) 2014 Grav Copyright (c) 2016 MATHIEU CORNIC Copyright (c) 2017 Valere JEANTET Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Project: SlimToolkit (Provisioning / Security & Compliance)
File: MAINTENANCE.md

The compose-go library has to be kept up-to-date with approved changes in the . As we define new attributes to be added to the spec, this typically requires: Updating `schema` to latest version from compose-spec Creating the matching struct/field in `types` Creating the matching `CheckXX` method in `compatibility` If the new attribute replaces a legacy one we want to deprecate, creating the adequate logic in `normalize.go`
Project: Apache Storm (App Definition and Development / Streaming & Messaging)
File: storm-jms.md

title: Storm JMS Integration layout: documentation documentation: true Storm JMS is a generic framework for integrating JMS messaging within the Storm framework. Storm-JMS allows you to inject data into Storm via a generic JMS spout, as well as consume data from Storm via a generic JMS bolt. Both the JMS Spout and JMS Bolt are data agnostic. To use them, you provide a simple Java class that bridges the JMS and Storm APIs and encapsulates and domain-specific logic. The JMS Spout component allows for data published to a JMS topic or queue to be consumed by a Storm topology. A JMS Spout connects to a JMS Destination (topic or queue), and emits Storm "Tuple" objects based on the content of the JMS message received. The JMS Bolt component allows for data within a Storm topology to be published to a JMS destination (topic or queue). A JMS Bolt connects to a JMS Destination, and publishes JMS Messages based on the Storm "Tuple" objects it receives.
Project: KICS (Provisioning / Security & Compliance)
File: b2418936-cd47-4ea2-8346-623c0bdb87bd.md

title: AKS RBAC Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b2418936-cd47-4ea2-8346-623c0bdb87bd Query name: AKS RBAC Disabled Platform: Crossplane Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Azure Container Service (AKS) instance should have role-based access control (RBAC) enabled<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="40 13" apiVersion: compute.azure.crossplane.io/v1alpha3 kind: AKSCluster metadata: name: anais-crossplane-demo spec: location: eastus version: "1.19.7" nodeVMSize: StandardD2v2 resourceGroupNameRef: name: anais-resource dnsNamePrefix: dt nodeCount: 2 disableRBAC: true apiVersion: apiextensions.crossplane.io/v1 kind: Composition metadata: name: aks.multik8s.platformref.crossplane.io labels: provider: AZURE spec: compositeTypeRef: apiVersion: multik8s.platformref.crossplane.io/v1alpha1 kind: AKS resources: name: sample-ec2 base: apiVersion: compute.azure.crossplane.io/v1alpha3 kind: AKSCluster metadata: name: anais-crossplane-demo spec: location: eastus version: "1.19.7" nodeVMSize: StandardD2v2 resourceGroupNameRef: name: anais-resource dnsNamePrefix: dt nodeCount: 2 disableRBAC: true ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: compute.azure.crossplane.io/v1alpha3 kind: AKSCluster metadata: name: anais-crossplane-demo spec: location: eastus version: "1.19.7" nodeVMSize: StandardD2v2 resourceGroupNameRef: name: anais-resource dnsNamePrefix: dt nodeCount: 2 disableRBAC: false apiVersion: apiextensions.crossplane.io/v1 kind: Composition metadata: name: aks.multik8s.platformref.crossplane.io labels: provider: AZURE spec: compositeTypeRef: apiVersion: multik8s.platformref.crossplane.io/v1alpha1 kind: AKS resources: name: sample-ec2 base: apiVersion: compute.azure.crossplane.io/v1alpha3 kind: AKSCluster metadata: name: anais-crossplane-demo spec: location: eastus version: "1.19.7" nodeVMSize: StandardD2v2 resourceGroupNameRef: name: anais-resource dnsNamePrefix: dt nodeCount: 2 ```
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.2.2.0.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Blocker | Define constraints on Auxiliary Service names. Change ShuffleHandler service name from mapreduce.shuffle to mapreduce\_shuffle.* WARNING: No release note provided for this change. | Major | Clean up Fair Scheduler configuration loading* WARNING: No release note provided for this change. | Blocker | disable symlinks temporarily* During review of symbolic links, many issues were found related to the impact on semantics of existing APIs such FileSystem#listStatus, FileSystem#globStatus etc. There were also many issues brought up about symbolic links, and the impact on security and functionality of HDFS. All these issues will be addressed in the upcoming release 2.3. Until then the feature is temporarily disabled.
Project: KICS (Provisioning / Security & Compliance)
File: d1846b12-20c5-4d45-8798-fc35b79268eb.md

title: ECR Image Tag Not Immutable hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d1846b12-20c5-4d45-8798-fc35b79268eb Query name: ECR Image Tag Not Immutable Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: ECR should have an image tag be immutable. This prevents image tags from being overwritten.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="10 3" resource "awsecrrepository" "foo2" { name = "bar" imagetagmutability = "MUTABLE" imagescanningconfiguration { scanonpush = true } } resource "awsecrrepository" "foo3" { name = "bar" imagescanningconfiguration { scanonpush = true } } ``` ```tf title="Negative test num. 1 - tf file" resource "awsecrrepository" "foo" { name = "bar" imagetagmutability = "IMMUTABLE" imagescanningconfiguration { scanonpush = true } } ```
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: v1.6.0.md

id: v1.6.0 title: v1.6.0 description: Backstage Release v1.6.0 These are the release notes for the v1.6.0 release of . A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for the hard work in getting this release developed and done. Weve replaced `sucrase` with for transpilation in the Backstage CLI. While `swc` has slightly slower transpilation times, its a library backed by a larger community, and allows us to take advantage of out of the box. Theres a few things that could possibly break installations of Backstage and compilation, you can read more about it in the Backstage has for a long time been using React Router version `6.0.0-beta.0`. We adopted this unstable version because v6 had some new features that fit really well with Backstage, particularly relative routing. Because we jumped on this early and unstable version, we knew that we would at some point need a breaking migration to the stable version of React Router v6, which is the point we're at now! The migration is controlled by each app, meaning this release will not force you to migrate straight away, you can do so at your own pace. Check out the for all you need to know! It is now possible to migrate Backstage projects to use Yarn 3. See the for more information. Migrating to Yarn 3 is optional, and Backstage projects created with `@backstage/create-app` will still use classic Yarn by default. The `user-settings` plugin now has an associated backend. This allows for the persistence of settings in your database, essentially in the form of a basic per-user key-value JSON store. As this backend was added, `user-settings` also gained a `UserSettingsStore` class that implements the `storageApiRef` Utility API. If you install the backend as well as this frontend API, your starred entities and other storage-API-based features will no longer just be persisted in your browsers local storage, but centrally so that all your devices can leverage them. Contributed by in This plugin can be used to create custom collections of Entities that can be shared throughout Backstage or for private usage. Contributed by in Be sure to upgrade to the latest version of `@backstage/plugin-scaffolder-backend`, as it contains an explicit bump of a transitive dependency where a vulnerability was discovered. If you subscribe to CVE notifications you will already have received this update. We recommend that you keep your Backstage project up to date with this latest release. For more guidance on how to upgrade, check out the documentation for . Below you can find a list of links and references to help you learn about and start using this new release. , , and Backstage's for discussions and support Backstage , , and Sign up for our if you want to be informed about what is happening in the world of Backstage.