cwielenb/CNCF-Dataset huggingface dataset:
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_attach.md

title: "Command - devspace attach" sidebar_label: devspace attach Attaches to a container ``` devspace attach [flags] ``` ``` Attaches to a running container devspace attach devspace attach --pick # Select pod to enter devspace attach -c my-container devspace attach -n my-namespace ``` ``` -c, --container string Container name within pod where to execute command -h, --help help for attach --image string Image is the config name of an image to select in the devspace config (e.g. 'default'), it is NOT a docker image like myuser/myimage --image-selector string The image to search a pod for (e.g. nginx, nginx:latest, ${runtime.images.app}, nginx:${runtime.images.app.tag}) -l, --label-selector string Comma separated key=value selector list (e.g. release=test) --pick Select a pod (default true) --pod string Pod to open a shell to ``` ``` --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: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-aux-cache-clear-cache.md

layout: global title: CLEAR CACHE displayTitle: CLEAR CACHE license: | 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. `CLEAR CACHE` removes the entries and associated data from the in-memory and/or on-disk cache for all cached tables and views. ```sql CLEAR CACHE ``` ```sql CLEAR CACHE; ```
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: builder_account.md

+++ title = "Create an Account" description = "Setting up Chef Habitat Builder in the Cloud and on your workstation" gh_repo = "habitat" [menu] [menu.habitat] title = "Create an Account" identifier = "habitat/builder/builder-account Builder Account" parent = "habitat/builder" weight = 20 +++ Whether you are looking to leverage the SaaS or on-prem version of Chef Habitat Builder, you will need to create an account on the SaaS version of Chef Habitat Builder. After you have then downloaded the version, you will then sync the two accounts. You need to set a few things up before you can get started with Chef Habitat Builder: Download and install the A Chef Habitat Builder automatically creates your account the first time you sign in using the GitHub authentication process. You'll also need to authorize the Chef Habitat Builder application in Github. Head over to the Chef Habitat Builder sign-in page at to get started. To sign in with an existing GitHub account, select Sign in with GitHub If you need to set up a GitHub account, select the Sign up here link Signing in with your GitHub account and authorizing the Chef Habitat Builder application the first time you sign in grants you access to the Chef Habitat Builder platform. Once you've completed signing in and authorizing Chef Habitat Builder, you'll arrive at the 'My Origins' view.
Project: Artifact Hub (App Definition and Development / Application Definition & Image Build)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: new feature assignees: '' Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here.
Project: StarRocks (App Definition and Development / Database)
File: utc_timestamp.md

displayed_sidebar: "English" Returns the current UTC date and time as a value in 'YYYY-MM-DD HH:MM:SS' or 'YYYYMMDDHHMMSS' format depending on the usage of the function, for example, in a string or numeric context. ```Haskell DATETIME UTC_TIMESTAMP() ``` ```Plain Text MySQL > select utctimestamp(),utctimestamp() + 1; +++ | utctimestamp() | utctimestamp() + 1 | +++ | 2019-07-10 12:31:18 | 20190710123119 | +++ ``` `utc_timestamp() + N` means adding `N` seconds to the current time. UTC_TIMESTAMP,UTC,TIMESTAMP
Project: Gradle Build Tool (App Definition and Development / Application Definition & Image Build)
File: 0003-avoid-introducing-Groovy-types-to-public-api.md

2024-01-12 Gradle's public API requires equal access from all JVM-based languages. Kotlin, Groovy, Java, and other JVM-based languages should be able to use the Gradle API without relying on another language's standard library. Historically, Gradle has shipped with some Groovy types in very prominent APIs. This required the Kotlin DSL to add special integration to work with Groovy closures. This has also forced plugins written in languages other than Groovy to use Groovy types for some APIs. When the Kotlin DSL was introduced, we made an effort to add non-Groovy equivalents for all APIs. This has been mostly done, but there remain a few holdouts (fixing these is out of scope). To keep the Groovy DSL ergonomic, we generate methods as necessary from the non-Groovy equivalents. Doing this provides the following specific benefits: Reduce the API surface - We no longer need to maintain two methods. Consistency - All languages have consistent access to the same APIs and ergonomics in the DSL. Reduce the size of the Gradle distribution - We no longer need to carry multiple standard libraries for different languages. We do not introduce new public API methods that include Groovy types in their signatures. Existing Groovy methods will not be removed immediately. ACCEPTED If we would have used `Closure`, we must instead use `Action<T>`, `Spec<T>`, `Callable<T>`, or `Transformer<OUT, IN>`. We need to ensure all APIs that are exposed in the Groovy DSL go through runtime decoration. Runtime decoration mixes in methods that use Groovy Closures to maintain consistent behavior in Groovy DSL. Decoration is performed on objects instantiated by `ObjectFactory`.
Project: KICS (Provisioning / Security & Compliance)
File: 69e7c320-b65d-41bb-be02-d63ecc0bcc9d.md

title: ECR Repository Without Policy hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 69e7c320-b65d-41bb-be02-d63ecc0bcc9d Query name: ECR Repository Without Policy Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: ECR Repository should have Policies attached to it<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsecrrepository" "foo" { name = "bar" } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "awsecrrepository" "foo2" { name = "bar" } resource "awsecrrepository_policy" "foopolicy" { repository = awsecrrepository.foo.name policy = <<EOF { "Version": "2008-10-17", "Statement": [ { "Sid": "new policy", "Effect": "Allow", "Principal": "*", "Action": [ "ecr:GetDownloadUrlForLayer", "ecr:BatchGetImage", "ecr:BatchCheckLayerAvailability", "ecr:PutImage", "ecr:InitiateLayerUpload", "ecr:UploadLayerPart", "ecr:CompleteLayerUpload", "ecr:DescribeRepositories", "ecr:GetRepositoryPolicy", "ecr:ListImages", "ecr:DeleteRepository", "ecr:BatchDeleteImage", "ecr:SetRepositoryPolicy", "ecr:DeleteRepositoryPolicy" ] } ] } EOF } ``` ```tf title="Negative test num. 1 - tf file" resource "awsecrrepository" "foo" { name = "bar" } resource "awsecrrepository_policy" "foopolicy" { repository = awsecrrepository.foo.name policy = <<EOF { "Version": "2008-10-17", "Statement": [ { "Sid": "new policy", "Effect": "Allow", "Principal": "*", "Action": [ "ecr:GetDownloadUrlForLayer", "ecr:BatchGetImage", "ecr:BatchCheckLayerAvailability", "ecr:PutImage", "ecr:InitiateLayerUpload", "ecr:UploadLayerPart", "ecr:CompleteLayerUpload", "ecr:DescribeRepositories", "ecr:GetRepositoryPolicy", "ecr:ListImages", "ecr:DeleteRepository", "ecr:BatchDeleteImage", "ecr:SetRepositoryPolicy", "ecr:DeleteRepositoryPolicy" ] } ] } EOF } ```
Project: SPIRE (Provisioning / Key Management)
File: plugin_agent_nodeattestor_x509pop.md

Must be used in conjunction with the server-side x509pop plugin The `x509pop` plugin provides attestation data for a node that has been provisioned with an x509 identity through an out-of-band mechanism and responds to a signature based proof-of-possession challenge issued by the server plugin. The SPIFFE ID produced by the server-side `x509pop` plugin is based on the certificate fingerprint, where the fingerprint is defined as the SHA1 hash of the ASN.1 DER encoding of the identity certificate. The SPIFFE ID has the form: ```xml spiffe://<trust_domain>/spire/agent/x509pop/<fingerprint> ``` | Configuration | Description | Default | |-|-|| | `privatekeypath` | The path to the private key on disk (PEM encoded PKCS1 or PKCS8) | | | `certificate_path` | The path to the certificate bundle on disk. The file must contain one or more PEM blocks, starting with the identity certificate followed by any intermediate certificates necessary for chain-of-trust validation. The identity certificate must contain the `digitalSignature` in the | | | `intermediatespath` | Optional. The path to a chain of intermediate certificates on disk. The file must contain one or more PEM blocks, corresponding to intermediate certificates necessary for chain-of-trust validation. If the file pointed by `certificatepath` contains more than one certificate, this chain of certificates will be appended to it. | | A sample configuration: ```hcl NodeAttestor "x509pop" { plugin_data { privatekeypath = "/opt/spire/conf/agent/agent.key.pem" certificate_path = "/opt/spire/conf/agent/agent.crt.pem" } } ```
Project: ClickHouse (App Definition and Development / Database)
File: v20.7.3.7-stable.md

Backported in : Added Redis requirepass authorization. (). Backported in : Allow using multi-volume storage configuration in storage Distributed. (). Backported in : Fixes /replicas_status endpoint response status code when verbose=1. (). Backported in : Fix GRANT ALL statement when executed on a non-global level. (). Backported in : Fix pointInPolygon with const 2d array as polygon. (). Backported in : Fix crash when INERT INTO Kafka engine table from an empty result set with a subquery. ... (). Backported in : Fix segfault in `clickhouse-odbc-bridge` during schema fetch from some external sources. This PR fixes . (). Backported in : Fix crash during `ALTER` query for table which was created `AS table_function`. Fixes . (). Backported in : Stop query execution if exception happened in `PipelineExecutor` itself. This could prevent rare possible query hung. (). Backported in : Stop query execution if exception happened in `PipelineExecutor` itself. This could prevent rare possible query hung. Continuation of . (). Backported in : Fix bug which leads to wrong merges assignment if table has partitions with a single part. (). Backported in : Check for array size overflow in `topK` aggregate function. Without this check the user may send a query with carefully crafter parameters that will lead to server crash. This closes . (). Backported in : Fix rare segfaults in functions with combinator -Resample, which could appear in result of overflow with very large parameters. (). Backported in : Cleanup data directory after Zookeeper exceptions during CreateQuery for StorageReplicatedMergeTree Engine. (). Backported in : Fix wrong Decimal multiplication result caused wrong decimal scale of result column. (). Backported in : Fix bug when `ALTER UPDATE` mutation with Nullable column in assignment expression and constant value (like `UPDATE x = 42`) leads to incorrect value in column or segfault. Fixes , . (). Backported in : Fixed missed default database name in metadata of materialized view when executing `ALTER ... MODIFY QUERY`. (). Backported in : Fix SIGSEGV for an attempt to INSERT into StorageFile(fd). (). Backported in : Fix the issue when some invocations of `extractAllGroups` function may trigger "Memory limit exceeded" error. This fixes . ().
Project: Shifu (Provisioning / Automation & Configuration)
File: develop-on-windows.md

Welcome developers! This guide will help you on setting up development environment for `Shifu` on `Windows` ``` Windows 11 Pro ``` Please submit an to GitHub if you are having issue following this guide/you have noticed anything wrong with this guide. From , install `wsl` with the following command in `administrator` PowerShell: ```PowerShell wsl --install ``` In Start Menu, enter `Ubuntu` and click on the `Ubuntu` app: After that follow the prompt to setup a user with password. Use the following command to clone *Shifu*: ```bash git clone https://github.com/Edgenesis/shifu.git ``` Follow the official from Docker official website. the installation exe and install. After installation, use `F1` key to open a new WSL window: Then, use "File --> Open Folder" to open *Shifu* directory: A prompt should show up automatically to open this project in remote container: Click on that, VSCode should open your project in remote container. Your development environment is ready! *Note*: If you use `Visual Studio Code` with `Dev Container` you can skip all below environment setup steps. From , download and install go using the following command: ```bash $ wget https://go.dev/dl/go1.22.0.linux-amd64.tar.gz $ rm -rf /usr/local/go && tar -C /usr/local -xzf go1.22.0.linux-amd64.tar.gz $ echo "export PATH=$PATH:/usr/local/go/bin" >> $HOME/.profile ``` from , install with: ```sh curl -Lo ./kind https://kind.sigs.k8s.io/dl/v0.16.0/kind-linux-amd64 \ && chmod +x ./kind \ && mv ./kind /usr/local/bin/kind ``` from , install with: ```bash $ curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl" $ sudo install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl ``` from , install with: ```sh curl -L -o kubebuilder https://go.kubebuilder.io/dl/latest/$(go env GOOS)/$(go env GOARCH) chmod +x kubebuilder && mv kubebuilder /usr/local/bin/ ``` Navigate to `shifu`'s directory, issue: ```sh GO111MODULE=on go mod download ``` *(Optional)* If you are having issue download dependencies, add a proxy by using: ```sh GOPROXY=https://goproxy.cn,direct GO111MODULE=on go mod download ``` Follow our and start building `Shifu`.
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: harbor-trivy.md

Harbor-Trivy is configured via specific environment variables and does not use a config file. `SCANNERLOGLEVEL` The logging level this service should use. The default value is `error`. This can be set to `debug` to enable very verbose logging. `SCANNERSTOREREDIS_URL` This value tells harbor-trivy how to connect to its Redis store. The default value is `redis://harbor-redis:6379/4`. `SCANNERJOBQUEUEREDISURL` This value tells harbor-trivy how to connect to its Redis store. The default value is `redis://harbor-redis:6379/4`. `SCANNERTRIVYVULN_TYPE` This value tells harbor-trivy what types of vulnerabilities it should be searching for. The default value is `os,library`
Project: Beam (App Definition and Development / Streaming & Messaging)
File: postcommits-guides.md

title: 'Post-commit tests processes guides' <!-- 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. --> These guides provide steps for common post-commit test failure tasks. To find the proper person to triage a test failure, you can use these suggestions: If you can triage it yourself, go for it. Look at the GitHub blame for the files with problematic code. Ask in the . Write to the dev list: dev@beam.apache.org Rolling back is usually the fastest way to fix a failing test. However it is is often inconvenient for the original author. To help the author fix the issue, follow these steps when you rollback someone's change. Rollback the PR (or individual commit of the PR). The rollback PR should be green except in rare cases. Create a GitHub issue that contains the following information: the reason for the rollback a link to the test failure's GitHub issue triage information any other relevant details Assign the new GitHub issue to the original PR author. Consider re-opening the GitHub issue associated with the original PR (if there is one). Send a notification email with information about the rollback, links to the original PR and the rollback PR, and the reasons for the rollback to: dev@beam.apache.org the original PR author and the committer of the PR Close the test failure GitHub issue. Your work is done here! If a test fails, our first priority is to rollback the problematic code and fix the issue. However, if both: rollback and fix will take awhile to implement, it is safer to temporarily disable the test until the fix is ready. Use caution when deciding to disable a test. When tests are disabled, contributors are no longer developing on top of fully tested code. If you decide to disable a test, use the following guidelines: Notify the dev@beam.apache.org mailing list. Describe the problem and let everyone know which test you are disabling. Implement the fix and get the test back online as soon as possible. While the test is disabled, contributors should not push code to the failing test's coverage area. The code area is not properly tested until you fix the test.
Project: CFEngine (Provisioning / Automation & Configuration)
File: README.md

==================== Inform Logging Tests ==================== These tests turn the model upside down a bit to make things easier. Two bits are needed at the top of each .cf test file: ```cf3 body file control { inputs => { "$(sys.policyentrydirname)/../common.cf.sub" }; } bundle common testcase { vars: "filename" string => "$(this.promise_filename)"; } ``` This is the boiler-plate to drive the tests. The framework automatically cleans up `$(G.testfile)` and `$(G.testdir)`. For the simplest case you can just include a `main` bundle to do the operation you want to perform. ```cf3 bundle agent main { files: "$(G.testfile)" create => "true"; } ``` And when the test is run it will generate a `<test.cf>.actual` and check it against a `<test.cf>.expected`. There are temporary files created during the test involving the results. If the test fails, these files will be kept, if the test passes, they will be removed. The little framework also supports a `setup` and `teardown` optional bundle for things you might need in that regard. Next to common.cf.sub there is a shell script called accept-actual.sh which will mv the .actual files to .expected and add them via `git`.
Project: KICS (Provisioning / Security & Compliance)
File: 2e275f16-b627-4d3f-ae73-a6153a23ae8f.md

title: Parameter JSON Reference Does Not Exists (v3) hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2e275f16-b627-4d3f-ae73-a6153a23ae8f Query name: Parameter JSON Reference Does Not Exists (v3) Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Structure and Semantics URL: Parameter reference should exists on components field<br> ```json title="Positive test num. 1 - json file" hl_lines="19" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "$ref": "#/components/schemas/Success" } }, "parameters": [ { "$ref": "#/components/parameters/wrongParameter" } ] } } }, "components": { "parameters": { "limitParam": { "name": "limit", "in": "query", "description": "max records to return", "required": true, "schema": { "type": "integer" } } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="14" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': "$ref": "#/components/schemas/Success" parameters: "$ref": "#/components/parameters/wrongParameter" components: parameters: limitParam: name: limit in: query description: max records to return required: true schema: type: integer ``` ```json title="Negative test num. 1 - json file" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "$ref": "#/components/schemas/Success" } }, "parameters": [ { "$ref": "#/components/parameters/limitParam" } ] } } }, "components": { "parameters": { "limitParam": { "name": "limit", "in": "query", "description": "max records to return", "required": true, "schema": { "type": "integer" } } } } } ``` ```yaml title="Negative test num. 2 - yaml file" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': "$ref": "#/components/schemas/Success" parameters: "$ref": "#/components/parameters/limitParam" components: parameters: limitParam: name: limit in: query description: max records to return required: true schema: type: integer ```