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

We really value anything that you can offer us! We've made building and viewing the documentation really straightforward, and the team is always ready to help out with reviews or pointers. We use with the excellent theme. From the root of the Lagoon repository (you'll need Docker), run: ```bash title="Get local docs up and running." docker run --rm -it -p 127.0.0.1:8000:8000 -v ${PWD}:/docs ghcr.io/amazeeio/mkdocs-material ``` <!-- markdown-link-check-disable-next-line --> This will start a development server on , configured to live-reload on any updates. The customized Docker image contains all the necessary extensions. Alternatively, to run the `mkdocs` package locally, you'll need to install mkdocs, and then install all of the necessary plugins. ```bash title="Install mkdocs" pip3 install -r docs/requirements.txt mkdocs serve ``` Each documentation page also has an "edit" pencil in the top right, that will take you to the correct page in the Git repository. Feel free to contribute here, too - you can always use the built-in . It's got basic Markdown previews, but none of the mkdocs loveliness. We use the GitHub Action to build all main branch pushes, and trigger a deployment of the `gh-pages` branch.
Project: YDB (App Definition and Development / Database)
File: logging.md

Each {{ ydb-short-name }} component writes messages to logs at different levels. They can be used to detect severe issues or identify the root causes. You can configure logging for the various components of the YDB in the . There are currently two options for running YDB logging: manually or using systemd. YDB provides standard mechanisms for collecting logs and metrics. Logging is done to standard `stdout` and `stderr` streams and can be redirected using popular solutions. Default logs are written to `journald` and can be retrieved via `journalctl -u ydbd`.
Project: KubeEdge (Provisioning / Automation & Configuration)
File: VERSIONING.md

We follow the , and use the corresponding tooling. For the purposes of the aforementioned guidelines, controller-runtime counts as a "library project", but otherwise follows the guidelines exactly. For release branches, we generally tend to support backporting one (1) major release (`release-{X-1}` or `release-0.{Y-1}`), but may go back further if the need arises and is very pressing (e.g. security updates). Note the . Particularly: We DO guarantee Kubernetes REST API compability -- if a given version of controller-runtime stops working with what should be a supported version of Kubernetes, this is almost certainly a bug. We DO NOT guarantee any particular compability matrix between kubernetes library dependencies (client-go, apimachinery, etc); Such compability is infeasible due to the way those libraries are versioned.
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v0.11.1.md

Fixed Dapr sidecar authentication issue when Highly available mode is enabled (https://github.com/dapr/dapr/issues/2187) fixed in the 0.11.1 release contained a regression that caused the Dapr control plane services to not function when running in HA (High Availability) mode enabled. The root cause was that multiple instances (3 in the case of HA mode) of the Sentry Certificate Authority would race to create new root certs. Until the pods were restarted to load the certificate from the secret store, each instance would contain different root CAs and would issue different certificates to the Dapr control plane pods and the Dapr sidecars, which resulted in rejected connections. The issue was fixed with . In addition, an to make sure that e2e tests run in HA mode in addition to a single pod setup. The issue was closed with the merging of this .
Project: Glasskube (App Definition and Development / Application Definition & Image Build)
File: 02_timoni.md

slug: timoni sidebar_label: With Timoni title: Glasskube vs Timoni Comparison description: Timoni installs and updates cloud-native applications as bundles (OCI images) with a great support for configuration, but it requires users to create its own bundles. is created by to improve bundling cloud native applications and their lifecycle management. Timoni is closer related to Helm than Glasskube, but brings some features and new approaches to the table Helm doesn't offer. Its bundles are OCI images, so the only way to install these bundles is to publish them first to an OCI registry, which makes additional security features like image (co-)singing possible. Similar to Glasskube it performs garbage collection of orphan resources after an uninstallation operation. Timoni is generally more mature than Glasskube. However, it doesn't prioritize making standard package installation and upgrades easy. As of now, there's no plan for GUI support either. Users have to bundle their own applications and provide their registry for images. Glasskube is not yet compatible with Timoni or its bundles, but in a similar way how Glasskube supports helm charts, Timoni bundles can be supported. There is currently an to provide Timoni support. Let us know what you think!
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: cap-drop.image.md

When executing RUN instructions, run the command specified in the instruction with the specified capability removed from its capability set. The CAP\CHOWN, CAP\DAC\OVERRIDE, CAP\FOWNER, CAP\FSETID, CAP\KILL, CAP\NET\BIND\SERVICE, CAP\SETFCAP, CAP\SETGID, CAP\SETPCAP, and CAP\_SETUID capabilities are granted by default; this option can be used to remove them. If a capability is specified to both the --cap-add and --cap-drop options, it is dropped, regardless of the order in which the options were given.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-pod-prune.1.md

% podman-pod-prune 1 podman-pod-prune - Remove all stopped pods and their containers podman pod prune [options] podman pod prune removes all stopped pods and their containers from local storage. Force removal of all running pods and their containers. The default is false. Remove all stopped pods and their containers from local storage. ``` $ sudo podman pod prune 22b8813332948064b6566370088c5e0230eeaf15a58b1c5646859fd9fc364fe7 2afb26869fe5beab979c234afb75c7506063cd4655b1a73557c9d583ff1aebe9 49161ad2a722cf18722f0e17199a9e840703a17d1158cdeda502b6d54080f674 5ca429f37fb83a9f54eea89e3a9102b7780a6e6ae5f132db0672da551d862c4a 6bb06573787efb8b0675bc88ebf8361f1a56d3ac7922d1a6436d8f59ffd955f1 ``` , April 2019, Originally compiled by Peter Hunt (pehunt at redhat dot com)
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-manifest-remove.1.md

% podman-manifest-remove 1 podman\-manifest\-remove - Remove an image from a manifest list or image index podman manifest remove listnameorindexname transport:details Removes the image with the specified digest from the specified manifest list or image index. The list image's ID and the digest of the removed image's manifest. Remove specified digest from the manifest list: ``` podman manifest remove mylist:v1.11 sha256:cb8a924afdf0229ef7515d9e5b3024e23b3eb03ddbba287f4a19c6ac90b8d221 e604eabaaee4858232761b4fef84e2316ed8f93e15eceafce845966ee3400036 :sha256:cb8a924afdf0229ef7515d9e5b3024e23b3eb03ddbba287f4a19c6ac90b8d221 ``` ,
Project: Flink (App Definition and Development / Streaming & Messaging)
File: environment_variables.md

title: "Environment Variables" weight: 131 type: docs aliases: /dev/python/environment_variables.html <!-- 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. --> These environment variables will affect the behavior of PyFlink: <table class="table table-bordered"> <thead> <tr> <th class="text-left" style="width: 30%">Environment Variable</th> <th class="text-center">Description</th> </tr> </thead> <tbody> <tr> <td> <strong>FLINK_HOME</strong> </td> <td> PyFlink job will be compiled before submitting and it requires Flink's distribution to compile the job. PyFlink's installation package already contains Flink's distribution and it's used by default. This environment allows you to specify a custom Flink's distribution. </td> </tr> <tr> <td> <strong>PYFLINKCLIENTEXECUTABLE</strong> </td> <td> The path of the Python interpreter used to launch the Python process when submitting the Python jobs via "flink run" or compiling the Java/Scala jobs containing Python UDFs. Equivalent to the configuration option 'python.client.executable'. The priority is as following: <ol> <li>The configuration 'python.client.executable' defined in the source code; </li> <li>The environment variable PYFLINKCLIENTEXECUTABLE; </li> <li>The configuration 'python.client.executable' defined in </li> </ol> If none of above is set, the default Python interpreter 'python' will be used. </td> </tr> </tbody> </table>
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_exec_mongodb.md

title: Kubectl-Dba Exec Mongodb menu: docs_{{ .version }}: identifier: kubectl-dba-exec-mongodb name: Kubectl-Dba Exec Mongodb parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Execute commands to a mongodb resource Use this cmd to execute mongodb commands to a mongodb object's primary pod. Examples: kubectl dba exec mg mg-rs -n demo -f mongo.js kubectl dba exec mg mg-rs -n demo -c "printjson(db.getCollectionNames())" ``` kubectl-dba exec mongodb [flags] ``` ``` -c, --command string command to execute -f, --file string path of the script file -h, --help help for mongodb ``` ``` --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/runner/.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 --default-seccomp-profile-type string Default seccomp profile --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 --password string Password for basic authentication to the API server --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 --username string Username for basic authentication to the API server ``` - Execute script or command to a database.
Project: MongoDB (App Definition and Development / Database)
File: README_default_max_time_ms.md

In addition to the query-specific `maxTimeMS`, the cluster-wide server parameter `defaultMaxTimeMS` can be used to set the default time limit for when `maxTimeMS` is not specified. The parameter has an effect only when authentication is turned on. The value of `defaultMaxTimeMS.readOperations` applies to read operations. Note: aggregations with pipelines containing $out and $merge stages are considered writes. The cluster parameter `defaultMaxTimeMS` shares the same semantic as `maxTimeMS`. When the value is set to 0, the default value, command runtime is unbounded. Commands that run longer than `defaultMaxTimeMS` will return a `MaxTimeMSExpired` error. All commands run by a user with `bypassDefaultMaxTimeMS` privilege will ignore the value of `defaultMaxTimeMS`. The root and \\system roles have the privilege by default. When multiple time-out values are available, the value is chosen using the following hierarchy (higher to lower priority): The query-specific `maxTimeMS` option The tenant-specific `defaultMaxTimeMS` value The global `defaultMaxTimeMS` value
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.35.md

layout: release date: 2022-12-14 tag: v0.6.35 language: en Fix panic @Revolyssup (#6707) Fix failing queries in case of custom telemetry deployment @MUzairS15 (#6705) Update script to add publish flag @sudo-NithishKarthik (#6704) Allow save operation for alternative format directly @Revolyssup (#6679) Remove overzealous notifications of design/app save @Revolyssup (#6697) Update contributing.md @Anand-Theertha (#6688) Edited Repository Overview Link @BabyElias (#6663) Improve the error messages in `mesheryctl mesh` @debasishbsws (#6626) disable some functionality in playground @harkiratsm (#6706) Instant fix of dashboard page. @Harshit-Dandriyal (#6709) [Extension] show SignUp Form in Playground for restricted users to extension @Abhishek-kumar09 (#6703) Fixed telemetry bug and organized telemetry components @MUzairS15 (#6693) Temp fix to get animated logo css style for Next.js to compile @acald-creator (#6684) Ellipsis property added for button in context-switcher @deepakdinesh1123 (#6671) updated gh workflows to ubuntu version 22.04 @StarTrooper08 (#6689) Add token while checking out layer5 repo @Revolyssup (#6696) Add token while checking out layer5 repo @Revolyssup (#6695) Remove /docs path mandate on component updater @Revolyssup (#6694) Add path to commit action @Revolyssup (#6692) Add cron as trigger for component updation in docs @Revolyssup (#6691) [Draft] Add flag to update docs from spreadsheet @Revolyssup (#6682) [cleanup] Remove extraneous debug logs @theBeginner86 (#6668) Add `system dashboard` to the mesheryctl command reference index @alphaX86 (#6643) Bump loofah from 2.18.0 to 2.19.1 in /docs @dependabot (#6699) Bump rails-html-sanitizer from 1.4.3 to 1.4.4 in /docs @dependabot (#6698) Edited repository overview link @BabyElias (#6664) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Anand-Theertha, @BabyElias, @Chadha93, @Harshit-Dandriyal, @MUzairS15, @Revolyssup, @StarTrooper08, @acald-creator, @alphaX86, @debasishbsws, @deepakdinesh1123, @dependabot, @dependabot[bot], @harkiratsm, @l5io, @leecalcote, @sudo-NithishKarthik, @theBeginner86 and l5io
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: metrics.md

This document aims to help users that are not familiar with metrics exposed by this operator. The metrics documentation is auto-generated by the utility tool "monitoring/metricsdocs" and reflects all of the metrics that are exposed by the operator. Total number of times the deployment size was not as desired. Type: Counter. After developing new metrics or changing old ones, please run "make generate-metricsdocs" to regenerate this document. If you feel that the new metric doesn't follow these rules, please change "monitoring/metricsdocs" according to your needs.
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: opa-wasm-js.md

title: OPA Wasm Javascript Module software: javascript inventors: styra labels: category: wasm type: poweredbyopa tutorials: https://github.com/open-policy-agent/npm-opa-wasm/blob/main/README.md code: https://github.com/open-policy-agent/npm-opa-wasm/ https://www.npmjs.com/package/@open-policy-agent/opa-wasm?activeTab=readme videos: title: 'Scratching an Itch: Running Policy in Hard to Reach Places with Wasm & OPA' speakers: name: Charlie Egan organization: styra link: https://www.youtube.com/watch?v=BdeBhukLwt4 docs_features: wasm-integration: note: 'This project implements the OPA Wasm module interface in JavaScript. ' A small SDK for using WebAssembly (Wasm) compiled Rego policies
Project: KICS (Provisioning / Security & Compliance)
File: 313d6deb-3b67-4948-b41d-35b699c2492e.md

title: Cloud DNS Without DNSSEC hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 313d6deb-3b67-4948-b41d-35b699c2492e Query name: Cloud DNS Without DNSSEC Platform: GoogleDeploymentManager Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: DNSSEC must be enabled for Cloud DNS<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" resources: name: dns type: dns.v1.managedZone properties: name: my-zone ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="6" resources: name: dns2 type: dns.v1.managedZone properties: name: my-zone2 dnssecConfig: kind: "dns#managedZoneDnsSecConfig" ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="7" resources: name: dns3 type: dns.v1.managedZone properties: name: my-zone3 dnssecConfig: state: "off" ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: dns4 type: dns.v1.managedZone properties: name: my-zone4 dnssecConfig: state: "on" ```
Project: FoundationDB (App Definition and Development / Database)
File: README.md

This contains a sample `docker-compose.yaml` to run a simple Python application running with FoundationDB as a storage backend. All variables are located in `.env` file. ```bash docker-compose up -d ``` This will start: 1 coordinator 2 fdbservers 1 Flask application The Flask application can be accessed using curl: ```bash curl http://0.0.0.0:5000/counter # 0 curl -X POST http://0.0.0.0:5000/counter/increment # 1 curl -X POST http://0.0.0.0:5000/counter/increment # 2 curl http://0.0.0.0:5000/counter # 2 ``` If you want to access the cluster from your machine, here's a `cluster file` ready for you: ```bash echo "docker:docker@127.0.0.1:4500" > docker.cluster FDBCLUSTERFILE=./docker.cluster fdbcli ``` ```bash docker-compose down ``` The client application is also available as a standalone image: `foundationdb/foundationdb-sample-python-app:latest`. : \"\"/fdb.cluster: \"test:test@$ips\"/" -e "s/\"runProcesses\": false/\"runProcesses\": true/" packaging/docker/kubernetes/test_config.yaml | kubectl apply -f - kubectl annotate pod -l app=fdb-kubernetes-example foundationdb.org/outdated-config-map-seen=$(date +%s) --overwrite kubectl exec -it sts/fdb-kubernetes-example -- fdbcli --exec "configure new double ssd" ``` This will set up a cluster in your Kubernetes environment using a StatefulSet, to provide a simple subset of what the Kubernetes operator does to set up the cluster. Note: This assumes that you are running Docker Desktop on your local machine, with Kubernetes configured through Docker Desktop. You can then make changes to the data in the ConfigMap and update the `fdbserver` processes: ```bash sed -e "s/fdb.cluster: \"\"/fdb.cluster: \"test:test@$ips\"/" -e "s/\"runProcesses\": false/\"runProcesses\": true/" packaging/docker/kubernetes/test_config.yaml | kubectl apply -f - kubectl annotate pod -l app=fdb-kubernetes-example foundationdb.org/outdated-config-map-seen=$(date +%s) --overwrite kubectl exec -it sts/fdb-kubernetes-example -- fdbcli --exec "kill; kill all; status" ``` Once you are done, you can tear down the example with the following command: ```bash kubectl delete -f packaging/docker/kubernetes/test_config.yaml kubectl delete pvc -l app=fdb-kubernetes-example ``` The following steps assume that you already have a setup for the fdb-kubernetes-operator. ```bash mkdir -p website docker build -t foundationdb/fdb-kubernetes-monitor:7.1.11 --target fdb-kubernetes-monitor --build-arg FDBVERSION=7.1.11 --build-arg FDBLIBRARY_VERSIONS="7.1.11 6.3.24 6.2.30" -f packaging/docker/Dockerfile . ``` Depending on the Kubernetes setup you use you might have to push the newly build image to a local registry. Now you should change to the directory that contains the repository. In the top directory run: ```bash vim ./config/tests/base/cluster.yaml kubectl apply -k ./config/tests/unified_image ```
Project: YDB (App Definition and Development / Database)
File: as_tagged.md

Wraps the value in the with the specified tag, preserving the physical data type. `Untag`: The reverse operation. Required arguments: Value of any type. Tag name. Returns a copy of the value from the first argument with the specified tag in the data type. Examples of use cases: Returns to the client's web interface the media files from BASE64-encoded strings{% if feature_webui %}. Tag support in the YQL Web UI {% endif %}. {% if feature_mapreduce %}* Prevent passing of invalid values at the boundaries of UDF calls.{% endif %} Additional refinements at the level of returned columns types.
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.17.3.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Checksum verification is disabled for LocalFS | Blocker | . | Raghu Angadi | Raghu Angadi | | | Bug in FSInputChecker makes it possible to read from an invalid buffer | Blocker | fs | Ning Li | Ning Li | | | distcp fails | Blocker | . | Christian Kunz | Tsz Wo Nicholas Sze | | | ChecksumFileSystem does not override all create(...) methods | Blocker | fs | Tsz Wo Nicholas Sze | Tsz Wo Nicholas Sze | | | [HOD] Be less agressive when querying job status from resource manager. | Blocker | contrib/hod | Hemanth Yamijala | Hemanth Yamijala | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Chinese translation of core docs | Major | documentation | Xuebing Yan | Xuebing Yan |
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: SECURITY.md

See for a list of currently supported versions. Vulnerabilities reported for versions out of support will not be investigated. Please responsibly disclosure vulnerabilities to `rabbitmq-core@groups.vmware.com` and include the following information: RabbitMQ and Erlang versions used Operating system used A set of steps to reproduce the observed behavior An archive produced by RabbitMQ core team will get back to you after we have triaged the issue. If there's no sufficient reproduction information available, we won't be able to act on the report. RabbitMQ core team does not have a security vulnerability bounty programme at this time.