cwielenb/CNCF-Dataset huggingface dataset:
Project: Sonobuoy (Provisioning / Security & Compliance)
File: dryRun-listGenerator.md

This process has been dramatically simplified. All that is necessary is that you create a new Git branch/PR and run `./scripts/gathere2edata.sh` and commit the changes. You can look through the script and the supporting files for a more in depth explanation of the process but it just boils down to finding the proper versions to check, running them in DRY_RUN mode, and extracting the necessary data. DEBUG If running this against a local kind cluster the server could run out of space for more conformance images (e.g. "no space left on device") Clear docker cache with `docker image prune -a` Add more disc space to docker (60GB to 300GB)
Project: Checkov (Provisioning / Security & Compliance)
File: PULL_REQUEST_TEMPLATE.md

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. Be aware that we use the title to create changelog automatically and therefore only allow specific prefixes break: to indicate a breaking change, this supersedes any of the types feat: to indicate new features or checks fix: to indicate a bugfix or handling of edge cases of existing checks docs: to indicate an update to our documentation chore: to indicate adjustments to workflow files or dependency updates platform: to indicate a change needed for the platform Additionally a scope is needs to be added to the prefix, which indicates the targeted framework, in doubt choose 'general'. Allowed prefixs: ansible|argo|arm|azure|bicep|bitbucket|circleci|cloudformation|dockerfile|github|gha|gitlab|helm|kubernetes|kustomize|openapi|sast|sca|secrets|serverless|terraform|general|graph|terraformplan|terraformjson ex. feat(terraform): add CKVAWS123 to ensure that VPC Endpoint Service is configured for Manual Acceptance " Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Fixes # (issue) Include a description of what makes it a violation and any relevant external links. How does someone fix the issue in code and/or in runtime? [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] I have added tests that prove my feature, policy, or fix is effective and works [ ] New and existing tests pass locally with my changes [ ] Any dependent changes have been merged and published in downstream modules
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: logger.md

id: logger title: Logger Service sidebar_label: Logger description: Documentation for the Logger service This service allows plugins to output logging information. There are actually two logger services: a root logger, and a plugin logger which is bound to individual plugins, so that you will get nice messages with the plugin ID referenced in the log lines. The following example shows how to get the logger in your `example` backend plugin and create a warning message that will be printed nicely to the console. ```ts import { coreServices, createBackendPlugin, } from '@backstage/backend-plugin-api'; createBackendPlugin({ pluginId: 'example', register(env) { env.registerInit({ deps: { log: coreServices.logger, }, async init({ log }) { log.warn("Here's a nice log line that's a warning!"); }, }); }, }); ``` The root logger is the logger that is used by other root services. It's where the implementation lies for creating child loggers around the backstage ecosystem including child loggers for plugins with the correct metadata and annotations. If you want to override the implementation for logging across all of the backend, this is the service that you should override. The following example is how you can override the root logger service to add additional metadata to all log lines. ```ts import { coreServices } from '@backstage/backend-plugin-api'; import { WinstonLogger } from '@backstage/backend-app-api'; const backend = createBackend(); backend.add( createServiceFactory({ service: coreServices.rootLogger, deps: { config: coreServices.rootConfig, }, async factory({ config }) { const logger = WinstonLogger.create({ meta: { service: 'backstage', // here's some additional information that is not part of the // original implementation podName: 'myk8spod', }, level: process.env.LOG_LEVEL || 'info', format: process.env.NODE_ENV === 'production' ? format.json() : WinstonLogger.colorFormat(), transports: [new transports.Console()], }); return logger; }, }), ); ```
Project: YDB (App Definition and Development / Database)
File: conditional_values.md

Select all the episode names of the first season of each series and sort them by name. {% include %} ```sql SELECT seriestitle, -- seriestitle is defined below in GROUP BY String::JoinFromList( -- calling a C++ UDF, -- see below AGGREGATE_LIST(title), -- an aggregate function that -- returns all the passed values as a list ", " -- String::JoinFromList concatenates -- items of a given list (the first argument) -- to a string using the separator (the second argument) ) AS episode_titles FROM episodes WHERE series_id IN (1,2) -- IN defines the set of values in the WHERE clause, -- to be included into the result. -- Syntax: -- test_expression (NOT) IN -- ( subquery | expression ` ,...n ` ) -- If the value of test_expression is equal -- to any value returned by subquery or is equal to -- any expression from the comma-separated list, -- the result value is TRUE. Otherwise, it's FALSE. -- using NOT IN negates the result of subquery -- or expression. -- Warning: using null values together with -- IN or NOT IN may lead to undesirable outcomes. AND season_id = 1 GROUP BY CASE -- CASE evaluates a list of conditions and -- returns one of multiple possible resulting -- expressions. CASE can be used in any -- statement or with any clause -- that supports a given statement. For example, you can use CASE in -- statements such as SELECT, UPDATE, and DELETE, -- and in clauses such as IN, WHERE, and ORDER BY. WHEN series_id = 1 THEN "IT Crowd" ELSE "Other series" END AS series_title -- GROUP BY can be performed on -- an arbitrary expression. -- The result is available in a SELECT -- via the alias specified with AS. ; COMMIT; ```
Project: ClickHouse (App Definition and Development / Database)
File: 96_installation-issues.md

name: Installation issue about: Issue with ClickHouse installation from https://clickhouse.com/docs/en/install/ title: '' labels: comp-install assignees: '' I have tried the following solutions: https://clickhouse.com/docs/en/faq/troubleshooting/#troubleshooting-installation-errors Installation type Packages, docker, single binary, curl? Source of the ClickHouse A link to the source. Or the command you've tried Expected result What you expected The actual result What you get How to reproduce For Linux-based operating systems: provide a script for clear docker container from the official image For anything else: steps to reproduce on as much as possible clear system
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_storage_object_acl.md

+++ title = "googlestorageobject_acl resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlestorageobject_acl" identifier = "inspec/resources/gcp/googlestorageobjectacl.md googlestorageobjectacl resource" parent = "inspec/resources/gcp" +++ A `googlestorageobject_acl` is used to test a Google ObjectACL resource ``` describe googlestorageobject_acl(bucket: 'bucket-with-object', object: 'image1', entity: user-email) do it { should exist } its('role') { should cmp "OWNER" } its('bucket') { should eq 'bucket-with-object' } its('email') { should include entity-email.com } end describe googlestorageobject_acl(bucket: 'bucket-with-object', object: 'image1', entity: "allUsers") do it { should_not exist } end ``` describe googlestorageobject_acl(bucket: 'bucket-buvsjjcndqz', object: 'bucket-object-pmxbiikq', entity: 'user-object-viewer@spaterson-project.iam.gserviceaccount.com') do it { should exist } end describe googlestorageobject_acl(bucket: 'bucket-buvsjjcndqz', object: 'bucket-object-pmxbiikq', entity: 'user-object-viewer@spaterson-project.iam.gserviceaccount.com') do its('role') { should eq 'OWNER' } end Properties that can be accessed from the `googlestorageobject_acl` resource: `domain` : The domain associated with the entity. `email` : The email address associated with the entity. `entity` : The entity holding the permission, in one of the following forms: user-{{userId}} user-{{email}} (such as "user-liz@example.com") group-{{groupId}} group-{{email}} (such as "group-example@googlegroups.com") domain-{{domain}} (such as "domain-example.com") project-team-{{projectId}} allUsers allAuthenticatedUsers `entity_id` : The ID for the entity `generation` : The content generation of the object, if applied to an object. `id` : The ID of the access-control entry. `object` : The name of the object, if applied to an object. `project_team` : The project team associated with the entity `project_number` : The project team associated with the entity `team` : The team. Possible values: editors owners viewers `role` : The access permission for the entity. Possible values: OWNER READER Ensure the is enabled for the current project.
Project: ClickHouse (App Definition and Development / Database)
File: v20.9.6.14-stable.md

Backported in : Make it possible to connect to `clickhouse-server` secure endpoint which requires SNI. This is possible when `clickhouse-server` is hosted behind TLS proxy. (). Backported in : Query is finished faster in case of exception. Cancel execution on remote replicas if exception happens. (). Backported in : fixes fixes fix remote query failure when using 'if' suffix aggregate function. (). Backported in : This will fix optimizereadinorder/optimizeaggregationinorder with max_threads>0 and expression in ORDER BY. (). Backported in : Fix `IN` operator over several columns and tuples with enabled `transformnullin` setting. Fixes . (). Backported in : Fix crash when using `any` without any arguments. This is for . cc @azat. (). Backported in : Abort multipart upload if no data was written to WriteBufferFromS3. (). Backported in : Prevent clickhouse server crashes when using TimeSeriesGroupSum. (). Backported in : Fix possible error `Illegal type of argument` for queries with `ORDER BY`. Fixes . (). Backported in : Install script should always create subdirs in config folders. This is only relevant for Docker build with custom config. (). Backported in : Fix possible server crash after `ALTER TABLE ... MODIFY COLUMN ... NewType` when `SELECT` have `WHERE` expression on altering column and alter doesn't finished yet. (). Backported in : Reresolve the IP of the `formatavroschemaregistryurl` in case of errors. (). Backported in : Fix bug when `ON CLUSTER` queries may hang forever for non-leader ReplicatedMergeTreeTables. ().
Project: Beam (App Definition and Development / Streaming & Messaging)
File: release-blocking.md

title: "Release blockers" aliases: /contribute/release-blockers/ <!-- 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. --> A release blocking GitHub Issue is any open Issue that has its Milestone set to an upcoming version of Beam. A bug should block a release if it is a significant regression or loss of functionality. It should usually have priority Critical/P1. Lower priorities do not have urgency, while Blocker/P0 is reserved for issues so urgent they do not wait for a release. By default, features do not block releases. Beam has a steady 6 week cadence of cutting release branches and releasing. Features "catch the train" or else wait for the next release. A feature can block a release if there is community consensus to delay a release in order to include the feature.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.2.md

layout: release date: 2023-12-19 tag: v0.7.2 [bug] Fix env component @theBeginner86 (#9659) chore: add aws controllers @VihasMakwana (#9650) [Model] AWS EKS: Model and Component metadata @leecalcote (#9649) chore: add aws eks controller statically @VihasMakwana (#9638) [Environments] Environments page @senali-d (#9647) [UI] Correct indicators for context switcher. @MUzairS15 (#9645) Upgrade Performance table to sistent table @sudhanshutech (#9648) update mdeditor @aabidsofi19 (#9646) [UI] - Prompt Component button color @senali-d (#9644) chore(build-and-release-stable): ignore rc releases @chenrui333 (#9642) chore(ci/cd): Update e2e tests with newer k8s versions @webstradev (#9665) [environments] Add API to Get Connections for Environment @theBeginner86 (#9651) [environments] Add API to Get Connections for Environment @theBeginner86 (#9651) Thank you to our contributors for making this release possible: @MUzairS15, @VihasMakwana, @Yashsharma1911, @aabidsofi19, @chenrui333, @leecalcote, @meshery[bot], @senali-d, @sudhanshutech, @theBeginner86 and @webstradev
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_list_ports.md

title: "Command - devspace list ports" sidebar_label: devspace list ports Lists port forwarding configurations ``` devspace list ports [flags] ``` ``` Lists the port forwarding configurations ``` ``` -h, --help help for ports ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ```
Project: KICS (Provisioning / Security & Compliance)
File: bc280331-27b9-4acb-a010-018e8098aa5d.md

title: VM With Full Cloud Access hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: bc280331-27b9-4acb-a010-018e8098aa5d Query name: VM With Full Cloud Access Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: A VM instance is configured to use the default service account with full access to all Cloud APIs<br> ```tf title="Positive test num. 1 - tf file" hl_lines="20" resource "googlecomputeinstance" "positive1" { name = "test" machine_type = "e2-medium" zone = "us-central1-a" boot_disk { initialize_params { image = "debian-cloud/debian-9" } } network_interface { network = "default" access_config { // Ephemeral IP } } service_account { scopes = ["userinfo-email", "compute-ro", "storage-ro", "cloud-platform"] } } ``` ```tf title="Negative test num. 1 - tf file" resource "googlecomputeinstance" "negative1" { name = "test" machine_type = "e2-medium" zone = "us-central1-a" boot_disk { initialize_params { image = "debian-cloud/debian-9" } } network_interface { network = "default" access_config { // Ephemeral IP } } service_account { scopes = ["userinfo-email", "compute-ro", "storage-ro"] } } ```
Project: Crunchy Postgres Operator (App Definition and Development / Database)
File: limitations.md

<!-- Copyright 2022 - 2024 Crunchy Data Solutions, Inc. 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. --> Most resource types require this kind of name. It must be 253 characters or less, lowercase, and alphanumeric with hyphens U+002D and dots U+002E allowed in between. Some resource types require this kind of name. It must be 63 characters or less, lowercase, and alphanumeric with hyphens U+002D allowed in between. Some have a stricter requirement to start with an alphabetic (nonnumerical) character. Label names must be 317 characters or less. The portion before an optional slash U+002F must be a DNS subdomain. The portion after must be 63 characters or less. Label values must be 63 characters or less and can be empty. Both label names and values must be alphanumeric with hyphens U+002D, underscores U+005F, and dots U+002E allowed in between. Annotation names must be 317 characters or less. The portion before an optional slash U+002F must be a DNS subdomain. The portion after must be 63 characters or less and alphanumeric with hyphens U+002D, underscores U+005F, and dots U+002E allowed in between. Annotation values may contain anything, but the combined size of all names and values must be 256 KiB or less. The Kubernetes API validates custom resource metadata. . It may be possible to limit this further through validation. This is a stated goal of . . but must be . . . When `.spec.completionMode = Indexed`, the name must be shorter (closer to 61 characters, it depends). When `.spec.manualSelector` is unset, its Pods get (and must have) a "job-name" label, limiting the name to 63 characters or less. . . . The strategy for truncates to 63 characters. The `.spec.hostname` field must be 63 characters or less. PodDisruptionBudget (PDB) . Role RoleBinding . that must begin with a letter. ServiceAccount (subdomain) , but its Pods get so it must be shorter (closer to 61 characters, it depends). Its Pods also get a "controller-revision-hash" label with , limiting the name to 52 characters or less.
Project: YugabyteDB (App Definition and Development / Database)
File: tslastn.md

title: TSLASTN linkTitle: TSLASTN description: TSLASTN menu: preview: parent: api-yedis weight: 2430 aliases: /preview/api/redis/tslastn /preview/api/yedis/tslastn type: docs `TSLASTN key N` This command fetches the latest N entries in the time series that is specified by the given `key`. The elements are returned in ascending order of timestamps. If the given `key` is associated with non-time series data, an error is raised. If the given `N` is not a positive 32 bit integer, an error is raised. Returns a list of timestamp, value pairs for the latest N entries in the time series. You can do this as shown below. ```sh $ TSADD ts_key 10 v1 20 v2 30 v3 40 v4 50 v5 ``` ``` "OK" ``` ```sh $ TSLASTN ts_key 2 ``` ``` 1) "40" 2) "v4" 3) "50" 4) "v5" ``` ```sh $ TSLASTN ts_key 3 ``` ``` 1) "30" 2) "v3" 3) "40" 4) "v4" 5) "50" 6) "v5" ``` ```sh $ TSLASTN ts_key 9999999999 ``` ``` (error) ERR tslastn: limit field 9999999999 is not within valid bounds ``` ```sh $ TSLASTN ts_key 0 ``` ``` (error) ERR tslastn: limit field 0 is not within valid bounds ``` ```sh $ TSLASTN ts_key -1 ``` ``` (error) ERR tslastn: limit field -1 is not within valid bounds ``` , , , , ,
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: pull.md

Pull image policy. The default is missing. always: Always pull the image and throw an error if the pull fails. missing: Pull the image only when the image is not in the local containers storage. Throw an error if no image is found and the pull fails. never: Never pull the image but use the one from the local containers storage. Throw an error if no image is found. newer: Pull if the image on the registry is newer than the one in the local containers storage. An image is considered to be newer when the digests are different. Comparing the time stamps is prone to errors. Pull errors are suppressed if a local image was found.
Project: Meshery (Provisioning / Automation & Configuration)
File: thanos-operator.md

layout: integration title: Thanos Operator subtitle: Collaborative and visual infrastructure as code for Thanos Operator image: /assets/img/integrations/thanos-operator/icons/color/thanos-operator-color.svg permalink: extensibility/integrations/thanos-operator docURL: https://docs.meshery.io/extensibility/integrations/thanos-operator description: integrations-category: Observability and Analysis integrations-subcategory: Monitoring registrant: Artifact Hub components: name: object-store colorIcon: assets/img/integrations/thanos-operator/components/object-store/icons/color/object-store-color.svg whiteIcon: assets/img/integrations/thanos-operator/components/object-store/icons/white/object-store-white.svg description: name: receiver colorIcon: assets/img/integrations/thanos-operator/components/receiver/icons/color/receiver-color.svg whiteIcon: assets/img/integrations/thanos-operator/components/receiver/icons/white/receiver-white.svg description: name: store-endpoint colorIcon: assets/img/integrations/thanos-operator/components/store-endpoint/icons/color/store-endpoint-color.svg whiteIcon: assets/img/integrations/thanos-operator/components/store-endpoint/icons/white/store-endpoint-white.svg description: name: thanos colorIcon: assets/img/integrations/thanos-operator/components/thanos/icons/color/thanos-color.svg whiteIcon: assets/img/integrations/thanos-operator/components/thanos/icons/white/thanos-white.svg description: name: thanos-endpoint colorIcon: assets/img/integrations/thanos-operator/components/thanos-endpoint/icons/color/thanos-endpoint-color.svg whiteIcon: assets/img/integrations/thanos-operator/components/thanos-endpoint/icons/white/thanos-endpoint-white.svg description: name: thanos-peer colorIcon: assets/img/integrations/thanos-operator/components/thanos-peer/icons/color/thanos-peer-color.svg whiteIcon: assets/img/integrations/thanos-operator/components/thanos-peer/icons/white/thanos-peer-white.svg description: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations