cwielenb/CNCF-Dataset huggingface dataset:
Project: secureCodeBox (Provisioning / Security & Compliance)
File: cascading-rule.md

title: "CascadingRule" sidebar_position: 7 CascadingRules are Custom Resource Definitions (CRD's) used to define how scans can be started automatically based on the results of previous scans. This lets you run large exploratory scans and automatically start more in depth scans on the targets found by the initial scans. You can find a more concrete example on how this works in the . The `matches.anyOf` fields consists of a list of objects / hashes. These objects are compared using a partial deep comparison, meaning that all field of the object must exactly match the finding. If multiple anyOf rules are specified at least one must match the finding. If multiple rules are matching, the CascadingRule will still only create one scan. Configures additional labels/annotations/ added to each subsequent scan (child). These labels/annotations overwrite any existing labels/annotations. You can use a simple templating scheme to gather details about the parent scan or finding (use `{{variable}}`, see example below). The following variables are available: The parent (e.g. `metadata.name`). The related (e.g. `category`, `attributes.hostname`). Custom variables (prepended with `$.`): `hostOrIP`: `finding.hostname || finding.ip_address` If you need more custom variables, please don't hesitate to ! Contains the which is supposed to be started of the a finding matches the CascadingRule. The `scanType`, `parameters`, values specified in `env` variables, as well as the `command` and `env` of any included `initContainers`, can use templates to refer to fields of the finding the CascadingRule has been applied to. The finding is passed in directly into the mustache templating call, so that fields of the findings can be directly referenced. E.g. the location can be directly referred to by: `{{location}}`. For convenience a helper object has been added to the mustache call under the `$` shorthand. This helper object has the following attributes: `$.hostOrIP` returns either the hostname (if available) or the hostname of the current finding. ```yaml apiVersion: "cascading.securecodebox.io/v1" kind: CascadingRule metadata: name: "zap-http" labels: securecodebox.io/invasive: non-invasive securecodebox.io/intensive: medium spec: matches: anyOf: category: "Open Port" attributes: service: http state: open category: "Open Port" attributes: service: https state: open scanLabels: mynewlabel: {{ metadata.name }} scanAnnotations: defectdojo.securecodebox.io/product-name: "{{$.hostOrIP}}" defectdojo.securecodebox.io/product-type-name: "{{metadata.labels.organization}}" defectdojo.securecodebox.io/engagement-name: "{{metadata.name}}" mynewannotation: "{{category}}" scanSpec: scanType: "zap-baseline" parameters: ["-t", "{{attributes.service}}://{{$.hostOrIP}}"] ```
Project: KubeArmor (Provisioning / Security & Compliance)
File: admin-tools.md

```sh kubectl exec -it dvwa-web-566855bc5b-4j4vl -- bash root@dvwa-web-566855bc5b-4j4vl:/var/www/html# kubectl bash: /usr/bin/kubectl: Permission denied root@dvwa-web-566855bc5b-4j4vl:/var/www/html# ``` ``` { "ATags": null, "Action": "Block", "ClusterName": "aditya", "ContainerID": "32015ebeea9e1f4d4e7dbf6608c010ef2b34c48f1af11a5c6f0ea2fd27c6ba6c", "ContainerImage": "docker.io/cytopia/dvwa:php-8.1@sha256:f7a9d03b1dfcec55757cc39ca2470bdec1618b11c4a51052bb4f5f5e7d78ca39", "ContainerName": "dvwa", "Data": "syscall=SYS_EXECVE", "Enforcer": "AppArmor", "HashID": "1167b21433f2a4e78a4c6875bb34232e6a2b3c8535e885bb4f9e336fd2801d92", "HostName": "aditya", "HostPID": 38035, "HostPPID": 37878, "Labels": "tier=frontend,app=dvwa-web", "Message": "", "NamespaceName": "default", "Operation": "Process", "Owner": { "Name": "dvwa-web", "Namespace": "default", "Ref": "Deployment" }, "PID": 554, "PPID": 548, "PodName": "dvwa-web-566855bc5b-4j4vl", "PolicyName": "DefaultPosture", "ProcessName": "/usr/bin/kubectl", "Resource": "/usr/bin/kubectl", "Result": "Permission denied", "Severity": "", "Source": "/bin/bash", "Tags": "", "Timestamp": 1696326880, "Type": "MatchedPolicy", "UID": 0, "UpdatedTime": "2023-10-03T09:54:40.056501Z", "cluster_id": "3896", "component_name": "kubearmor", "instanceGroup": "0", "instanceID": "0", "workload": "1" } ```
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_set.md

title: "Command - devspace set" sidebar_label: devspace set Make global configuration changes ``` ``` ``` -h, --help help for set ``` ``` --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: Plural (App Definition and Development / Application Definition & Image Build)
File: report-missing-documentation.md

name: Report missing documentation about: Please file documentation content issues here. We use this to track missing docs content. title: "[Content Gap]" labels: documentation assignees: '' <!-- Help us to understand your request in context --> <!-- Do you have exactly anything in mind you are looking for --> Are you looking for the same documentation content? Give it a :thumbsup:. We factor engagement into prioritization.
Project: Meshery (Provisioning / Automation & Configuration)
File: cortex.md

layout: integration title: Cortex subtitle: Collaborative and visual infrastructure as code for Cortex image: /assets/img/integrations/cortex/icons/color/cortex-color.svg permalink: extensibility/integrations/cortex docURL: https://docs.meshery.io/extensibility/integrations/cortex description: integrations-category: Observability and Analysis integrations-subcategory: Metrics registrant: Artifact Hub components: featureList: [ "Durably store data for longer than the lifetime of any single machine, and use this data for long term capacity planning.", "Makes your PromQL queries blazin' fast through aggressive parallelization and caching.", "Gives you a global view of Prometheus time series data that includes data in long-term storage, greatly expanding the usefulness of PromQL for analytical purposes." ] 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: Chef InSpec (Provisioning / Security & Compliance)
File: google_kms_crypto_keys.md

+++ title = "googlekmscrypto_keys resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlekmscrypto_keys" identifier = "inspec/resources/gcp/googlekmscryptokeys.md googlekmscryptokeys resource" parent = "inspec/resources/gcp" +++ A `googlekmscrypto_keys` is used to test a Google CryptoKey resource ```ruby describe googlekmscryptokeys(project: 'chef-gcp-inspec', location: 'europe-west2', keyring_name: 'kms-key-ring') do its('count') { should be >= 1 } its('cryptokeynames') { should include 'kms-key' } end ``` describe googlekmscryptokeys(project: 'chef-inspec-gcp', location: 'us-east1', keyring_name: 'key-ring') do its('count') { should be <= 100} end describe googlekmscryptokeys(project: 'chef-inspec-gcp', location: 'us-east1', keyring_name: 'key-ring') do its('cryptokeynames') { should include "my-crypto-key-name" } end Properties that can be accessed from the `googlekmscrypto_keys` resource: See the resource for more information. `cryptokeynames` : an array of `googlekmscryptokey` cryptokey_name `create_times` : an array of `googlekmscryptokey` createtime `labels` : an array of `googlekmscrypto_key` labels `purposes` : an array of `googlekmscrypto_key` purpose `rotation_periods` : an array of `googlekmscryptokey` rotationperiod `version_templates` : an array of `googlekmscryptokey` versiontemplate `nextrotationtimes` : an array of `googlekmscryptokey` nextrotation_time `key_rings` : an array of `googlekmscryptokey` keyring This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: ArangoDB (App Definition and Development / Database)
File: disable_execinfo.md

+++ title = "`BOOSTOUTCOMEDISABLE_EXECINFO`" description = "If defined, disables the use of the `<execinfo.h>` header (or the win32 emulation)." +++ If defined, disables the use of the `<execinfo.h>` header (or the win32 emulation). Some embedded Linux toolchains do not define `<execinfo.h>`, thus disabling C++ exceptions on those toolchains produces a failure to find this file. Avoid that problem by defining this macro to disable stack backtrace support entirely. Overridable: Define before inclusion. Default: Defined if `ANDROID` is defined, else undefined. Header: `<boost/outcome/config.hpp>`
Project: userver (App Definition and Development / Streaming & Messaging)
File: CONTRIBUTING.md

Hello! In order for us (YANDEX LLC) to accept patches and other contributions from you, you will have to adopt our Yandex Contributor License Agreement (the CLA). The current version of the CLA can be found here: 1) https://yandex.ru/legal/cla/?lang=en (in English) and 2) https://yandex.ru/legal/cla/?lang=ru (in Russian). By adopting the CLA, you state the following: You obviously wish and are willingly licensing your contributions to us for our open source projects under the terms of the CLA, You have read the terms and conditions of the CLA and agree with them in full, You are legally able to provide and license your contributions as stated, We may use your contributions for our open source projects and for any other our project too, We rely on your assurances concerning the rights of third parties in relation to your contributions. If you agree with these principles, please read and adopt our CLA. By providing us your contributions, you hereby declare that you have already read and adopt our CLA, and we may freely merge your contributions with our corresponding open source project and use it in further in accordance with terms and conditions of the CLA. If you have already adopted terms and conditions of the CLA, you are able to provide your contributions. When you submit your pull request, please add the following information into it: ``` I hereby agree to the terms of the CLA available at: [link]. ``` Replace the bracketed text as follows: [link] is the link to the current version of the CLA: https://yandex.ru/legal/cla/, https://yandex.ru/legal/cla/?lang=en (in English) or https://yandex.ru/legal/cla/?lang=ru (in Russian). It is enough to provide us such notification once. If you have any questions, please mail us at opensource@yandex-team.ru.
Project: ko (App Definition and Development / Application Definition & Image Build)
File: faq.md

is a common way to embed version info in go binaries (In fact, we do this for `ko`!). Unfortunately, because `ko` wraps `go build`, it's not possible to use this flag directly; however, you can use the `GOFLAGS` environment variable instead: ```sh GOFLAGS="-ldflags=-X=main.version=1.2.3" ko build . ``` Currently, there is a limitation that does not allow to set multiple arguments in `ldflags` using `GOFLAGS`. Using `-ldflags` multiple times also does not work. In this use case, it works best to use the in the `.ko.yaml` file. In order to support , `ko` doesn't embed timestamps in the images it produces by default. However, `ko` does respect the environment variable, which will set the container image's timestamp accordingly. Similarly, the `KODATADATEEPOCH` environment variable can be used to set the modtime timestamp of the files in `KODATA_PATH`. For example, you can set the container image's timestamp to the current timestamp by executing: ```sh export SOURCEDATEEPOCH=$(date +%s) ``` or set the timestamp of the files in `KODATAPATH` to the latest git commit's timestamp with: ```sh export KODATADATE_EPOCH=$(git log -1 --format='%ct') ``` Yes, but support for Windows containers is new, experimental, and tenuous. Be prepared to file bugs. The default base image does not provide a Windows image. You can try out building a Windows container image by to a Windows base image and building with `--platform=windows/amd64` or `--platform=all`: For example, to build a Windows container image, update your `.ko.yaml` to set the base image: ```plaintext defaultBaseImage: mcr.microsoft.com/windows/nanoserver:ltsc2022 ``` And build for `windows/amd64`. ```sh ko build ./ --platform=windows/amd64 ``` Symlinks in `kodata` are ignored when building Windows images; only regular files and directories will be included in the Windows image. Yes! `ko completion` generates a Bash/Zsh/Fish/PowerShell completion script. You can get how to load it from help document. ```sh ko completion [bash|zsh|fish|powershell] --help ``` Or, you can source it directly: ```bash source <(ko completion) ``` Yes! `ko resolve -f -` will read and process input from stdin, so you can have `ko` easily process the output of the `kustomize` command. ```sh kustomize build config | ko resolve -f - ``` Oh, you betcha. Here's a partial list: `ko` support in `ko` support for `ko` task in the `ko` support in `ko` extension for Yes! Follow these steps: so you can push to it: Export your token to `$HOME/.docker/config.json`: ```sh oc registry login --to=$HOME/.docker/config.json ``` Create a namespace where you will push your images, i.e: `ko-images` Execute this command to set `KODOCKERREPO` to publish images to the internal registry. ```sh export KODOCKERREPO=$(oc registry info --public)/ko-images ```
Project: YDB (App Definition and Development / Database)
File: session_start.md

No arguments. It's allowed only if there is in / . Returns the value of the `SessionWindow` key column. If `SessionWindow` has two arguments, it returns the minimum value of the first argument within the group/section. In the case of the expanded version `SessionWindow`, it returns the value of the second element from the tuple returned by `<calculate_lambda>`, for which the first tuple element is `True`.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: perf-12196.en.md

Improve network efficiency during routes cleanup. Previously, when a node node was down, a delete operation for every route to that node must have been exchanged between all other live nodes. After this change, only one 'match and delete' operation is exchanged between all live nodes, meaning that much fewer packets are to be sent over inter-cluster network. This optimization must be especially helpful for geo-distributed EMQX deployments, when network latency can be significantly high.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_backuprepo.md

title: kbcli backuprepo BackupRepo command. ``` -h, --help help for backuprepo ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Create a backup repo - Describe a backup repository. - List Backup Repositories. - Update a backup repository.
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: blackfire.md

The Lagoon Base Images have support for Blackfire included in the PHP Images (see ). In order to use Blackfire in Lagoon, these three environment variables need to be defined: | Environment Variable | Default | Description | | : | : | : | | `BLACKFIRE_ENABLED` | \(not set\) | Used to enable `blackfire` extension with setting variable to `TRUE` or `true` | | `BLACKFIRESERVERID` | \(not set\) | Set to Blackfire Server ID provided by Blackfire.io. Needs `BLACKFIRE_ENABLED` set to `true` | | `BLACKFIRESERVERTOKEN` | \(not set\) | Set to Blackfire Server Token provided by Blackfire.io. Needs `BLACKFIRE_ENABLED` set to `true` | For local usage of Blackfire with Lagoon Images, set the above environment variables for the PHP container. Here is an example for a Drupal application: ```yaml title="docker-compose.yml" services: [[snip]] php: [[snip]] environment: << : *default-environment # loads the defined environment variables from the top BLACKFIRE_ENABLED: TRUE BLACKFIRESERVERID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx BLACKFIRESERVERTOKEN: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ``` After restarting the containers, you should be able to profile via the or the . In order to use Blackfire in deployed Lagoon environments the same enviornment variables need to be set, this time via one of the possibilities of adding . Important: Environment variables set in the `docker-compose.yml` for local development are not used by Lagoon in remote environments! The Blackfire Agent running in the PHP containers outputs logs as normal container logs, which can be seen via `docker-compose logs` or via the Lagoon Logging Infrastructure for remote environments. By default the Logs are set to Level `3` (info), via the environment variable `BLACKFIRELOGLEVEL` the level can be increased to `4` (debug) to generate more debugging ouput.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.70.md

layout: release date: 2023-04-03 tag: v0.6.70 Fix spec anomaly in Meshmodel components @Revolyssup (#7437) [Batch2] Update Content APIs @theBeginner86 (#7423) [Batch1] Update Catalog APIs @theBeginner86 (#7421) create meshmodel helper @Azanul (#7314) Add Metabit Trading to the org list @sjtu-biggie (#7433) Add group in generated meshmodel component's apiVersion @Revolyssup (#7426) FIX white BG in dark mode in settings page under Actions @Ambareen09 (#7440) Bump eslint-config-next from 13.1.5 to 13.2.4 in /provider-ui @dependabot (#7442) Bump @cypress/code-coverage from 3.10.0 to 3.10.1 in /ui @dependabot (#7443) Bump @fortawesome/free-brands-svg-icons from 6.2.0 to 6.4.0 in /ui @dependabot (#7449) Bump @mui/material from 5.11.6 to 5.11.15 in /provider-ui @dependabot (#7441) Bump eslint-plugin-cypress from 2.12.1 to 2.13.2 in /provider-ui @dependabot (#7445) Bump cypress from 12.7.0 to 12.9.0 in /provider-ui @dependabot (#7444) [cypress ]add mochawesome package @Abhishek-kumar09 (#7429) Corrected App definition and Development Icon @ritiksaxena124 (#7424) Created Storybook components: AppBar and Chip @acald-creator (#7407) Bump eslint-config-next from 13.1.5 to 13.2.4 in /provider-ui @dependabot (#7442) Bump @cypress/code-coverage from 3.10.0 to 3.10.1 in /ui @dependabot (#7443) Bump @fortawesome/free-brands-svg-icons from 6.2.0 to 6.4.0 in /ui @dependabot (#7449) Bump @mui/material from 5.11.6 to 5.11.15 in /provider-ui @dependabot (#7441) Bump eslint-plugin-cypress from 2.12.1 to 2.13.2 in /provider-ui @dependabot (#7445) Bump cypress from 12.7.0 to 12.9.0 in /provider-ui @dependabot (#7444) Bump rack from 2.2.6.3 to 2.2.6.4 in /docs @dependabot (#7362) add light mode support for summary view @vishalvivekm (#7403) Reduce the size of the logos @mohit-marathe (#7201) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Ambareen09, @Azanul, @Revolyssup, @acald-creator, @dependabot, @dependabot[bot], @l5io, @leecalcote, @mohit-marathe, @ritiksaxena124, @sjtu-biggie, @theBeginner86, @vishalvivekm and l5io
Project: BOSH (Provisioning / Automation & Configuration)
File: code_style.md

We use which generally enforces the . We use a for customized style configuration. The current strategy is to fix the offenses either manually (if your changes are small enough) or fix them automated by running `rubocop --autocorrect` on the file(s) you changed. However, if you decide to run `rubocop --autocorrect` on the whole file(s), make sure to have a separate commit for the reformatting so that your actual commit is not polluted with code reformatting. You could do this in one of two ways: skipping the hook `git commit --no-verify` for your code change `rubocop --autocorrect` on the file you changed do the commit for the reformatted file reformatting the file before you commit your changes stash your changes `rubocop --autocorrect` on the file you're about to change do the commit for the reformatted file reapply your changes `rubocop --autocorrect` on the file commit your changes It's currently not possible to run `rubocop -a` on the whole repo since it's breaking some of our tests and makes it difficult for feature branches to be rebased onto master. Our code style is still evolving, however `rake rubocop` is run by Travis so making these pass will improve the chances that the pull request will be accepted.