all:
  children:
    zuul_unreachable:
      hosts: {}
  hosts:
    ubuntu-noble:
      ansible_connection: ssh
      ansible_host: 162.253.55.82
      ansible_port: 22
      ansible_python_interpreter: auto
      ansible_user: zuul
      nodepool:
        az: yul2
        cloud: public
        external_id: c3bd67b7-ee34-4f62-a0d8-739341ba11e3
        host_id: 2192bc2b1209c5480c3ec667dceeb335e063a02ae8475d748c2e77e2
        interface_ip: 162.253.55.82
        label: ubuntu-noble
        node_properties: {}
        private_ipv4: 162.253.55.82
        private_ipv6: null
        provider: yul1
        public_ipv4: 162.253.55.82
        public_ipv6: 2604:e100:1:0:f816:3eff:feab:dc4a
        region: ca-ymq-1
        slot: null
      zuul_node:
        az: yul2
        cloud: public
        external_id: c3bd67b7-ee34-4f62-a0d8-739341ba11e3
        host_id: 2192bc2b1209c5480c3ec667dceeb335e063a02ae8475d748c2e77e2
        interface_ip: 162.253.55.82
        label: ubuntu-noble
        node_properties: {}
        private_ipv4: 162.253.55.82
        private_ipv6: null
        provider: yul1
        public_ipv4: 162.253.55.82
        public_ipv6: 2604:e100:1:0:f816:3eff:feab:dc4a
        region: ca-ymq-1
        slot: null
        uuid: null
  vars:
    zuul:
      _inheritance_path:
      - '<Job base explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: vexxhost/zuul-config/zuul.d/jobs.yaml@main#1>'
      - '<Job ansible-test explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: vexxhost/zuul-jobs/zuul.d/ansible-jobs.yaml@main#25>'
      - '<Job ansible-test explicit: None implied: None source: vexxhost/ansible-collection-kubernetes/.zuul.yaml@main#209>'
      ansible_version: '9'
      attempts: 1
      branch: main
      build: ffb15e78eae64ebdab4701b68b6813de
      build_refs:
      - branch: main
        change: '319'
        change_message: "feat(cluster_api): manage clusterctl add-on providers\n\nThe
          `cluster_api` role can only install the core, bootstrap, control plane and
          infrastructure providers, and each one is hard coded in four places: the
          clusterctl config, `clusterctl init`, `clusterctl upgrade apply` and the
          node selector patch. Running another controller next to Cluster API, such
          as [cluster-api-csr-approver](https://github.com/vexxhost/cluster-api-csr-approver),
          would mean writing another role with its own install path, the way ORC works
          today.\n\nThis adds `cluster_api_addon_providers`, which hands clusterctl
          add-on providers to clusterctl like the other providers:\n\n```yaml\ncluster_api_addon_providers:\n
          \ - name: csr-approver\n    version: 0.1.0\n```\n\nAll providers are now
          described once in `vars/main.yml`. The role compares them with the `Provider`
          objects in the cluster, then runs one `clusterctl upgrade apply` for the
          outdated ones and one `clusterctl init` for the missing ones. Upgrades run
          first, so a new add-on is validated against the target Cluster API contract.
          This also means:\n\n- An add-on, or any provider, can be added to an existing
          management cluster. Before, `init` only ran when no providers existed. clusterctl
          refuses to `init` a provider that is already installed, so only the missing
          ones are passed.\n- Upgrade namespaces come from the installed `Provider`
          objects instead of being hard coded, and only the providers whose version
          changed are upgraded.\n- `cluster_api_node_selector` is applied to every
          provider Deployment found by the `cluster.x-k8s.io/provider` label that
          clusterctl sets, which covers add-ons too.\n- Add-on variables and image
          overrides use the existing `clusterctl_config`, for example `images: {addon-csr-approver/cluster-api-csr-approver:
          ...}`.\n\ncluster-api-csr-approver v0.1.0 is bundled under `files/providers/addon-csr-approver/v0.1.0`
          so offline installs keep working. An entry can set `url` to use an add-on
          that isn't bundled. The default stays `[]`, so nothing changes for current
          users.\n\n### Where the CSR approver gets enabled\n\nAtmosphere should enable
          it, in `roles/magnum/meta/main.yml`. This collection only provides the mechanism
          and the bundled manifests:\n\n- It requires the v1beta2 contract (Cluster
          API 1.11+). This role still supports Cluster API releases back to 1.3, so
          turning it on by default would break those users.\n- It is only needed once
          magnum-cluster-api turns on `serverTLSBootstrap` and `--kubelet-certificate-authority`.
          Atmosphere pins the driver, so it can ship the approver in the same release.\n-
          Atmosphere already mirrors images through `atmosphere_images` and `magnum_clusterctl_config`,
          and that's where the approver image override belongs.\n- With its default
          selector it connects to every workload cluster, which this collection shouldn't
          impose on everyone.\n\nThe Atmosphere change after this is released:\n\n```yaml\ncluster_api_addon_providers:\n
          \ - name: csr-approver\n    version: 0.1.0\n```\n\nIt also needs an `addon-csr-approver/cluster-api-csr-approver`
          entry in `magnum_clusterctl_config.images`, backed by a new `atmosphere_images`
          key.\n\n### Testing\n\n- The `cluster-api` molecule job now installs the
          approver. Verify checks that its Deployment is ready, its `Provider` version
          is correct, and every provider Deployment has the node selector.\n- The
          role was run with ansible-core 2.17 and 2.20 against stubbed Kubernetes
          modules and a fake `clusterctl`, to check the generated commands:\n\n| Cluster
          state | Commands |\n|---|---|\n| Empty | `init` with all four providers
          plus `--addon csr-approver:v0.1.0` |\n| Providers current, add-on missing
          | `init --addon csr-approver:v0.1.0` |\n| Older CAPI and add-on | `upgrade
          apply` for core, bootstrap, control plane and `capi-csr-approver-system/csr-approver`
          |\n| Older CAPI, add-on missing | `upgrade apply`, then `init --addon` |\n|
          Everything current | no clusterctl calls |\n\n- `yamllint` and `ansible-lint`
          25.6.1 pass.\n\nRelated: Zendesk 370181.\n"
        change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/319
        commit_id: ddd72174ad5b177ee278122335d00af3544b744d
        patchset: ddd72174ad5b177ee278122335d00af3544b744d
        project:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/ansible-collection-kubernetes
          name: vexxhost/ansible-collection-kubernetes
          short_name: ansible-collection-kubernetes
          src_dir: src/github.com/vexxhost/ansible-collection-kubernetes
        src_dir: src/github.com/vexxhost/ansible-collection-kubernetes
        topic: null
      buildset: 1ab0bcc081934a1386095c935426ca8e
      buildset_refs:
      - branch: main
        change: '319'
        change_message: "feat(cluster_api): manage clusterctl add-on providers\n\nThe
          `cluster_api` role can only install the core, bootstrap, control plane and
          infrastructure providers, and each one is hard coded in four places: the
          clusterctl config, `clusterctl init`, `clusterctl upgrade apply` and the
          node selector patch. Running another controller next to Cluster API, such
          as [cluster-api-csr-approver](https://github.com/vexxhost/cluster-api-csr-approver),
          would mean writing another role with its own install path, the way ORC works
          today.\n\nThis adds `cluster_api_addon_providers`, which hands clusterctl
          add-on providers to clusterctl like the other providers:\n\n```yaml\ncluster_api_addon_providers:\n
          \ - name: csr-approver\n    version: 0.1.0\n```\n\nAll providers are now
          described once in `vars/main.yml`. The role compares them with the `Provider`
          objects in the cluster, then runs one `clusterctl upgrade apply` for the
          outdated ones and one `clusterctl init` for the missing ones. Upgrades run
          first, so a new add-on is validated against the target Cluster API contract.
          This also means:\n\n- An add-on, or any provider, can be added to an existing
          management cluster. Before, `init` only ran when no providers existed. clusterctl
          refuses to `init` a provider that is already installed, so only the missing
          ones are passed.\n- Upgrade namespaces come from the installed `Provider`
          objects instead of being hard coded, and only the providers whose version
          changed are upgraded.\n- `cluster_api_node_selector` is applied to every
          provider Deployment found by the `cluster.x-k8s.io/provider` label that
          clusterctl sets, which covers add-ons too.\n- Add-on variables and image
          overrides use the existing `clusterctl_config`, for example `images: {addon-csr-approver/cluster-api-csr-approver:
          ...}`.\n\ncluster-api-csr-approver v0.1.0 is bundled under `files/providers/addon-csr-approver/v0.1.0`
          so offline installs keep working. An entry can set `url` to use an add-on
          that isn't bundled. The default stays `[]`, so nothing changes for current
          users.\n\n### Where the CSR approver gets enabled\n\nAtmosphere should enable
          it, in `roles/magnum/meta/main.yml`. This collection only provides the mechanism
          and the bundled manifests:\n\n- It requires the v1beta2 contract (Cluster
          API 1.11+). This role still supports Cluster API releases back to 1.3, so
          turning it on by default would break those users.\n- It is only needed once
          magnum-cluster-api turns on `serverTLSBootstrap` and `--kubelet-certificate-authority`.
          Atmosphere pins the driver, so it can ship the approver in the same release.\n-
          Atmosphere already mirrors images through `atmosphere_images` and `magnum_clusterctl_config`,
          and that's where the approver image override belongs.\n- With its default
          selector it connects to every workload cluster, which this collection shouldn't
          impose on everyone.\n\nThe Atmosphere change after this is released:\n\n```yaml\ncluster_api_addon_providers:\n
          \ - name: csr-approver\n    version: 0.1.0\n```\n\nIt also needs an `addon-csr-approver/cluster-api-csr-approver`
          entry in `magnum_clusterctl_config.images`, backed by a new `atmosphere_images`
          key.\n\n### Testing\n\n- The `cluster-api` molecule job now installs the
          approver. Verify checks that its Deployment is ready, its `Provider` version
          is correct, and every provider Deployment has the node selector.\n- The
          role was run with ansible-core 2.17 and 2.20 against stubbed Kubernetes
          modules and a fake `clusterctl`, to check the generated commands:\n\n| Cluster
          state | Commands |\n|---|---|\n| Empty | `init` with all four providers
          plus `--addon csr-approver:v0.1.0` |\n| Providers current, add-on missing
          | `init --addon csr-approver:v0.1.0` |\n| Older CAPI and add-on | `upgrade
          apply` for core, bootstrap, control plane and `capi-csr-approver-system/csr-approver`
          |\n| Older CAPI, add-on missing | `upgrade apply`, then `init --addon` |\n|
          Everything current | no clusterctl calls |\n\n- `yamllint` and `ansible-lint`
          25.6.1 pass.\n\nRelated: Zendesk 370181.\n"
        change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/319
        commit_id: ddd72174ad5b177ee278122335d00af3544b744d
        patchset: ddd72174ad5b177ee278122335d00af3544b744d
        project:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/ansible-collection-kubernetes
          name: vexxhost/ansible-collection-kubernetes
          short_name: ansible-collection-kubernetes
          src_dir: src/github.com/vexxhost/ansible-collection-kubernetes
        src_dir: src/github.com/vexxhost/ansible-collection-kubernetes
        topic: null
      change: '319'
      change_message: "feat(cluster_api): manage clusterctl add-on providers\n\nThe
        `cluster_api` role can only install the core, bootstrap, control plane and
        infrastructure providers, and each one is hard coded in four places: the clusterctl
        config, `clusterctl init`, `clusterctl upgrade apply` and the node selector
        patch. Running another controller next to Cluster API, such as [cluster-api-csr-approver](https://github.com/vexxhost/cluster-api-csr-approver),
        would mean writing another role with its own install path, the way ORC works
        today.\n\nThis adds `cluster_api_addon_providers`, which hands clusterctl
        add-on providers to clusterctl like the other providers:\n\n```yaml\ncluster_api_addon_providers:\n
        \ - name: csr-approver\n    version: 0.1.0\n```\n\nAll providers are now described
        once in `vars/main.yml`. The role compares them with the `Provider` objects
        in the cluster, then runs one `clusterctl upgrade apply` for the outdated
        ones and one `clusterctl init` for the missing ones. Upgrades run first, so
        a new add-on is validated against the target Cluster API contract. This also
        means:\n\n- An add-on, or any provider, can be added to an existing management
        cluster. Before, `init` only ran when no providers existed. clusterctl refuses
        to `init` a provider that is already installed, so only the missing ones are
        passed.\n- Upgrade namespaces come from the installed `Provider` objects instead
        of being hard coded, and only the providers whose version changed are upgraded.\n-
        `cluster_api_node_selector` is applied to every provider Deployment found
        by the `cluster.x-k8s.io/provider` label that clusterctl sets, which covers
        add-ons too.\n- Add-on variables and image overrides use the existing `clusterctl_config`,
        for example `images: {addon-csr-approver/cluster-api-csr-approver: ...}`.\n\ncluster-api-csr-approver
        v0.1.0 is bundled under `files/providers/addon-csr-approver/v0.1.0` so offline
        installs keep working. An entry can set `url` to use an add-on that isn't
        bundled. The default stays `[]`, so nothing changes for current users.\n\n###
        Where the CSR approver gets enabled\n\nAtmosphere should enable it, in `roles/magnum/meta/main.yml`.
        This collection only provides the mechanism and the bundled manifests:\n\n-
        It requires the v1beta2 contract (Cluster API 1.11+). This role still supports
        Cluster API releases back to 1.3, so turning it on by default would break
        those users.\n- It is only needed once magnum-cluster-api turns on `serverTLSBootstrap`
        and `--kubelet-certificate-authority`. Atmosphere pins the driver, so it can
        ship the approver in the same release.\n- Atmosphere already mirrors images
        through `atmosphere_images` and `magnum_clusterctl_config`, and that's where
        the approver image override belongs.\n- With its default selector it connects
        to every workload cluster, which this collection shouldn't impose on everyone.\n\nThe
        Atmosphere change after this is released:\n\n```yaml\ncluster_api_addon_providers:\n
        \ - name: csr-approver\n    version: 0.1.0\n```\n\nIt also needs an `addon-csr-approver/cluster-api-csr-approver`
        entry in `magnum_clusterctl_config.images`, backed by a new `atmosphere_images`
        key.\n\n### Testing\n\n- The `cluster-api` molecule job now installs the approver.
        Verify checks that its Deployment is ready, its `Provider` version is correct,
        and every provider Deployment has the node selector.\n- The role was run with
        ansible-core 2.17 and 2.20 against stubbed Kubernetes modules and a fake `clusterctl`,
        to check the generated commands:\n\n| Cluster state | Commands |\n|---|---|\n|
        Empty | `init` with all four providers plus `--addon csr-approver:v0.1.0`
        |\n| Providers current, add-on missing | `init --addon csr-approver:v0.1.0`
        |\n| Older CAPI and add-on | `upgrade apply` for core, bootstrap, control
        plane and `capi-csr-approver-system/csr-approver` |\n| Older CAPI, add-on
        missing | `upgrade apply`, then `init --addon` |\n| Everything current | no
        clusterctl calls |\n\n- `yamllint` and `ansible-lint` 25.6.1 pass.\n\nRelated:
        Zendesk 370181.\n"
      change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/319
      child_jobs: []
      commit_id: ddd72174ad5b177ee278122335d00af3544b744d
      event_id: a3774eb0-d239-11f1-989c-b38501872372
      executor:
        hostname: 2d72f0692154
        inventory_file: /var/lib/zuul/builds/ffb15e78eae64ebdab4701b68b6813de/ansible/inventory.yaml
        log_root: /var/lib/zuul/builds/ffb15e78eae64ebdab4701b68b6813de/work/logs
        result_data_file: /var/lib/zuul/builds/ffb15e78eae64ebdab4701b68b6813de/work/results.json
        src_root: /var/lib/zuul/builds/ffb15e78eae64ebdab4701b68b6813de/work/src
        work_root: /var/lib/zuul/builds/ffb15e78eae64ebdab4701b68b6813de/work
      include_vars: []
      items:
      - branch: main
        change: '319'
        change_message: "feat(cluster_api): manage clusterctl add-on providers\n\nThe
          `cluster_api` role can only install the core, bootstrap, control plane and
          infrastructure providers, and each one is hard coded in four places: the
          clusterctl config, `clusterctl init`, `clusterctl upgrade apply` and the
          node selector patch. Running another controller next to Cluster API, such
          as [cluster-api-csr-approver](https://github.com/vexxhost/cluster-api-csr-approver),
          would mean writing another role with its own install path, the way ORC works
          today.\n\nThis adds `cluster_api_addon_providers`, which hands clusterctl
          add-on providers to clusterctl like the other providers:\n\n```yaml\ncluster_api_addon_providers:\n
          \ - name: csr-approver\n    version: 0.1.0\n```\n\nAll providers are now
          described once in `vars/main.yml`. The role compares them with the `Provider`
          objects in the cluster, then runs one `clusterctl upgrade apply` for the
          outdated ones and one `clusterctl init` for the missing ones. Upgrades run
          first, so a new add-on is validated against the target Cluster API contract.
          This also means:\n\n- An add-on, or any provider, can be added to an existing
          management cluster. Before, `init` only ran when no providers existed. clusterctl
          refuses to `init` a provider that is already installed, so only the missing
          ones are passed.\n- Upgrade namespaces come from the installed `Provider`
          objects instead of being hard coded, and only the providers whose version
          changed are upgraded.\n- `cluster_api_node_selector` is applied to every
          provider Deployment found by the `cluster.x-k8s.io/provider` label that
          clusterctl sets, which covers add-ons too.\n- Add-on variables and image
          overrides use the existing `clusterctl_config`, for example `images: {addon-csr-approver/cluster-api-csr-approver:
          ...}`.\n\ncluster-api-csr-approver v0.1.0 is bundled under `files/providers/addon-csr-approver/v0.1.0`
          so offline installs keep working. An entry can set `url` to use an add-on
          that isn't bundled. The default stays `[]`, so nothing changes for current
          users.\n\n### Where the CSR approver gets enabled\n\nAtmosphere should enable
          it, in `roles/magnum/meta/main.yml`. This collection only provides the mechanism
          and the bundled manifests:\n\n- It requires the v1beta2 contract (Cluster
          API 1.11+). This role still supports Cluster API releases back to 1.3, so
          turning it on by default would break those users.\n- It is only needed once
          magnum-cluster-api turns on `serverTLSBootstrap` and `--kubelet-certificate-authority`.
          Atmosphere pins the driver, so it can ship the approver in the same release.\n-
          Atmosphere already mirrors images through `atmosphere_images` and `magnum_clusterctl_config`,
          and that's where the approver image override belongs.\n- With its default
          selector it connects to every workload cluster, which this collection shouldn't
          impose on everyone.\n\nThe Atmosphere change after this is released:\n\n```yaml\ncluster_api_addon_providers:\n
          \ - name: csr-approver\n    version: 0.1.0\n```\n\nIt also needs an `addon-csr-approver/cluster-api-csr-approver`
          entry in `magnum_clusterctl_config.images`, backed by a new `atmosphere_images`
          key.\n\n### Testing\n\n- The `cluster-api` molecule job now installs the
          approver. Verify checks that its Deployment is ready, its `Provider` version
          is correct, and every provider Deployment has the node selector.\n- The
          role was run with ansible-core 2.17 and 2.20 against stubbed Kubernetes
          modules and a fake `clusterctl`, to check the generated commands:\n\n| Cluster
          state | Commands |\n|---|---|\n| Empty | `init` with all four providers
          plus `--addon csr-approver:v0.1.0` |\n| Providers current, add-on missing
          | `init --addon csr-approver:v0.1.0` |\n| Older CAPI and add-on | `upgrade
          apply` for core, bootstrap, control plane and `capi-csr-approver-system/csr-approver`
          |\n| Older CAPI, add-on missing | `upgrade apply`, then `init --addon` |\n|
          Everything current | no clusterctl calls |\n\n- `yamllint` and `ansible-lint`
          25.6.1 pass.\n\nRelated: Zendesk 370181.\n"
        change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/319
        commit_id: ddd72174ad5b177ee278122335d00af3544b744d
        patchset: ddd72174ad5b177ee278122335d00af3544b744d
        project:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/ansible-collection-kubernetes
          name: vexxhost/ansible-collection-kubernetes
          short_name: ansible-collection-kubernetes
          src_dir: src/github.com/vexxhost/ansible-collection-kubernetes
        topic: null
      job: ansible-test
      jobtags: []
      max_attempts: 3
      message: ZmVhdChjbHVzdGVyX2FwaSk6IG1hbmFnZSBjbHVzdGVyY3RsIGFkZC1vbiBwcm92aWRlcnMKClRoZSBgY2x1c3Rlcl9hcGlgIHJvbGUgY2FuIG9ubHkgaW5zdGFsbCB0aGUgY29yZSwgYm9vdHN0cmFwLCBjb250cm9sIHBsYW5lIGFuZCBpbmZyYXN0cnVjdHVyZSBwcm92aWRlcnMsIGFuZCBlYWNoIG9uZSBpcyBoYXJkIGNvZGVkIGluIGZvdXIgcGxhY2VzOiB0aGUgY2x1c3RlcmN0bCBjb25maWcsIGBjbHVzdGVyY3RsIGluaXRgLCBgY2x1c3RlcmN0bCB1cGdyYWRlIGFwcGx5YCBhbmQgdGhlIG5vZGUgc2VsZWN0b3IgcGF0Y2guIFJ1bm5pbmcgYW5vdGhlciBjb250cm9sbGVyIG5leHQgdG8gQ2x1c3RlciBBUEksIHN1Y2ggYXMgW2NsdXN0ZXItYXBpLWNzci1hcHByb3Zlcl0oaHR0cHM6Ly9naXRodWIuY29tL3ZleHhob3N0L2NsdXN0ZXItYXBpLWNzci1hcHByb3ZlciksIHdvdWxkIG1lYW4gd3JpdGluZyBhbm90aGVyIHJvbGUgd2l0aCBpdHMgb3duIGluc3RhbGwgcGF0aCwgdGhlIHdheSBPUkMgd29ya3MgdG9kYXkuCgpUaGlzIGFkZHMgYGNsdXN0ZXJfYXBpX2FkZG9uX3Byb3ZpZGVyc2AsIHdoaWNoIGhhbmRzIGNsdXN0ZXJjdGwgYWRkLW9uIHByb3ZpZGVycyB0byBjbHVzdGVyY3RsIGxpa2UgdGhlIG90aGVyIHByb3ZpZGVyczoKCmBgYHlhbWwKY2x1c3Rlcl9hcGlfYWRkb25fcHJvdmlkZXJzOgogIC0gbmFtZTogY3NyLWFwcHJvdmVyCiAgICB2ZXJzaW9uOiAwLjEuMApgYGAKCkFsbCBwcm92aWRlcnMgYXJlIG5vdyBkZXNjcmliZWQgb25jZSBpbiBgdmFycy9tYWluLnltbGAuIFRoZSByb2xlIGNvbXBhcmVzIHRoZW0gd2l0aCB0aGUgYFByb3ZpZGVyYCBvYmplY3RzIGluIHRoZSBjbHVzdGVyLCB0aGVuIHJ1bnMgb25lIGBjbHVzdGVyY3RsIHVwZ3JhZGUgYXBwbHlgIGZvciB0aGUgb3V0ZGF0ZWQgb25lcyBhbmQgb25lIGBjbHVzdGVyY3RsIGluaXRgIGZvciB0aGUgbWlzc2luZyBvbmVzLiBVcGdyYWRlcyBydW4gZmlyc3QsIHNvIGEgbmV3IGFkZC1vbiBpcyB2YWxpZGF0ZWQgYWdhaW5zdCB0aGUgdGFyZ2V0IENsdXN0ZXIgQVBJIGNvbnRyYWN0LiBUaGlzIGFsc28gbWVhbnM6CgotIEFuIGFkZC1vbiwgb3IgYW55IHByb3ZpZGVyLCBjYW4gYmUgYWRkZWQgdG8gYW4gZXhpc3RpbmcgbWFuYWdlbWVudCBjbHVzdGVyLiBCZWZvcmUsIGBpbml0YCBvbmx5IHJhbiB3aGVuIG5vIHByb3ZpZGVycyBleGlzdGVkLiBjbHVzdGVyY3RsIHJlZnVzZXMgdG8gYGluaXRgIGEgcHJvdmlkZXIgdGhhdCBpcyBhbHJlYWR5IGluc3RhbGxlZCwgc28gb25seSB0aGUgbWlzc2luZyBvbmVzIGFyZSBwYXNzZWQuCi0gVXBncmFkZSBuYW1lc3BhY2VzIGNvbWUgZnJvbSB0aGUgaW5zdGFsbGVkIGBQcm92aWRlcmAgb2JqZWN0cyBpbnN0ZWFkIG9mIGJlaW5nIGhhcmQgY29kZWQsIGFuZCBvbmx5IHRoZSBwcm92aWRlcnMgd2hvc2UgdmVyc2lvbiBjaGFuZ2VkIGFyZSB1cGdyYWRlZC4KLSBgY2x1c3Rlcl9hcGlfbm9kZV9zZWxlY3RvcmAgaXMgYXBwbGllZCB0byBldmVyeSBwcm92aWRlciBEZXBsb3ltZW50IGZvdW5kIGJ5IHRoZSBgY2x1c3Rlci54LWs4cy5pby9wcm92aWRlcmAgbGFiZWwgdGhhdCBjbHVzdGVyY3RsIHNldHMsIHdoaWNoIGNvdmVycyBhZGQtb25zIHRvby4KLSBBZGQtb24gdmFyaWFibGVzIGFuZCBpbWFnZSBvdmVycmlkZXMgdXNlIHRoZSBleGlzdGluZyBgY2x1c3RlcmN0bF9jb25maWdgLCBmb3IgZXhhbXBsZSBgaW1hZ2VzOiB7YWRkb24tY3NyLWFwcHJvdmVyL2NsdXN0ZXItYXBpLWNzci1hcHByb3ZlcjogLi4ufWAuCgpjbHVzdGVyLWFwaS1jc3ItYXBwcm92ZXIgdjAuMS4wIGlzIGJ1bmRsZWQgdW5kZXIgYGZpbGVzL3Byb3ZpZGVycy9hZGRvbi1jc3ItYXBwcm92ZXIvdjAuMS4wYCBzbyBvZmZsaW5lIGluc3RhbGxzIGtlZXAgd29ya2luZy4gQW4gZW50cnkgY2FuIHNldCBgdXJsYCB0byB1c2UgYW4gYWRkLW9uIHRoYXQgaXNuJ3QgYnVuZGxlZC4gVGhlIGRlZmF1bHQgc3RheXMgYFtdYCwgc28gbm90aGluZyBjaGFuZ2VzIGZvciBjdXJyZW50IHVzZXJzLgoKIyMjIFdoZXJlIHRoZSBDU1IgYXBwcm92ZXIgZ2V0cyBlbmFibGVkCgpBdG1vc3BoZXJlIHNob3VsZCBlbmFibGUgaXQsIGluIGByb2xlcy9tYWdudW0vbWV0YS9tYWluLnltbGAuIFRoaXMgY29sbGVjdGlvbiBvbmx5IHByb3ZpZGVzIHRoZSBtZWNoYW5pc20gYW5kIHRoZSBidW5kbGVkIG1hbmlmZXN0czoKCi0gSXQgcmVxdWlyZXMgdGhlIHYxYmV0YTIgY29udHJhY3QgKENsdXN0ZXIgQVBJIDEuMTErKS4gVGhpcyByb2xlIHN0aWxsIHN1cHBvcnRzIENsdXN0ZXIgQVBJIHJlbGVhc2VzIGJhY2sgdG8gMS4zLCBzbyB0dXJuaW5nIGl0IG9uIGJ5IGRlZmF1bHQgd291bGQgYnJlYWsgdGhvc2UgdXNlcnMuCi0gSXQgaXMgb25seSBuZWVkZWQgb25jZSBtYWdudW0tY2x1c3Rlci1hcGkgdHVybnMgb24gYHNlcnZlclRMU0Jvb3RzdHJhcGAgYW5kIGAtLWt1YmVsZXQtY2VydGlmaWNhdGUtYXV0aG9yaXR5YC4gQXRtb3NwaGVyZSBwaW5zIHRoZSBkcml2ZXIsIHNvIGl0IGNhbiBzaGlwIHRoZSBhcHByb3ZlciBpbiB0aGUgc2FtZSByZWxlYXNlLgotIEF0bW9zcGhlcmUgYWxyZWFkeSBtaXJyb3JzIGltYWdlcyB0aHJvdWdoIGBhdG1vc3BoZXJlX2ltYWdlc2AgYW5kIGBtYWdudW1fY2x1c3RlcmN0bF9jb25maWdgLCBhbmQgdGhhdCdzIHdoZXJlIHRoZSBhcHByb3ZlciBpbWFnZSBvdmVycmlkZSBiZWxvbmdzLgotIFdpdGggaXRzIGRlZmF1bHQgc2VsZWN0b3IgaXQgY29ubmVjdHMgdG8gZXZlcnkgd29ya2xvYWQgY2x1c3Rlciwgd2hpY2ggdGhpcyBjb2xsZWN0aW9uIHNob3VsZG4ndCBpbXBvc2Ugb24gZXZlcnlvbmUuCgpUaGUgQXRtb3NwaGVyZSBjaGFuZ2UgYWZ0ZXIgdGhpcyBpcyByZWxlYXNlZDoKCmBgYHlhbWwKY2x1c3Rlcl9hcGlfYWRkb25fcHJvdmlkZXJzOgogIC0gbmFtZTogY3NyLWFwcHJvdmVyCiAgICB2ZXJzaW9uOiAwLjEuMApgYGAKCkl0IGFsc28gbmVlZHMgYW4gYGFkZG9uLWNzci1hcHByb3Zlci9jbHVzdGVyLWFwaS1jc3ItYXBwcm92ZXJgIGVudHJ5IGluIGBtYWdudW1fY2x1c3RlcmN0bF9jb25maWcuaW1hZ2VzYCwgYmFja2VkIGJ5IGEgbmV3IGBhdG1vc3BoZXJlX2ltYWdlc2Aga2V5LgoKIyMjIFRlc3RpbmcKCi0gVGhlIGBjbHVzdGVyLWFwaWAgbW9sZWN1bGUgam9iIG5vdyBpbnN0YWxscyB0aGUgYXBwcm92ZXIuIFZlcmlmeSBjaGVja3MgdGhhdCBpdHMgRGVwbG95bWVudCBpcyByZWFkeSwgaXRzIGBQcm92aWRlcmAgdmVyc2lvbiBpcyBjb3JyZWN0LCBhbmQgZXZlcnkgcHJvdmlkZXIgRGVwbG95bWVudCBoYXMgdGhlIG5vZGUgc2VsZWN0b3IuCi0gVGhlIHJvbGUgd2FzIHJ1biB3aXRoIGFuc2libGUtY29yZSAyLjE3IGFuZCAyLjIwIGFnYWluc3Qgc3R1YmJlZCBLdWJlcm5ldGVzIG1vZHVsZXMgYW5kIGEgZmFrZSBgY2x1c3RlcmN0bGAsIHRvIGNoZWNrIHRoZSBnZW5lcmF0ZWQgY29tbWFuZHM6Cgp8IENsdXN0ZXIgc3RhdGUgfCBDb21tYW5kcyB8CnwtLS18LS0tfAp8IEVtcHR5IHwgYGluaXRgIHdpdGggYWxsIGZvdXIgcHJvdmlkZXJzIHBsdXMgYC0tYWRkb24gY3NyLWFwcHJvdmVyOnYwLjEuMGAgfAp8IFByb3ZpZGVycyBjdXJyZW50LCBhZGQtb24gbWlzc2luZyB8IGBpbml0IC0tYWRkb24gY3NyLWFwcHJvdmVyOnYwLjEuMGAgfAp8IE9sZGVyIENBUEkgYW5kIGFkZC1vbiB8IGB1cGdyYWRlIGFwcGx5YCBmb3IgY29yZSwgYm9vdHN0cmFwLCBjb250cm9sIHBsYW5lIGFuZCBgY2FwaS1jc3ItYXBwcm92ZXItc3lzdGVtL2Nzci1hcHByb3ZlcmAgfAp8IE9sZGVyIENBUEksIGFkZC1vbiBtaXNzaW5nIHwgYHVwZ3JhZGUgYXBwbHlgLCB0aGVuIGBpbml0IC0tYWRkb25gIHwKfCBFdmVyeXRoaW5nIGN1cnJlbnQgfCBubyBjbHVzdGVyY3RsIGNhbGxzIHwKCi0gYHlhbWxsaW50YCBhbmQgYGFuc2libGUtbGludGAgMjUuNi4xIHBhc3MuCgpSZWxhdGVkOiBaZW5kZXNrIDM3MDE4MS4K
      patchset: ddd72174ad5b177ee278122335d00af3544b744d
      pipeline: check
      playbook_context:
        playbook_projects:
          trusted/project_0/github.com/vexxhost/zuul-config:
            canonical_name: github.com/vexxhost/zuul-config
            checkout: main
            commit: 298983cd1253e6833abdb49d87d912527e0e6597
          trusted/project_1/opendev.org/zuul/zuul-jobs:
            canonical_name: opendev.org/zuul/zuul-jobs
            checkout: master
            commit: be52461cd48abccbf95b13a58b2551ac673d8ad7
          trusted/project_2/github.com/vexxhost/zuul-jobs:
            canonical_name: github.com/vexxhost/zuul-jobs
            checkout: main
            commit: 4fd48825891421af0774bdd500fee36e111d80a6
          untrusted/project_0/github.com/vexxhost/zuul-jobs:
            canonical_name: github.com/vexxhost/zuul-jobs
            checkout: main
            commit: 4fd48825891421af0774bdd500fee36e111d80a6
          untrusted/project_1/github.com/vexxhost/zuul-config:
            canonical_name: github.com/vexxhost/zuul-config
            checkout: main
            commit: 298983cd1253e6833abdb49d87d912527e0e6597
          untrusted/project_2/opendev.org/zuul/zuul-jobs:
            canonical_name: opendev.org/zuul/zuul-jobs
            checkout: master
            commit: be52461cd48abccbf95b13a58b2551ac673d8ad7
        playbooks:
        - path: untrusted/project_0/github.com/vexxhost/zuul-jobs/playbooks/ansible-test/run.yaml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/playbook_0/role_1/zuul-jobs
            link_target: untrusted/project_2/opendev.org/zuul/zuul-jobs
            role_path: ansible/playbook_0/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: playbook branch
            link_name: ansible/playbook_0/role_2/zuul-jobs
            link_target: untrusted/project_0/github.com/vexxhost/zuul-jobs
            role_path: ansible/playbook_0/role_2/zuul-jobs/roles
        post_playbooks:
        - path: trusted/project_0/github.com/vexxhost/zuul-config/playbooks/base/post.yaml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/post_playbook_0/role_1/zuul-jobs
            link_target: trusted/project_1/opendev.org/zuul/zuul-jobs
            role_path: ansible/post_playbook_0/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/post_playbook_0/role_2/zuul-jobs
            link_target: trusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/post_playbook_0/role_2/zuul-jobs/roles
        - path: trusted/project_0/github.com/vexxhost/zuul-config/playbooks/base/post-logs.yaml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/post_playbook_1/role_1/zuul-jobs
            link_target: trusted/project_1/opendev.org/zuul/zuul-jobs
            role_path: ansible/post_playbook_1/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/post_playbook_1/role_2/zuul-jobs
            link_target: trusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/post_playbook_1/role_2/zuul-jobs/roles
        pre_playbooks:
        - path: trusted/project_0/github.com/vexxhost/zuul-config/playbooks/base/pre.yaml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/pre_playbook_0/role_1/zuul-jobs
            link_target: trusted/project_1/opendev.org/zuul/zuul-jobs
            role_path: ansible/pre_playbook_0/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/pre_playbook_0/role_2/zuul-jobs
            link_target: trusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/pre_playbook_0/role_2/zuul-jobs/roles
        - path: untrusted/project_0/github.com/vexxhost/zuul-jobs/playbooks/ansible-test/pre.yaml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/pre_playbook_1/role_1/zuul-jobs
            link_target: untrusted/project_2/opendev.org/zuul/zuul-jobs
            role_path: ansible/pre_playbook_1/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: playbook branch
            link_name: ansible/pre_playbook_1/role_2/zuul-jobs
            link_target: untrusted/project_0/github.com/vexxhost/zuul-jobs
            role_path: ansible/pre_playbook_1/role_2/zuul-jobs/roles
      post_review: false
      post_timeout: null
      pre_timeout: null
      project:
        canonical_hostname: github.com
        canonical_name: github.com/vexxhost/ansible-collection-kubernetes
        name: vexxhost/ansible-collection-kubernetes
        short_name: ansible-collection-kubernetes
        src_dir: src/github.com/vexxhost/ansible-collection-kubernetes
      projects:
        github.com/vexxhost/ansible-collection-kubernetes:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/ansible-collection-kubernetes
          checkout: main
          checkout_description: zuul branch
          commit: 35efb34683192d2ecc76a16a5055dc54020b0bd8
          name: vexxhost/ansible-collection-kubernetes
          required: false
          short_name: ansible-collection-kubernetes
          src_dir: src/github.com/vexxhost/ansible-collection-kubernetes
      ref: refs/pull/319/head
      resources: {}
      tenant: oss
      timeout: 1800
      topic: null
      voting: true
