cwielenb/CNCF-Dataset huggingface dataset:
Project: ClickHouse (App Definition and Development / Database)
File: v23.1.6.42-stable.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Use sccache as a replacement for ccache and using S3 as cache backend. (). Backported in : The `clickhouse/clickhouse-keeper` image used to be pushed only with tags `-alpine`, e.g. `latest-alpine`. As it was suggested in https://github.com/ClickHouse/examples/pull/2, now it will be pushed as suffixless too. (). Fix changing an expired role (). Fix bug in zero-copy replication disk choice during fetch (). Fix NOT_IMPLEMENTED error with CROSS JOIN and algorithm = auto (). Disable logical expression optimizer for expression with aliases. (). Fix query parameters (). Parameterized view bug fix 47287 47247 (). Fix wait for zero copy lock during move (). Hotfix for too verbose warnings in HTTP (). Better error messages in ReplicatedMergeTreeAttachThread (). Fix `00933testfixextraseekoncompressed_cache` in releases. (). Add a fuse for backport branches w/o a created PR (). Only valid Reviews.STATES overwrite existing reviews (). Place short return before big block, improve logging (). Artifacts s3 prefix (). Fix tsan error lock-order-inversion ().
Project: Meshery (Provisioning / Automation & Configuration)
File: aws-eventbridge-controller.md

layout: integration title: AWS EventBridge subtitle: Collaborative and visual infrastructure as code for AWS EventBridge image: /assets/img/integrations/aws-eventbridge-controller/icons/color/aws-eventbridge-controller-color.svg permalink: extensibility/integrations/aws-eventbridge-controller docURL: https://docs.meshery.io/extensibility/integrations/aws-eventbridge-controller description: integrations-category: App Definition and Development integrations-subcategory: Streaming & Messaging registrant: GitHub components: name: archive colorIcon: assets/img/integrations/aws-eventbridge-controller/components/archive/icons/color/archive-color.svg whiteIcon: assets/img/integrations/aws-eventbridge-controller/components/archive/icons/white/archive-white.svg description: name: endpoint colorIcon: assets/img/integrations/aws-eventbridge-controller/components/endpoint/icons/color/endpoint-color.svg whiteIcon: assets/img/integrations/aws-eventbridge-controller/components/endpoint/icons/white/endpoint-white.svg description: name: event-bus colorIcon: assets/img/integrations/aws-eventbridge-controller/components/event-bus/icons/color/event-bus-color.svg whiteIcon: assets/img/integrations/aws-eventbridge-controller/components/event-bus/icons/white/event-bus-white.svg description: name: field-export colorIcon: assets/img/integrations/aws-eventbridge-controller/components/field-export/icons/color/field-export-color.svg whiteIcon: assets/img/integrations/aws-eventbridge-controller/components/field-export/icons/white/field-export-white.svg description: name: rule colorIcon: assets/img/integrations/aws-eventbridge-controller/components/rule/icons/color/rule-color.svg whiteIcon: assets/img/integrations/aws-eventbridge-controller/components/rule/icons/white/rule-white.svg description: name: adopted-resource colorIcon: assets/img/integrations/aws-eventbridge-controller/components/adopted-resource/icons/color/adopted-resource-color.svg whiteIcon: assets/img/integrations/aws-eventbridge-controller/components/adopted-resource/icons/white/adopted-resource-white.svg description: featureList: [ "Amazon EventBridge Event Bus is a serverless event bus that helps you receive, filter, transform, route, and deliver events.", "Amazon EventBridge Pipes is a serverless point-to-point integration resource that helps you connect event producers to event consumers with optional filtering, enrichment, and transformation capabilities.", "Use Amazon EventBridge Scheduler to schedule tasks and events at scale." ] 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: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-rmi.1.md

% podman-rmi 1 podman\-rmi - Remove one or more locally stored images podman rmi [options] image [...] podman image rm [options] image [...] Removes one or more locally stored images. Passing an argument image deletes it, along with any of its dangling parent images. A dangling image is an image without a tag and without being referenced by another image. Note: To delete an image from a remote registry, use the command. Some registries do not allow users to delete an image via a CLI remotely. Remove all images in the local storage. This option causes Podman to remove all containers that are using the image before removing the image from the system. If a specified image does not exist in the local storage, ignore it and do not throw an error. This option does not remove dangling parents of the specified image. Remove an image by its short ID ``` $ podman rmi c0ed59d05ff7 ``` Remove an image and its associated containers. ``` $ podman rmi --force imageID ``` Remove multiple images by their shortened IDs. ``` $ podman rmi c4dfb1609ee2 93fd78260bd1 c0ed59d05ff7 ``` Remove all images and containers. ``` $ podman rmi -a -f ``` Remove an absent image with and without the `--ignore` flag. ``` $ podman rmi --ignore nothing $ podman rmi nothing Error: nothing: image not known ``` 0 All specified images removed 1 One of the specified images did not exist, and no other failures 2 One of the specified images has child images or is being used by a container 125 The command fails for any other reason , March 2017, Originally compiled by Dan Walsh <dwalsh@redhat.com>
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: until.md

Show logs until TIMESTAMP. The --until option can be Unix timestamps, date formatted timestamps, or Go duration strings (e.g. 10m, 1h30m) computed relative to the client machine's time. Supported formats for date formatted time stamps include RFC3339Nano, RFC3339, 2006-01-02T15:04:05, 2006-01-02T15:04:05.999999999, 2006-01-02Z07:00, and 2006-01-02.
Project: KICS (Provisioning / Security & Compliance)
File: d6fae5b6-ada9-46c0-8b36-3108a2a2f77b.md

title: PostgreSQL Logging Of Temporary Files Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d6fae5b6-ada9-46c0-8b36-3108a2a2f77b Query name: PostgreSQL Logging Of Temporary Files Disabled Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: PostgreSQL database 'logtempfiles' flag isn't set to '0'<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10" name: sql_instance google.cloud.gcpsqlinstance: auth_kind: serviceaccount databaseversion: SQLSERVER13_1 name: "{{ resource_name }}-2" project: test_project region: us-central1 serviceaccountfile: /tmp/auth.pem settings: database_flags: name: logtempfiles value: 1 tier: db-n1-standard-1 state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: sql_instance google.cloud.gcpsqlinstance: auth_kind: serviceaccount databaseversion: SQLSERVER13_1 name: '{{ resource_name }}-2' project: test_project region: us-central1 serviceaccountfile: /tmp/auth.pem settings: database_flags: name: logtempfiles value: 0 tier: db-n1-standard-1 state: present ```
Project: userver (App Definition and Development / Streaming & Messaging)
File: security_changelog.md

Problem type: Stack-based Buffer Overflow Description: The json parsing functionality in userver before allows attackers to cause a stack overflow via crafted HTTP request. Credits: Problem type: Uncontrolled Resource Consumption Description: The hash functionality in userver before allows attackers to cause a denial of service via crafted HTTP request, involving collisions. Credits: Problem type: Uncontrolled Resource Consumption Description: The hash functionality in userver before allows attackers to cause a denial of service via crafted HTTP request, involving collisions. Credits:
Project: YugabyteDB (App Definition and Development / Database)
File: ysql-aiopg.md

title: Build a Python application that uses YSQL and aiopg headerTitle: Build a Python application linkTitle: Python description: Build a sample Python application with aiopg that uses YSQL. menu: v2.14: parent: build-apps name: Python identifier: python-aiopg weight: 553 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="{{< relref "./ysql-psycopg2.md" >}}" class="nav-link"> <i class="icon-postgres" aria-hidden="true"></i> YSQL - psycopg2 </a> </li> <li > <a href="{{< relref "./ysql-aiopg.md" >}}" class="nav-link active"> <i class="icon-postgres" aria-hidden="true"></i> YSQL - aiopg </a> </li> <li > <a href="{{< relref "./ysql-sqlalchemy.md" >}}" class="nav-link"> <i class="icon-postgres" aria-hidden="true"></i> YSQL - SQL Alchemy </a> </li> <li> <a href="{{< relref "./ycql.md" >}}" class="nav-link"> <i class="icon-cassandra" aria-hidden="true"></i> YCQL </a> </li> <li> <a href="{{< relref "./ysql-django.md" >}}" class="nav-link"> <i class="icon-postgres" aria-hidden="true"></i> YSQL - Django </a> </li> </ul> The following tutorial creates a simple Python application that connects to a YugabyteDB cluster using the `aiopg` database adapter, performs a few basic database operations creating a table, inserting data, and running a SQL query and prints the results to the screen. This tutorial assumes that you have satisfied the following prerequisites. YugabyteDB is up and running. If you are new to YugabyteDB, you can have YugabyteDB up and running within five minutes by following the steps in . Python 3, or later, is installed. package is installed. To install the package using `pip3` run: ```sh $ pip3 install aiopg ``` For details about using this database adapter, see . Create a file `yb-sql-helloworld.py` and add the following content to it. ```python import asyncio import aiopg dsn = 'dbname=yugabyte user=yugabyte password=yugabyte host=127.0.0.1 port=5433' async def go(): async with aiopg.create_pool(dsn) as pool: async with pool.acquire() as conn: async with conn.cursor() as cur: await cur.execute(f""" DROP TABLE IF EXISTS employee; CREATE TABLE employee (id int PRIMARY KEY, name varchar, age int, language varchar); """) print("Created table employee") await cur.execute("INSERT INTO employee (id, name, age, language) VALUES (%s, %s, %s, %s)", (1, 'John', 35, 'Python')) print("Inserted (id, name, age, language) = (1, 'John', 35, 'Python')") await cur.execute("SELECT name, age, language FROM employee WHERE id = 1") async for row in cur: print("Query returned: %s, %s, %s" % (row[0], row[1], row[2])) loop = asyncio.geteventloop() loop.rununtilcomplete(go()) ``` To use the application, run the following Python script you just created. ```sh $ python yb-sql-helloworld.py ``` You should see the following output. ```output Created table employee Inserted (id, name, age, language) = (1, 'John', 35, 'Python') Query returned: John, 35, Python ```
Project: KICS (Provisioning / Security & Compliance)
File: 7c81d34c-8e5a-402b-9798-9f442630e678.md

title: Image Without Digest hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7c81d34c-8e5a-402b-9798-9f442630e678 Query name: Image Without Digest Platform: Kubernetes Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: Images should be specified together with their digests to ensure integrity<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8" apiVersion: v1 kind: Pod metadata: name: private-image-test-1 spec: containers: name: uses-private-image image: $PRIVATEIMAGENAME imagePullPolicy: Always command: [ "echo", "SUCCESS" ] ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: private-image-test-1 spec: containers: name: uses-private-image image: image@sha256:45b23dee08af5e43a7fea6c4cf9c25ccf269ee113168c19722f87876677c5cb imagePullPolicy: Always command: [ "echo", "SUCCESS" ] ```
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: backstage.md

title: Backstage labels: category: authorization layer: application software: backstage inventors: petermacdonald tutorials: https://github.com/Parsifal-M/backstage-opa-plugins/blob/main/plugins/permission-backend-module-opa-wrapper/README.md code: https://github.com/Parsifal-M/backstage-opa-plugins/tree/main/plugins/permission-backend-module-opa-wrapper This integration is a plugin that acts as a wrapper around the Backstage permissions system, allowing you to use OPA to enforce permissions!
Project: YugabyteDB (App Definition and Development / Database)
File: hvals.md

title: HVALS linkTitle: HVALS description: HVALS menu: preview: parent: api-yedis weight: 2200 aliases: /preview/api/redis/hvals /preview/api/yedis/hvals type: docs `HVALS key` This command selects all the values in the hash that is associated with the given `key`. If the `key` does not exist, an empty list is returned. if the `key` is associated with a non-hash data, an error is raised. Returns list of values in the specified hash. ```sh $ HMSET yugahash area1 "America" area2 "Africa" ``` ``` "OK" ``` ```sh $ HVALS yugahash ``` ``` 1) "America" 2) "Africa" ``` , , , , , , , , , ,
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.3.18.md

layout: release date: 2020-07-04 tag: v0.3.18 language: en Mesheryctl `mesheryctl version` now retrieves server version information, including release tag and git sha. `meshery perf` now supports SPMS as a package through the `--file` flag. Meshery Extensibility enhancement: an abstract interface, Load Generator Interface, is now provided for ease of extending Meshery to support other load generators, like Nighthawk. Docs uplifted EKS and GKE instructions
Project: KICS (Provisioning / Security & Compliance)
File: 7c98538a-81c6-444b-bf04-e60bc3ceeec0.md

title: IP Forwarding Enabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7c98538a-81c6-444b-bf04-e60bc3ceeec0 Query name: IP Forwarding Enabled Platform: GoogleDeploymentManager Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: Instances must not have IP forwarding enabled, which means the attribute 'canIpForward' must not be true<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="16" resources: name: vm-template type: compute.v1.instance properties: zone: us-central1-a machineType: zones/us-central1-a/machineTypes/n1-standard-1 disks: deviceName: boot type: PERSISTENT boot: true autoDelete: true initializeParams: sourceImage: projects/debian-cloud/global/images/family/debian-9 networkInterfaces: network: global/networks/default canIpForward: true ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: vm-template2 type: compute.v1.instance properties: zone: us-central1-a machineType: zones/us-central1-a/machineTypes/n1-standard-1 disks: deviceName: boot type: PERSISTENT boot: true autoDelete: true initializeParams: sourceImage: projects/debian-cloud/global/images/family/debian-9 networkInterfaces: network: global/networks/default canIpForward: false ```
Project: kpt (Provisioning / Automation & Configuration)
File: 03-handling-dependencies.md

Sometimes resources within a package have dependencies that require one resource to be applied and reconciled before another resource. For example, a package that includes both Wordpress and MySQL might require that the MySQL `StatefulSet` is running before the Wordpress `Deployment` is started. In kpt, this is supported by declaring dependencies with the `config.kubernetes.io/depends-on` annotation. Let's take a look at the `wordpress-with-dependencies` package, a modified version of the `wordpress` package used earlier: ```shell $ kpt pkg get https://github.com/GoogleContainerTools/kpt.git/package-examples/wordpress-with-dependencies@v0.1 ``` You can see that the resources belonging to wordpress have the `depends-on` annotation referencing the MySQL `StatefulSet`: ```yaml apiVersion: apps/v1 kind: Deployment metadata: name: wordpress namespace: default labels: app: wordpress annotations: config.kubernetes.io/depends-on: apps/namespaces/default/StatefulSet/wordpress-mysql ``` The syntax for the resource references are: For namespaced resources: `<group>/namespaces/<namespace>/<kind>/<name>` For cluster-scoped resources: `<group>/<kind>/<name>` Before you can deploy the package, you need to initialize it and create a `Secret` containing the mysql password: ```shell $ kpt live init wordpress-with-dependencies initializing Kptfile inventory info (namespace: default)...success $ kubectl create secret generic mysql-pass --from-literal=password=YOUR_PASSWORD ``` You can deploy the package just like other packages. You can see that the MySQL `StatefulSet` and `Service` are created and reconciled before the Wordpress `Deployment` and `Service` are applied. ```shell $ kpt live apply wordpress-with-dependencies --reconcile-timeout=2m service/wordpress-mysql created statefulset.apps/wordpress-mysql created service/wordpress-mysql reconcile pending statefulset.apps/wordpress-mysql reconcile pending service/wordpress-mysql reconciled statefulset.apps/wordpress-mysql reconciled service/wordpress created deployment.apps/wordpress created 4 resource(s) applied. 4 created, 0 unchanged, 0 configured, 0 failed service/wordpress reconcile pending deployment.apps/wordpress reconcile pending service/wordpress reconciled deployment.apps/wordpress reconciled 4 resource(s) reconciled, 0 skipped, 0 failed to reconcile, 0 timed out ``` When you delete the package from the cluster, you can see that resources are deleted in reverse order: ```shell $ kpt live destroy wordpress-with-dependencies deployment.apps/wordpress deleted service/wordpress deleted deployment.apps/wordpress reconciled service/wordpress reconciled statefulset.apps/wordpress-mysql deleted service/wordpress-mysql deleted 4 resource(s) deleted, 0 skipped, 0 failed to delete statefulset.apps/wordpress-mysql reconcile pending service/wordpress-mysql reconcile pending statefulset.apps/wordpress-mysql reconciled service/wordpress-mysql reconciled 4 resource(s) reconciled, 0 skipped, 0 failed to reconcile, 0 timed out ``` See [depends-on] for more information.
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: ARC-003-grpc-protobuf-coding-convention.md

Proposed We have defined gRPC services and protobuf messages without convention, which results in the duplicated protobuf definitions and inconsistent names of services and messages. Thus, this record defines the minimum-level coding convention for Protobuf message to improve the quality of grpc/protobuf message definitions. Use `google.protobuf.Any` data field only if the message field conveys serialized protobuf message with type url. Otherwise, use the explicit data type or protobuf message. Use `Request` suffix for gRPC request message name and `Response` suffix for gRPC response message name Do not use `Client` and `Service` suffix for gRPC service name e.g. (x) DaprClient, DaprService Avoid the duplicated protobuf message definitions by defining the messages in shared proto Define and use enum type if field accepts only predefined values. This allows us to define the consistent, readable gRPC service and protobuf message.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: yaml.md

+++ title = "yaml resource" draft = false gh_repo = "inspec" platform = "os" [menu] [menu.inspec] title = "yaml" identifier = "inspec/resources/os/yaml.md yaml resource" parent = "inspec/resources/os" +++ Use the `yaml` Chef InSpec audit resource to test configuration data in a Yaml file. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `yaml` resource block declares the configuration data to be tested. Assume the following Yaml file: name: foo array: zero one This file can be queried using: describe yaml('filename.yml') do its('name') { should eq 'foo' } its(['array', 1]) { should eq 'one' } end where `name` is a configuration setting in a Yaml file `should eq 'foo'` tests a value of `name` as read from a Yaml file versus the value declared in the test Like the `json` resource, the `yaml` resource can read a file, run a command, or accept content inline: describe yaml('config.yaml') do its(['driver', 'name']) { should eq 'vagrant' } end describe yaml({ command: 'retrieve_data.py --yaml' }) do its('state') { should eq 'open' } end describe yaml({ content: "\"key1: value1\nkey2: value2\"" }) do its('key2') { should cmp 'value2' } end The following examples show how to use this Chef InSpec audit resource. describe yaml('.kitchen.yaml') do its(['driver','name']) { should eq('vagrant') } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The `name` matcher tests the value of `name` as read from a Yaml file versus the value declared in the test: its('name') { should eq 'foo' }
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-machine-os.1.md

% podman-machine-os 1 podman\-machine\-os - Manage a Podman virtual machine's OS podman machine os subcommand `podman machine os` is a set of subcommands that manage a Podman virtual machine's operating system. | Command | Man Page | Description | ||--|-| | apply | | Apply an OCI image to a Podman Machine's OS | , , February 2023, Originally compiled by Ashley Cui <acui@redhat.com>