cwielenb/CNCF-Dataset huggingface dataset:
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-network-connect.1.md

% podman-network-connect 1 podman\-network\-connect - Connect a container to a network podman network connect [options] network container Connects a container to a network. A container can be connected to a network by name or by ID. Once connected, the container can communicate with other containers in the same network. Add network-scoped alias for the container. If the network has DNS enabled (`podman network inspect -f {{.DNSEnabled}} <NAME>`), these aliases can be used for name resolution on the given network. Multiple --alias options may be specified as input. NOTE: When using CNI, a container only has access to aliases on the first network that it joins. This limitation does not exist with netavark/aardvark-dns. Set a static ipv4 address for this container on this network. Set a static ipv6 address for this container on this network. Set a static mac address for this container on this network. Connect specified container to a named network: ``` podman network connect test web ``` Connect specified container to named network with two aliases: ``` podman network connect --alias web1 --alias web2 test web ``` Connect specified container to named network with a static ip: ``` podman network connect --ip 10.89.1.13 test web ``` , , , November 2020, Originally compiled by Brent Baude <bbaude@redhat.com>
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_create_view.md

title: CREATE VIEW statement [YSQL] headerTitle: CREATE VIEW linkTitle: CREATE VIEW description: Use the CREATE VIEW statement to create a view in a database. menu: v2.18: identifier: ddlcreateview parent: statements type: docs Use the `CREATE VIEW` statement to create a view in a database. It defines the view name and the (select) statement defining it. {{%ebnf%}} create_view {{%/ebnf%}} Create a view. Specify the name of the view. An error is raised if view with that name already exists in the specified database (unless the `OR REPLACE` option is used). Specify a comma-separated list of columns. If not specified, the column names are deduced from the query. Specify a `SELECT` or `VALUES` statement that will provide the columns and rows of the view. Using this qualifier will create a temporary view. Temporary views are visible only in the current client session in which they are created and are automatically dropped at the end of the session. See the section . Create a sample table. ```plpgsql CREATE TABLE sample(k1 int, k2 int, v1 int, v2 text, PRIMARY KEY (k1, k2)); ``` Insert some rows. ```plpgsql INSERT INTO sample(k1, k2, v1, v2) VALUES (1, 2.0, 3, 'a'), (2, 3.0, 4, 'b'), (3, 4.0, 5, 'c'); ``` Create a view on the `sample` table. ```plpgsql CREATE VIEW sample_view AS SELECT * FROM sample WHERE v2 != 'b' ORDER BY k1 DESC; ``` Select from the view. ```plpgsql yugabyte=# SELECT * FROM sample_view; ``` ``` k1 | k2 | v1 | v2 -+-+-+- 3 | 4 | 5 | c 1 | 2 | 3 | a (2 rows) ```
Project: RBAC Manager (Provisioning / Security & Compliance)
File: rbacdefinitions.md

Just as Kubernetes Deployments make Pods much simpler to manage at scale, RBAC Definitions are designed to simplify the management of Role Bindings and Service Accounts at scale. RBAC Manager will create, update, or delete Cluster Role Bindings, Role Bindings, or Service Accounts that are referenced in an RBAC Definition. Here's a more complete example of what that could look like: ```yaml apiVersion: rbacmanager.reactiveops.io/v1beta1 kind: RBACDefinition metadata: name: rbac-manager-users-example rbacBindings: name: cluster-admins subjects: kind: User name: jane@example.com clusterRoleBindings: clusterRole: cluster-admin name: web-developers subjects: kind: User name: dave@example.com kind: User name: joe@example.com roleBindings: clusterRole: edit namespace: web clusterRole: view namespace: api name: ci-bot subjects: kind: ServiceAccount name: ci-bot namespace: rbac-manager roleBindings: clusterRole: edit namespaceSelector: matchLabels: ci: edit clusterRole: admin namespaceSelector: matchExpressions: key: app operator: In values: web queue ``` In the above example, RBAC Manager will create the following resources: A Cluster Role Binding that gives Jane cluster-admin access A Role Binding that gives Dave and Joe edit access in the web namespace A Role Binding that gives Dave and Joe view access in the api namespace A Service Account named ci-bot in the rbac-manager namespace Role Binding(s) that grant the ci-bot Service Account edit access in all namespaces with `ci=edit` labels Role Binding(s) that grant the ci-bot Service Account admin access in all namespaces with `app=web` or `app=queue` labels There are more examples of RBAC Definitions in the examples directory of this repo.
Project: KICS (Provisioning / Security & Compliance)
File: e42a3ef0-5325-4667-84bf-075ba1c9d58e.md

title: EC2 Instance Using Default VPC hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e42a3ef0-5325-4667-84bf-075ba1c9d58e Query name: EC2 Instance Using Default VPC Platform: CloudFormation Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: EC2 Instances should not be configured under a default VPC network<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" Resources: DefaultVPC: Type: AWS::EC2::Instance Properties: ImageId: "ami-79fd7eee" KeyName: "testkey" SubnetId: !Ref PublicSubnetA2 PublicSubnetA2: Type: AWS::EC2::Subnet Properties: VpcId: !Ref DefaultVPC CidrBlock: 10.1.10.0/24 AvailabilityZone: !Select [ 0, !GetAZs ] # Obtenha o primeiro AZ na lista Tags: Key: Name Value: !Sub ${AWS::StackName}-Public-A ``` ```json title="Positive test num. 2 - json file" hl_lines="7" { "Resources": { "DefaultVPC": { "Properties": { "ImageId": "ami-79fd7eee", "KeyName": "testkey", "SubnetId": "PublicSubnetA2" }, "Type": "AWS::EC2::Instance" }, "PublicSubnetA2": { "Properties": { "AvailabilityZone": [ 0, "" ], "CidrBlock": "10.1.10.0/24", "Tags": [ { "Key": "Name", "Value": "${AWS::StackName}-Public-A" } ], "VpcId": "DefaultVPC" }, "Type": "AWS::EC2::Subnet" } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: DefaultVPC: Type: AWS::EC2::Instance Properties: ImageId: "ami-79fd7eee" KeyName: "testkey" SubnetId: !Ref PublicSubnetA22 PublicSubnetA22: Type: AWS::EC2::Subnet Properties: VpcId: !Ref VPC CidrBlock: 10.1.10.0/24 AvailabilityZone: !Select [ 0, !GetAZs ] # Obtenha o primeiro AZ na lista Tags: Key: Name Value: !Sub ${AWS::StackName}-Public-A ``` ```json title="Negative test num. 2 - json file" { "Resources": { "DefaultVPC": { "Properties": { "ImageId": "ami-79fd7eee", "KeyName": "testkey", "SubnetId": "PublicSubnetA22" }, "Type": "AWS::EC2::Instance" }, "PublicSubnetA22": { "Properties": { "AvailabilityZone": [ 0, "" ], "CidrBlock": "10.1.10.0/24", "Tags": [ { "Key": "Name", "Value": "${AWS::StackName}-Public-A" } ], "VpcId": "VPC" }, "Type": "AWS::EC2::Subnet" } } } ```
Project: KICS (Provisioning / Security & Compliance)
File: ec18a0d3-0069-4a58-a7fb-fbfe0b4bbbe0.md

title: Kubelet Certificate Authority Not Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ec18a0d3-0069-4a58-a7fb-fbfe0b4bbbe0 Query name: Kubelet Certificate Authority Not Set Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Secret Management URL: When using kube-apiserver command, the 'kubelet-certificate-authority' flag should be set<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--kubelet-certificate-authority=/path/to/any/cert/file.pem"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver","--kubelet-certificate-authority=/path/to/any/cert/file.crt"] args: [] restartPolicy: OnFailure ```
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-11541.en.md

Introduced additional way of file transfer interactions. Now client may send file transfer commands to `$file-async/...` topic instead of `$file/...` and receive command execution results as messages to `$file-response/{clientId}` topic. This simplifies file transfer feature usage in certain cases, for example, when a client uses MQTTv3 or when the broker is behind an MQTT bridge. See the for more details.
Project: ClickHouse (App Definition and Development / Database)
File: v21.11.3.6-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Memory amount was incorrectly estimated when ClickHouse is run in containers with cgroup limits. (). Backported in : Fix possible assert in `hdfs` table function/engine, add test. (). Backported in : Fix abort in debug server and `DB::Exception: std::outofrange: basic_string` error in release server in case of bad hdfs url by adding additional check of hdfs url structure. ().
Project: YugabyteDB (App Definition and Development / Database)
File: yba_universe_restart.md

Restart a YugabyteDB Anywhere Universe Restart a YugabyteDB Anywhere Universe ``` yba universe restart [flags] ``` ``` -n, --name string [Required] The name of the universe to be restarted. -f, --force [Optional] Bypass the prompt for non-interactive usage. -s, --skip-validations [Optional] Skip validations before running the CLI command. --delay-between-master-servers int32 [Optional] Upgrade delay between Master servers (in miliseconds). (default 18000) --delay-between-tservers int32 [Optional] Upgrade delay between Tservers (in miliseconds). (default 18000) --upgrade-option string [Optional] Upgrade Options, defaults to Rolling. Allowed values (case sensitive): Rolling, Non-Rolling (involves DB downtime). Only a "Rolling" type of restart is allowed on a Kubernetes universe. (default "Rolling") -h, --help help for restart ``` ``` -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 universes
Project: KICS (Provisioning / Security & Compliance)
File: 11e9a948-c6c3-4a0f-8dcf-b5cf1763cdbe.md

title: Web App Accepting Traffic Other Than HTTPS hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 11e9a948-c6c3-4a0f-8dcf-b5cf1763cdbe Query name: Web App Accepting Traffic Other Than HTTPS Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Web app should only accept HTTPS traffic in Azure Web App Service.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="28 37" resource "azurermresourcegroup" "example" { name = "example-resources" location = "West Europe" } resource "azurermappservice_plan" "example" { name = "example-appserviceplan" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name sku { tier = "Standard" size = "S1" } } resource "azurermappservice" "example2" { name = "example-app-service" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name appserviceplanid = azurermappserviceplan.example.id site_config { dotnetframeworkversion = "v4.0" scm_type = "LocalGit" } https_only = false connection_string { name = "Database" type = "SQLServer" value = "Server=some-server.mydomain.com;Integrated Security=SSPI" } } resource "azurermappservice" "example3" { name = "example-app-service" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name appserviceplanid = azurermappserviceplan.example.id site_config { dotnetframeworkversion = "v4.0" scm_type = "LocalGit" } connection_string { name = "Database" type = "SQLServer" value = "Server=some-server.mydomain.com;Integrated Security=SSPI" } } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermresourcegroup" "example" { name = "example-resources" location = "West Europe" } resource "azurermappservice_plan" "example" { name = "example-appserviceplan" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name sku { tier = "Standard" size = "S1" } } resource "azurermappservice" "example" { name = "example-app-service" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name appserviceplanid = azurermappserviceplan.example.id site_config { dotnetframeworkversion = "v4.0" scm_type = "LocalGit" } https_only = true connection_string { name = "Database" type = "SQLServer" value = "Server=some-server.mydomain.com;Integrated Security=SSPI" } } ```
Project: MongoDB (App Definition and Development / Database)
File: fail_points.md

are test-only configurable hooks that can be triggered at runtime. Fail points allow tests to change behavior at pre-defined points to block threads, choose rarely executed branches, enhance diagnostics, or achieve any number of other aims. Fail points can be enabled, configured, and disabled via command request to a remote process or via an API within the same process. For more on what test-only means and how to enable the `configureFailPoint` command, see . A fail point must first be defined using `MONGOFAILPOINT_DEFINE(myFailPoint)`. This statement adds the fail point to a registry and allows it to be evaluated in code. There are three common patterns for evaluating a fail point: Exercise a rarely used branch: `if (whenPigsFly || myFailPoint.shouldFail()) { ... }` Block until the fail point is unset: `myFailPoint.pauseWhileSet();` Use the fail point's payload to perform custom behavior: `myFailPoint.execute( { useMyPayload(data); };` For more complete usage, see the or the [fail point tests][failpointtest]. Fail point configuration involves choosing a "mode" for activation (e.g., "alwaysOn") and optionally providing additional data in the form of a BSON object. For the vast majority of cases, this is done by issuing a `configureFailPoint` command request. This is made easier in JavaScript using the `configureFailPoint` helper from . Fail points can also be useful in C++ unit tests and integration tests. To configure fail points on the local process, use a `FailPointEnableBlock` to enable and configure the fail point for a given block scope. Finally, a fail point can also be set via setParameter by its name prefixed with "failpoint." (e.g., "failpoint.myFailPoint"). Users can also wait until a fail point has been evaluated a certain number of times _over its lifetime_. A `waitForFailPoint` command request will send a response back when the fail point has been evaluated the given number of times. For ease of use, the `configureFailPoint` JavaScript helper returns an object that can be used to wait a certain amount of times _from when the fail point was enabled_. In C++ tests, users can invoke `FailPoint::waitForTimesEntered()` for similar behavior. `FailPointEnableBlock` records the amount of times the fail point had been evaluated when it was constructed, accessible via `FailPointEnableBlock::initialTimesEntered()`. For JavaScript examples, see the . For the command implementations, see . The `failCommand` fail point is a special fail point used to mock arbitrary response behaviors to requests filtered by command, appName, etc. It is most often used to simulate specific conditions between nodes like invalid replica set configurations. For examples of use, see the .
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.4.13.md

layout: release date: 2020-11-10 tag: v0.4.13 General UI: Refine Dashboard @daksh-sagar (#1668) Improve meshery contribution flow guide @daksh-sagar (#1667) Removing snackbar while fetching results for SMI table @dhruv0000 (#1665)
Project: SPIRE (Provisioning / Key Management)
File: plugin_server_bundlepublisher_aws_s3.md

The `aws_s3` plugin puts the current trust bundle of the server in a designated Amazon S3 bucket, keeping it updated. The plugin accepts the following configuration options: | Configuration | Description | Required | Default | |-|-||--| | accesskeyid | AWS access key id. | Required only if AWSACCESSKEYID environment variable is not set. | Value of AWSACCESSKEYID environment variable. | | secretaccesskey | AWS secret access key. | Required only if AWSSECRETACCESSKEY environment variable is not set. | Value of AWSSECRETACCESSKEY environment variable. | | region | AWS region to store the trust bundle. | Yes. | | | bucket | The Amazon S3 bucket name to which the trust bundle is uploaded. | Yes. | | | object_key | The object key inside the bucket. | Yes. | | | format | Format in which the trust bundle is stored, &lt;spiffe &vert; jwks &vert; pem&gt;. See for more details. | Yes. | | The following bundle formats are supported: The trust bundle is represented as an RFC 7517 compliant JWK Set, with the specific parameters defined in the . Both the JWT authorities and the X.509 authorities are included. The trust bundle is encoded as an RFC 7517 compliant JWK Set, omitting SPIFFE-specific parameters. Both the JWT authorities and the X.509 authorities are included. The trust bundle is formatted using PEM encoding. Only the X.509 authorities are included. The user or role identified by the configured credentials must have the `s3:PutObject` IAM permissions. The following configuration uploads the local trust bundle contents to the `example.org` object in the `spire-trust-bundle` bucket. The AWS access key id and secret access key are obtained from the AWSACCESSKEYID and AWSSECRET_ACCESSKEY environment variables. ```hcl BundlePublisher "aws_s3" { plugin_data { region = "us-east-1" bucket = "spire-trust-bundle" object_key = "example.org" format = "spiffe" } } ```
Project: CyberArk Conjur (Provisioning / Key Management)
File: UPGRADING.md

This section describes how to upgrade a Conjur Server. The following steps describe a standard upgrade of the Conjur server, when deployed using Docker Compose. These steps assume you have defined your Conjur image in a service named `conjur`, and that you have access to the Conjur data key that was used when you originally deployed your Conjur server. In a local terminal session, set the `CONJURDATAKEY` environment variable: ``` export CONJURDATAKEY=<Conjur data key content> ``` Note: Information regarding the Conjur data key can be in this . Edit the Conjur image version in `docker-compose.yml` to reference the new version. Pull the new Conjur image version: ``` docker compose pull conjur ``` Stop the Conjur container: ``` docker compose stop conjur ``` Bring up the Conjur service using the new image version without changing linked services: ``` docker compose up -d --no-deps conjur ``` View Docker containers and verify all are healthy, up and running: ``` docker compose ps -a ``` It may also be useful to check if Conjur started successfully, which can be done by running ``` $ docker compose exec conjur conjurctl wait Waiting for Conjur to be ready... ... Conjur is ready! ``` If Conjur does not report as ready please read the . If you run through the steps above without setting the `CONJURDATAKEY` environment variable first, you will be able to complete the steps without an visible/explicit error message, but the logs of the new Conjur container will show an error like: ``` $ docker compose logs conjur_server rake aborted! No CONJURDATAKEY ... ``` To fix this, set the `CONJURDATAKEY` environment variable and run through the again. This time when you check the logs of the Conjur server container you should see the service starting as expected: ``` $ docker compose logs conjur_server ... => Booting Puma => Rails 5.2.4.3 application starting in production => Run `rails server -h` for more startup options [10] Puma starting in cluster mode... [10] * Version 3.12.6 (ruby 2.5.1-p57), codename: Llamas in Pajamas [10] * Min threads: 5, max threads: 5 [10] * Environment: development [10] * Process workers: 2 [10] * Preloading application [10] * Listening on tcp://0.0.0.0:80 [10] Use Ctrl-C to stop [10] - Worker 0 (pid: 26) booted, phase: 0 [10] - Worker 1 (pid: 30) booted, phase: 0 ``` When upgrading to version `1.9.0` and above, please ensure that you also upgrade your to at least `v5.3.4`. The Ruby client changed to accommodate the changes in the REST API that were made in response to this . Upgrading from versions `1.7.4` and below to versions `1.8.0` and `1.8.1` Starting in version `1.8.0`, the hashing algorithm used to fingerprint and identify encryption keys was changed from MD5 to a more secure SHA256. This fingerprint is stored in the Postgres database and must be updated to ensure a seamless upgrade. However, the does not address this fingerprint update in both version `1.8.0` and `1.8.1`. A database migration, which addresses this fingerprint update, is added in version `1.9.0`. Upgrade directly to versions `1.9.0` and above.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-pod.1.md

% podman-pod 1 podman\-pod - Management tool for groups of containers, called pods podman pod subcommand podman pod is a set of subcommands that manage pods, or groups of containers. | Command | Man Page | Description | | - | - | | | clone | | Create a copy of an existing pod. | | create | | Create a new pod. | | exists | | Check if a pod exists in local storage. | | inspect | | Display information describing a pod. | | kill | | Kill the main process of each container in one or more pods. | | logs | | Display logs for pod with one or more containers. | | pause | | Pause one or more pods. | | prune | | Remove all stopped pods and their containers. | | ps | | Print out information about pods. | | restart | | Restart one or more pods. | | rm | | Remove one or more stopped pods and containers. | | start | | Start one or more pods. | | stats | | Display a live stream of resource usage stats for containers in one or more pods. | | stop | | Stop one or more pods. | | top | | Display the running processes of containers in a pod. | | unpause | | Unpause one or more pods. | July 2018, Originally compiled by Peter Hunt <pehunt@redhat.com>