cwielenb/CNCF-Dataset huggingface dataset:
Project: Kyverno (Provisioning / Security & Compliance)
File: kyverno_oci_push.md

Push policie(s) that are included in an OCI image to OCI registry. Push policie(s) that are included in an OCI image to OCI registry. NOTE: This is an experimental command, use `KYVERNO_EXPERIMENTAL=true` to enable it. For more information visit https://kyverno.io/docs/kyverno-cli/#pushing ``` kyverno oci push [dir or file] [flags] ``` ``` kyverno oci push ./policy.yaml -i <imgref> kyverno oci push . -i <imgref> ``` ``` -h, --help help for push -i, --image string image reference to push to or pull from ``` ``` --adddirheader If true, adds the file directory to the header of the log messages --alsologtostderr log to standard error as well as files (no effect when -logtostderr=true) --logbacktraceat traceLocation when logging hits line file:N, emit a stack trace (default :0) --log_dir string If non-empty, write log files in this directory (no effect when -logtostderr=true) --log_file string If non-empty, use this log file (no effect when -logtostderr=true) --logfilemax_size uint Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800) --logtostderr log to standard error instead of files (default true) --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true) --skip_headers If true, avoid header prefixes in the log messages --skiplogheaders If true, avoid headers when opening log files (no effect when -logtostderr=true) --stderrthreshold severity logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2) -v, --v Level number for the log level verbosity --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging ``` - Pulls/pushes images that include policie(s) from/to OCI registries.
Project: KICS (Provisioning / Security & Compliance)
File: 17e52ca3-ddd0-4610-9d56-ce107442e110.md

title: HPA Targets Invalid Object hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 17e52ca3-ddd0-4610-9d56-ce107442e110 Query name: HPA Targets Invalid Object Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Availability URL: The Horizontal Pod Autoscaler must target a valid object<br> ```tf title="Positive test num. 1 - tf file" hl_lines="49 15" resource "kuberneteshorizontalpod_autoscaler" "example" { metadata { name = "test" } spec { min_replicas = 50 max_replicas = 100 scaletargetref { kind = "Deployment" name = "MyApp" } metric { type = "External" external { metric { name = "latency" selector { match_labels = { lb_name = "test" } } } target { type = "Value" value = "100" } } } } } resource "kuberneteshorizontalpod_autoscaler" "example2" { metadata { name = "test" } spec { min_replicas = 50 max_replicas = 100 scaletargetref { kind = "Deployment" name = "MyApp" } metric { type = "Object" object { target { type = "Value" value = "100" } } } } } ``` ```tf title="Negative test num. 1 - tf file" resource "kuberneteshorizontalpod_autoscaler" "example5" { metadata { name = "test" } spec { min_replicas = 50 max_replicas = 100 scaletargetref { kind = "Deployment" name = "MyApp" } metric { type = "Object" object { metric { name = "latency" } described_object { name = "main-route" api_version = "networking.k8s.io/v1beta1" kind = "Ingress" } target { type = "Value" value = "100" } } } } } ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-machine-os-apply.1.md

% podman-machine-os-apply 1 podman\-machine\-os\-apply - Apply an OCI image to a Podman Machine's OS podman machine os apply [options] image [vm] Apply machine OS changes from an OCI image. VM's that use OS's that use rpm-ostreee have the capability to rebase itself from the content of an OCI image. `podman machine image apply` takes an OCI image with container native ostree functionality and rebases itself on that image. By default, Podman machines on Mac and Linux use an rpm-ostree based distribution (Fedora CoreOS). For more information, see the . The default machine name is `podman-machine-default`. If a machine name is not specified as an argument, then the OS changes will be applied to `podman-machine-default`. Print usage statement. Restart VM after applying changes. Update the default Podman machine to the specified bootable OCI image. ``` $ podman machine os apply quay.io/podman_next ``` Update the specified Podman machine to the specified bootable OCI image. ``` $ podman machine os apply quay.io/podman_next podman-machine-default ``` , , February 2023, Originally compiled by Ashley Cui <acui@redhat.com>
Project: VMClarity (Provisioning / Security & Compliance)
File: BUG_REPORT.md

name: Bug Report about: Report a bug to help us improve title: '' labels: '' assignees: '' Please provide a description of the problem. Please describe what you expected would happen. Please describe what happened instead. Please provide the version number where this issue was encountered. First step Second step etc. <!-- TODO: Update the link below to point to your project's contributing guidelines --> [ ] I have verified this does not duplicate an existing issue
Project: kpt (Provisioning / Automation & Configuration)
File: 04-developing-in-Starlark.md

You can write the function in Starlark script. ?> Starlark SDK is in experimental stage. [Starlark] is a python-like language designed for use in configuration files that has several desirable properties: deterministic evaluation hermetic execution simplicity. Current Starlark SDK is driven by [`gcr.io/kpt-fn/starlark:v0.4`] which contains the interpreter and accepts a `StarlarkRun` object as its `FunctionConfig`. You should place your starlark script in the `source` field of the `StarlarkRun` object. Let's write a starlark function which add annotation "managed-by=kpt" only to `Deployment` resources. ```shell kpt pkg get https://github.com/GoogleContainerTools/kpt-functions-sdk.git/starlark/get-started@master set-annotation cd set-annotation ``` ```yaml apiVersion: fn.kpt.dev/v1alpha1 kind: StarlarkRun metadata: name: set-annotation source: | for resource in ctx.resource_list["items"]: if resource.get("kind") == "Deployment": resource["managed-by"] = "kpt" ``` In the `source` field, the `ResourceList` from STDIN is loaded to `ctx.resource_list` as a dict. You can manipulate KRM resource as operating on a dict. Run the starlark script via `kpt` ```shell kpt fn eval ./data --image starlark:v0.4 --fn-config starlark-fn-config.yaml cat ./data/resources.yaml | grep annotations -A1 -B5 ``` ?> Refer to the for details on how to use this function.
Project: kpt (Provisioning / Automation & Configuration)
File: 04-arm-build.md

Author(s): Mike Borozdin, @mikebz Approver: Mengqi, Sunil More people are getting Apple M1 machines. The current docker images for functions do not work. Here is an example: https://github.com/GoogleContainerTools/kpt/issues/2874 While it's not a problem for CI/CD pipelines where architecture is mostly amd64 for client development purposes the users are stuck. Building arm64 and amd64 multi platform images is possible: https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/ but it has it's caveats. The build is done in a builder which needs to be created: https://docs.docker.com/engine/reference/commandline/buildx_create/ The caveat is that the multi platform images do not load into docker images: https://github.com/docker/buildx/blob/master/docs/reference/buildx_build.md#-load-the-single-platform-build-result-to-docker-imagesload Right now the build pipeline has several steps: 1) build 2) tag 3) push In different scenarios only the first two steps are executed. If we switch to `buildx` we will need to build/tag/push in one step. Locally developers might want to build and tag images locally. However if we make the changes needed to the shell scripts that produce the images all that the users of docker images will need to do is just update to the next version of the function image. Docker promises to use the right architecture automatically. The user guide for using the new images should not change. People using amd64 systems (Linux or Mac) can continue using the same systems. People using arm64 systems can already get the arm64 kpt binary and will update their pipelines to the next version of functions. The functions should select the right architecture to run. Please list any open questions here in the following format: An alternative to using a multi architecture images is to build a special image for each platform and then tag them differently. The benefits of this are: users can select the right architecture in their Kptfile or imperability invoking the right function image. The problem is that most of the time CI/CD systems are amd64 linux and the arm64 is primarily for the convenience of client systems. The users most likely do not want to change their hydration pipeline definition from client to CI/CD systems. NOTE: we have done a test on how the images look in the container registry. buildx builds two images and the individual images are not any bigger. Links and description of the approach, the pros and cons identified during the design.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: sbom.md

Generate SBOMs (Software Bills Of Materials) for the output image by scanning the working container and build contexts using the named combination of scanner image, scanner commands, and merge strategy. Must be specified with one or more of --sbom-image-output, --sbom-image-purl-output, --sbom-output, and --sbom-purl-output. Recognized presets, and the set of options which they equate to: "syft", "syft-cyclonedx": --sbom-scanner-image=ghcr.io/anchore/syft --sbom-scanner-command="/syft scan -q dir:{ROOTFS} --output cyclonedx-json={OUTPUT}" --sbom-scanner-command="/syft scan -q dir:{CONTEXT} --output cyclonedx-json={OUTPUT}" --sbom-merge-strategy=merge-cyclonedx-by-component-name-and-version "syft-spdx": --sbom-scanner-image=ghcr.io/anchore/syft --sbom-scanner-command="/syft scan -q dir:{ROOTFS} --output spdx-json={OUTPUT}" --sbom-scanner-command="/syft scan -q dir:{CONTEXT} --output spdx-json={OUTPUT}" --sbom-merge-strategy=merge-spdx-by-package-name-and-versioninfo "trivy", "trivy-cyclonedx": --sbom-scanner-image=ghcr.io/aquasecurity/trivy --sbom-scanner-command="trivy filesystem -q {ROOTFS} --format cyclonedx --output {OUTPUT}" --sbom-scanner-command="trivy filesystem -q {CONTEXT} --format cyclonedx --output {OUTPUT}" --sbom-merge-strategy=merge-cyclonedx-by-component-name-and-version "trivy-spdx": --sbom-scanner-image=ghcr.io/aquasecurity/trivy --sbom-scanner-command="trivy filesystem -q {ROOTFS} --format spdx-json --output {OUTPUT}" --sbom-scanner-command="trivy filesystem -q {CONTEXT} --format spdx-json --output {OUTPUT}" --sbom-merge-strategy=merge-spdx-by-package-name-and-versioninfo
Project: YugabyteDB (App Definition and Development / Database)
File: compare-dp-results.md

title: compare-dp-results linkTitle: compare-dp-results headerTitle: Output from running docomparedpresults.sql on dpresults description: Output from running docomparedpresults.sql on dpresults. menu: v2.18: identifier: compare-dp-results parent: normal-distribution-analysis-reports weight: 30 type: docs ``` bucket | pr n equal | pr mins equal | pr maxs equal | cd n equal | cd mins equal | cd maxs equal --++-+-++-+- 1 | true | true | true | true | true | true 2 | true | true | true | true | true | true 3 | true | true | true | true | true | true 4 | true | true | true | true | true | true 5 | true | true | true | true | true | true 6 | true | true | true | true | true | true 7 | true | true | true | true | true | true 8 | true | true | true | true | true | true 9 | true | true | true | true | true | true 10 | true | true | true | true | true | true 11 | true | true | true | true | true | true 12 | true | true | true | true | true | true 13 | true | true | true | true | true | true 14 | true | true | true | true | true | true 15 | true | true | true | true | true | true 16 | true | true | true | true | true | true 17 | true | true | true | true | true | true 18 | true | true | true | true | true | true 19 | true | true | true | true | true | true 20 | true | true | true | true | true | true ```
Project: Meshery (Provisioning / Automation & Configuration)
File: terraform.md

layout: integration title: Terraform subtitle: Collaborative and visual infrastructure as code for Terraform image: /assets/img/integrations/terraform/icons/color/terraform-color.svg permalink: extensibility/integrations/terraform docURL: https://docs.meshery.io/extensibility/integrations/terraform description: integrations-category: Provisioning integrations-subcategory: Automation & Configuration registrant: Artifact Hub components: name: workspace colorIcon: assets/img/integrations/terraform/components/workspace/icons/color/workspace-color.svg whiteIcon: assets/img/integrations/terraform/components/workspace/icons/white/workspace-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
Project: StarRocks (App Definition and Development / Database)
File: multi_distinct_count.md

displayed_sidebar: "English" Returns the total number of rows of the `expr`, equivalent to count(distinct expr). ```Haskell multidistinctcount(expr) ``` `expr`: the column or expression based on which `multidistinctcount()` is performed. If `expr` is a column name, the column can be of any data type. Returns a numeric value. If no rows can be found, 0 is returned. This function ignores NULL values. Suppose there is a table named `test`. Query the category and supplier of each order by `id`. ```Plain select * from test order by id; ++-+-++ | id | country | category | supplier | ++-+-++ | 1001 | US | A | supplier_1 | | 1002 | Thailand | A | supplier_2 | | 1003 | Turkey | B | supplier_3 | | 1004 | US | A | supplier_2 | | 1005 | China | C | supplier_4 | | 1006 | Japan | D | supplier_3 | | 1007 | Japan | NULL | supplier_5 | ++-+-++ ``` Example 1: Count the number of distinct values in the `category` column. ```Plain select multidistinctcount(category) from test; +--+ | multidistinctcount(category) | +--+ | 4 | +--+ ``` Example 2: Count the number of distinct values in the `supplier` column. ```Plain select multidistinctcount(supplier) from test; +--+ | multidistinctcount(supplier) | +--+ | 5 | +--+ ```
Project: Teleport (Provisioning / Security & Compliance)
File: 0111-support-connection-testers-with-per-session-mfa.md

authors: Lisa Kim (lisa@goteleport.com) state: implemented Add a field to request. As mentioned in the related issue, when a role or config has enabled the field, users were not able to proceed testing connections to their newly added resource in the web UI, because we didn't implement a way for users to provide and authenticate their MFA device. The feature requires establishing a brief session with the target resource which requires generating a short lived user certificate. If the `requiremfasession` is enabled, the certs field must be set. Upon testing, the field could potentially be set to any string value (and still be qualified as verified), so it's important how we set this field. By accepting a , the request will be responsible for validating the response (if provided), and upon success will capture the verified MFA device ID which will be used to set the `mfaVerified` field. If validation failed, the request will return an authentication error. In the web UI, when a user clicks on the `test connection` button, we will make a call to this existing endpoint that checks whether MFA is required to access the specified resource. Then depending on the response: If MFA wasn't required, proceed to make a request to test connection as we did before If MFA is required, we will ask the user to enter their MFA credentials, take the response and send it off with the request to test connection
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_resourcemanager_folder.md

+++ title = "googleresourcemanagerfolder resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleresourcemanagerfolder" identifier = "inspec/resources/gcp/googleresourcemanagerfolder.md googleresourcemanagerfolder resource" parent = "inspec/resources/gcp" +++ A `googleresourcemanagerfolder` is used to test a Google Folder resource ```ruby describe.one do googleresourcemanagerfolders(parent: 'organizations/12345').names.each do |name| describe googleresourcemanagerfolder(name: name) do it { should exist } its('display_name') { should eq 'inspec-gcp-folder' } end end end ``` Properties that can be accessed from the `googleresourcemanagerfolder` resource: `name` : The resource name of the Folder. Its format is folders/{folder_id}, for example: "folders/1234". `lifecycle_state` : The lifecycle state of the folder. Updates to the lifecycleState must be performed via folders.delete and folders.undelete. Possible values: LIFECYCLESTATEUNSPECIFIED ACTIVE DELETE_REQUESTED `create_time` : Time of creation `parent` : The Folders parent's resource name. Updates to the folder's parent must be performed via folders.move. `display_name` : The folders display name. A folders display name must be unique amongst its siblings, e.g. no two folders with the same parent can share the same display name. The display name must start and end with a letter or digit, may contain letters, digits, spaces, hyphens and underscores and can be no longer than 30 characters. This is captured by the regular expression: `?`. Ensure the is enabled for the current project.
Project: ShardingSphere (App Definition and Development / Database)
File: start-migration.en.md

+++ title = "START MIGRATION" weight = 14 +++ The `START MIGRATION` syntax is used to start migration process. {{< tabs >}} {{% tab name="Grammar" %}} ```sql StartMigration ::= 'START' 'MIGRATION' migrationJobId migrationJobId ::= string ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} `migrationJobId` needs to be obtained through syntax query Start migration process ```sql START MIGRATION 'j010180026753ef0e25d3932d94d1673ba551'; ``` `START`, `MIGRATION`
Project: Meshery (Provisioning / Automation & Configuration)
File: bfe.md

layout: integration title: BFE subtitle: Collaborative and visual infrastructure as code for BFE image: /assets/img/integrations/bfe/icons/color/bfe-color.svg permalink: extensibility/integrations/bfe docURL: https://docs.meshery.io/extensibility/integrations/bfe description: integrations-category: Cloud Native Network integrations-subcategory: Service Proxy registrant: Artifact Hub components: featureList: [ "BFE has a builtin plugin framework that makes it possible to develop new features rapidly by writing plugins.", "BFE is designed to provide every tenant a dedicated share of the instance. Each tenant&ldquos configuration is isolated and remains invisible to other tenants", "BFE provides an advanced domain-specific language to describe routing rules which are easy to understand and maintain." ] 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: Crux (App Definition and Development / Database)
File: design_in_practice_rich_hickey.md

Its about writing out your thoughts. Having the problem right in your face all the time. Writing as part of thinking. Add a Glossary to your project Asking the right questions is a good skill. Where are you at ? Where are you going ? What do you know ? What do you need to know? The Socratic method | | Understanding | Activity | | | | | | Status - to stand | What do you know? | Where are you at? | | Agenda - to be done | What do you need to know? | Where are you going? | non monotonic backtracking - after you have learned something, you might retract and go to an earlier phase Deciding: Scoping is always possible. Rejecting is always possible. Describe What do you know? - something is off/missing What do you need to know? - the extent of it Where are you at? - observing, listening Where are you going? initial title of the story write down a description in the top story Description 1 summary paragraph situation you find yourself in not the reasons for the problem or possible causes Diagnose bug/feature - both of them might need a different approach feature We dont have feature X! is not a valid Problem statement. Go from feature problem The feature is then 1 possible answer. Open set of solutions (this is where design happens). What do you know? - the symptoms/context What do you need to know? - the cause Where are you at? - good description (one above), evidence Ware are you going? - applying logic and experimentation Delimit the problem you are going to solve next as multiple problems might have appeared during the diagnose phase What do you know ? - the problem What do yo need to know ? - How to state it succinctly. Its scope. Where are you at ? - having done the diagnosis (one above) Where are you going ? - Writing the problem statement. Succinct statement of unmet user objectives and causes Story title might change Direction Where are you at? - Description and Problem statement Where are you going? - The approaches Enumerating use cases Not how, but intentions and objectives (of the user Making a strategy DM (Decision Matrix) A1 - Problem statement First column - criteria Other columns - approaches Cells should be descriptive - not just yes/no, good/bad etc. Avoid subjective statements Subjectivity is ONLY added via colors Determining the scope Its not shopping (just find different approaches). Its about going through the exercise of examining how the approaches differ from each other (via the criteria) Design You cant start here. All of the above have to come first. Where are you at? use case and strategy DM (from above) What do you know ? - The problem and the direction we are going to take (previous phases) What do you need to know ? implementation approaches the best of these What matters in deciding. Dev - only now
Project: Beam (App Definition and Development / Streaming & Messaging)
File: samza-runner.md

title: "Samza Runner Roadmap" <!-- 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. --> This roadmap is in progress. In the meantime, here are available resources: - Issues: