cwielenb/CNCF-Dataset huggingface dataset:
Project: Beam (App Definition and Development / Streaming & Messaging)
File: yaml_mapping.md

<!-- 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. --> The contents of this file have been moved to the main Apache Beam site at https://beam.apache.org/documentation/sdks/yaml-udf/
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: open-service-mesh.md

title: Open Service Mesh (OSM) software: osm labels: category: servicemesh layer: network tutorials: https://release-v1-2.docs.openservicemesh.io/docs/guides/integrations/externalauthopa/ docs_features: envoy: note: | External Authorization supports OPA and is documented Open Service Mesh is a lightweight and extensible cloud native service mesh.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.74.md

layout: release date: 2023-04-07 tag: v0.6.74 [MeshModel/Application] add core component-metadata @Abhishek-kumar09 (#7507) [Chore] Server: Remove OAM Model @leecalcote (#7487) Perform greedy search on display name for components @Revolyssup (#7502) Fix failing build @Revolyssup (#7498) changes the application icon w/signoff @AakashRaj20 (#7482) Remove all OAM related code @Revolyssup (#7493) Thank you to our contributors for making this release possible: @AakashRaj20, @Abhishek-kumar09, @Chadha93, @Revolyssup, @acald-creator and @leecalcote
Project: Beam (App Definition and Development / Streaming & Messaging)
File: flatten.md

title: "Flatten" <!-- 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. --> <table align="left"> <a target="_blank" class="button" href="https://beam.apache.org/releases/pydoc/current/apachebeam.transforms.core.html?highlight=flatten#apachebeam.transforms.core.Flatten"> <img src="/images/logos/sdks/python.png" width="20px" height="20px" alt="Pydoc" /> Pydoc </a> </table> <br><br> Merges multiple `PCollection` objects into a single logical `PCollection`. A transform for `PCollection` objects that store the same data type. See more information in the . {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHON_Flatten" show="flatten" >}} {{< /playground >}} applies a simple 1-to-many mapping function over each element in the collection. This transform might produce zero or more outputs.
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_azure_list.md

List Azure YugabyteDB Anywhere providers List Azure YugabyteDB Anywhere providers ``` yba provider azure list [flags] ``` ``` -h, --help help for list ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Optional] The name of the provider for the action. Required for create, delete, describe, update. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage a YugabyteDB Anywhere Azure provider
Project: FOSSA (Provisioning / Security & Compliance)
File: podman.md

`fossa-cli` can use podman client to perform container image scanning analysis. `fossa-cli` will look for environment variable `DOCKER_HOST`, to infer docker engine api's socket location. As of now, `fossa-cli` only works with `unix://` socket. For podman, you can use `podman machine start` command, to retrieve Docker client compatible `DOCKER_HOST`. ```bash podman machine start Starting machine "podman-machine-default" Waiting for VM ... Mounting volume... /Users/fossa:/Users/fossa This machine is currently configured in rootless mode. If your containers require root permissions (e.g. ports < 1024), or if you run into compatibility issues with non-podman clients, you can switch using the following command: podman machine set --rootful API forwarding listening on: /Users/fossa/.local/share/containers/podman/machine/podman-machine-default/podman.sock The system helper service is not installed; the default Docker API socket address can\'t be used by podman. If you would like to install it run the following commands: sudo /usr/local/Cellar/podman/4.2.0/bin/podman-mac-helper install podman machine stop; podman machine start You can still connect Docker API clients by setting DOCKER_HOST using the following command in your terminal session: export DOCKER_HOST='unix:///Users/fossa/.local/share/containers/podman/machine/podman-machine-default/podman.sock' Machine "podman-machine-default" started successfully ``` Now we can specify `DOCKER_HOST` when running `fossa-cli`. ```bash DOCKER_HOST='unix:///Users/fossa/.local/share/containers/podman/machine/podman-machine-default/podman.sock' fossa container analyze ``` Likewise, if you are using `podman-remote`, you should be able to use generate unix socket, and use it with `fossa-cli`. Refer to documentation below for more details. Refer to documentation here: https://web.archive.org/web/20230405171636/https://podman.io/blogs/2020/07/01/rest-versioning.html https://docs.podman.io/en/latest/_static/api.html https://web.archive.org/web/20220926013308/https://access.redhat.com/documentation/en-us/redhatenterpriselinux/8/html/buildingrunningandmanagingcontainers/assemblyusing-the-container-tools-api_building-running-and-managing-containers `fossa-cli` will perform the following command: ```bash podman image inspect <ARG> podman save --format docker-archive -o <temp-path> ``` `fossa-cli` will look for `podman` executable in `$PATH`. Note this is same approach as integration via Docker Archive except that `fossa-cli` performs necessary invocation and does cleanup of artifacts. We can manually export image using podman, and analyze such image with `fossa-cli`. ```bash podman build . -t someImg:1.0.0 podman save --format docker-archive -o image.tar fossa container analyze image.tar rm image.tar ```
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_gcp.md

Manage a YugabyteDB Anywhere GCP provider Manage a GCP provider in YugabyteDB Anywhere ``` yba provider gcp [flags] ``` ``` -n, --name string [Optional] The name of the provider for the action. Required for create, delete, describe, update. -h, --help help for gcp ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage YugabyteDB Anywhere providers - Create a GCP YugabyteDB Anywhere provider - Delete a GCP YugabyteDB Anywhere provider - Describe a GCP YugabyteDB Anywhere provider - List GCP YugabyteDB Anywhere providers - Update a GCP YugabyteDB Anywhere provider
Project: BigchainDB (App Definition and Development / Database)
File: node-components.md

<! Copyright 2020 Interplanetary Database Association e.V., BigchainDB and IPDB software contributors. SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0) Code is Apache-2.0 and docs are CC-BY-4.0 > A production BigchainDB node must include: BigchainDB Server MongoDB Server 3.4+ (mongod) Tendermint Storage for MongoDB and Tendermint It could also include several other components, including: NGINX or similar, to provide authentication, rate limiting, etc. An NTP daemon running on all machines running BigchainDB Server or mongod, and possibly other machines Probably not MongoDB Automation Agent. It's for automating the deployment of an entire MongoDB cluster. MongoDB Monitoring Agent MongoDB Backup Agent Log aggregation software Monitoring software Maybe more The relationship between the main components is illustrated below.
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: compose_alpha_watch.md

<!MARKERGENSTART--> Watch build context for service and rebuild/refresh containers when files are updated | Name | Type | Default | Description | |:|:--|:--|:-| | `--dry-run` | | | Execute command in dry run mode | | `--no-up` | | | Do not build & start services before watching | | `--quiet` | | | hide build output | <!MARKERGENEND-->
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_plugin.md

title: kbcli plugin Provides utilities for interacting with plugins. Provides utilities for interacting with plugins. Plugins provide extended functionality that is not part of the major command-line distribution. ``` -h, --help help for plugin ``` ``` --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 ``` - Describe a plugin - Manage custom plugin indexes - Install kbcli or kubectl plugins - List all visible plugin executables on a user's PATH - Search kbcli or kubectl plugins - Uninstall kbcli or kubectl plugins - Upgrade kbcli or kubectl plugins
Project: MySQL (App Definition and Development / Database)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: bug assignees: PJK Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior. If possible, please attach a runnable code snippet. Expected behavior A clear and concise description of what you expected to happen. Environment libcbor version and build configuration flags (or source package version if using a package manager).
Project: Kafka (App Definition and Development / Streaming & Messaging)
File: CONTRIBUTING.md

Before opening a pull request, review the and pages. It lists steps that are required before creating a PR. When you contribute code, you affirm that the contribution is your original work and that you license the work to the project under the project's open source license. Whether or not you state this explicitly, by submitting any copyrighted material via pull request, email, or other means you agree to license the material under the project's open source license and warrant that you have the legal authority to do so.
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_open.md

title: "Command - devspace open" sidebar_label: devspace open Opens the space in the browser ``` devspace open [flags] ``` ``` Opens the space domain in the browser Example: devspace open ``` ``` -h, --help help for open --port int The port on the localhost to listen on --provider string The cloud provider to use ``` ``` --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: YugabyteDB (App Definition and Development / Database)
File: caspio.md

title: Use Caspio with YugabyteDB YSQL headerTitle: Caspio linkTitle: Caspio description: Use Caspio to work with distributed SQL databases in YugabyteDB. menu: preview_integrations: identifier: caspio parent: development-platforms weight: 900 type: docs is a no-code platform for creating business applications. With a wide variety of application integrations, it allows users to better connect to and understand their business data. You can access your PostgreSQL-compatible databases, such as YugabyteDB, by connecting to Caspio through one of their . This document describes how to connect to YugabyteDB using Caspio via . Your YugabyteDB cluster should be up and running. Refer to . To connect your YugabyteDB database to Caspio: In Zapier, create a Caspio application integration by providing your Caspio subdomain. In Zapier, create a PostgreSQL integration as follows: Add the host address of your YugabyteDB instance. Change the port from `5432` to `5433`. Change the database name to that of your YugabyteDB instance. Provide the schema name. Provide the username and password for your YugabyteDB instance. Optionally, to connect via SSL, provide the CA certificate. If your cluster is in YugabteDB Managed, be sure to add the listed IP addresses to the cluster . With these applications connected, you can create Zaps to trigger events and create relationships between Caspio and the underlying YugabyteDB data source.
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: ansible-operator-status.md

Status: implemented The operator can surface basic information from the Ansible code in a generic fashion - it can set the conditions and it can surface a failure message if the run failed. See documentation in the Developer Guide: There is currently no way to intentionally surface information to the status object from Ansible. If users want to surface custom information in their Custom Resources status field, they would need to change the Go code for the operator. There are two main approaches we see for users wanting to manage the status: The user wants to change the status of the Custom Resource over the course of an Ansible reconciliation run, but still wants to make use of the operator's builtin status management utilities to set certain conditions and failure messages The user wants to manage the entire status manually from Ansible, and the Go-side of Ansible Operator does nothing with statuses Add a new field to the watches.yaml entry, which tells the operator whether or not it is allowed to manage status. Add a new Ansible module, named `k8s_status` that is usable when running inside Ansible Operator. The `k8s_status` module would take the apiVersion, kind, name, namespace as well as a status blob and list of conditions. It would then set the status on the specified resource using that blob. The conditions would be validated to conform to the . It would then take this status blob and call to update the status subresource for the specified resource (which should be the CR that is being reconciled).\ **Note - likely this module would inherit from k8scommon, and include the same general authentication/etc options as the other k8s modules*_ The Go-side of the Ansible Operator would need two changes: It needs to not attempt to manage the status when the watches.yaml tells it not to It needs to `GET` the current state of the object before updating the status after an Ansible reconciliation run, so that it does not attempt to write a stale version of the object. Not all clusters and Custom Resource Definitions have the status subresource enabled. In the case where the status subresource is not enabled for a CRD, we can do one of two things: Error out - if the user is attempting to manage the status of an object that doesnt have the subresource enabled, we call it a misconfiguration and fail without attempting to update the status. If a resource doesnt have the status subresource enabled, the status field can still be updated. Instead of updating the status subresource, you would `GET` the resource in its current state, update the status field manually, and `PUT` the whole object back.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: volumes-from.md

Mount volumes from the specified container(s). Used to share volumes between containers<<| and pods>>. The options is a comma-separated list with the following available elements: rw|ro* z* Mounts already mounted volumes from a source container onto another <<container|pod>>. CONTAINER may be a name or ID. To share a volume, use the --volumes-from option when running the target container. Volumes can be shared even if the source container is not running. By default, Podman mounts the volumes in the same mode (read-write or read-only) as it is mounted in the source container. This can be changed by adding a `ro` or `rw` option. Labeling systems like SELinux require that proper labels are placed on volume content mounted into a <<container|pod>>. Without a label, the security system might prevent the processes running inside the container from using the content. By default, Podman does not change the labels set by the OS. To change a label in the <<container|pod>> context, add `z` to the volume mount. This suffix tells Podman to relabel file objects on the shared volumes. The `z` option tells Podman that two entities share the volume content. As a result, Podman labels the content with a shared content label. Shared volume labels allow all containers to read/write content. If the location of the volume from the source container overlaps with data residing on a target <<container|pod>>, then the volume hides that data on the target.
Project: Meshery (Provisioning / Automation & Configuration)
File: components.md

layout: default title: Components permalink: concepts/logical/components type: concepts abstract: "Meshery Components identify and characterize infrastructure under management." language: en list: include redirect_from: concepts/components Components represent entities in the Meshery ecosystem, exposing capabilities of the underlying platform. They can be registered, created, and used by users and operators. Components have definitions, instances, and associated metadata. Components having the same `kind`, `apiVersion` and `model.name` attributes are considered duplicates. [Meshery Components]({{ site.baseurl }}/assets/img/architecture/meshery-components.svg) <!-- @leecalcote - This is mumbo jumbo to users and needs to be re-written. --> Components have a status that is represented as a `Connection` object. Both the administrative and real-time status of a component is a normalized representation of the connection's state. The status is represented as a `Connection` object because the status of a component is a connection to the component. For example, the status of a Kubernetes cluster is a direct reflection of a Meshery Server's connection to the cluster. Normalizing and extracting the status of a component as a direct property of the component and putting it into a connection allows multiple systems to share the same component with different states. For example, different Meshery Servers can access the same Kubernetes cluster, but each Meshery Server has its own connection to the cluster with its own status. Learn more about .
Project: KICS (Provisioning / Security & Compliance)
File: f99d3482-fa8c-4f79-bad9-35212dded164.md

title: Serverless Function Without Tags hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: f99d3482-fa8c-4f79-bad9-35212dded164 Query name: Serverless Function Without Tags Platform: ServerlessFW Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: Serverless Function should be have associated tags<br> ```yml title="Positive test num. 1 - yml file" hl_lines="8" service: service frameworkVersion: '2' provider: name: aws runtime: nodejs12.x functions: hello: handler: handler.hello onError: arn:aws:sns:us-east-1:XXXXXX:test ``` ```yml title="Negative test num. 1 - yml file" service: service frameworkVersion: '2' provider: name: aws runtime: nodejs12.x functions: hello: handler: handler.hello onError: arn:aws:sns:us-east-1:XXXXXX:test tags: foo: bar ``` ```yml title="Negative test num. 2 - yml file" service: service frameworkVersion: '2' provider: name: aws runtime: nodejs12.x stackTags: foo: bar functions: hello: handler: handler.hello onError: arn:aws:sns:us-east-1:XXXXXX:test ```