all:
  children:
    zuul_unreachable:
      hosts: {}
  hosts:
    debian-bookworm:
      ansible_connection: ssh
      ansible_host: 2a13:1a81:8000:3124:f816:3eff:fe12:4c29
      ansible_port: 22
      ansible_python_interpreter: auto
      ansible_user: zuul
      nodepool:
        az: nova
        cloud: regiocloud-a-ci
        external_id: eca9e463-2a72-4dd8-9e17-c8fa06a926f2
        host_id: 7f2607eceb24f4583c6f9496c53c64b51afe50de5eacda4379b21c42
        interface_ip: 2a13:1a81:8000:3124:f816:3eff:fe12:4c29
        label: debian-bookworm
        node_properties: {}
        private_ipv4: 10.128.0.100
        private_ipv6: null
        provider: regiocloud-a
        public_ipv4: 81.163.192.162
        public_ipv6: 2a13:1a81:8000:3124:f816:3eff:fe12:4c29
        region: null
        slot: null
  vars:
    zuul:
      _inheritance_path:
      - '<Job base explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: osism/zuul-config/zuul.d/jobs.yaml@main#2>'
      - '<Job ansible-collection-ensure-readme explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: osism/zuul-jobs/.zuul.yaml@main#2>'
      - '<Job ansible-collection-ensure-readme explicit: None implied: None source:
        osism/osism-kubernetes/.zuul.yaml@main#104>'
      ansible_version: '9'
      attempts: 1
      branch: main
      build: 33dfa1ae83904979837a93522156957a
      build_refs:
      - branch: main
        change: '322'
        change_message: "Apply the keycloak-operator CRDs from the role\n\nApply the
          Keycloak CRDs that the role already ships, so `osism apply k8s-keycloak-operator`\nproduces
          a working operator on a cluster that has never had Keycloak.\n\n### The
          problem\n\nThe role ships both CRDs in `roles/keycloak_operator/files/`:\n\n-
          `keycloaks.k8s.keycloak.org-v1.yml` (~205 KB)\n- `keycloakrealmimports.k8s.keycloak.org-v1.yml`
          (~176 KB)\n\nbut **no task ever applies them**. `tasks/main.yml` runs `config`
          \u2192 `namespace` \u2192 `deploy`,\nand `deploy.yml` applies only the rendered
          `keycloak-operator.yml`. The separate `crds` role\ncovers only the prometheus-operator
          CRDs \u2014 `roles/crds/tasks/main.yml` contains a single task,\ngated on
          `crds_prometheus_operator`.\n\nSo on a cluster where the CRDs are not already
          present, the play installs an operator with\nnothing to reconcile.\n\n###
          What this changes\n\n- adds `roles/keycloak_operator/tasks/crds.yml`, included
          from `tasks/main.yml` before\n  `namespace` and `deploy` so the CRDs exist
          by the time the operator starts\n- waits for both CRDs to report `Established`\n-
          adds `keycloak_operator_crd_directory`, `keycloak_operator_crds` and\n  `keycloak_operator_crd_names`
          to the role defaults, so the file list is not hardcoded in the\n  task\n\n###
          Note on server-side apply\n\n`crds.yml` uses `server_side_apply` rather
          than a plain apply. At this size a client-side\napply stores the entire
          object in the `kubectl.kubernetes.io/last-applied-configuration`\nannotation,
          which exceeds the metadata size limit and fails. This is the standard approach\nfor
          large CRDs.\n\n### Evidence\n\nVerified on a k3s 1.36.3 cluster with no
          prior Keycloak installation:\n\n- before: `osism apply k8s-keycloak-operator`
          leaves the operator running with no\n  `keycloaks.k8s.keycloak.org` CRD
          present\n- after: both CRDs reach `Established`, the operator reaches `1/1
          Running`, and a `Keycloak`\n  custom resource reconciles to `Ready=True`
          with a working instance behind it\n\n`ansible-lint roles/keycloak_operator/`
          reports the same single pre-existing\n`schema[meta]` violation before and
          after this change (an unrelated `meta/main.yml` platform\nschema issue)
          \u2014 no new violations are introduced.\n\n### Related\n\nThe role deploys
          only the operator: no `Keycloak` CR, no database, no TLS and no Service,
          all\nof which are needed for a usable Keycloak. That is arguably out of
          scope for this role, but\nworth either documenting or covering with an opinionated
          example. Happy to follow up\nseparately if useful."
        change_url: https://github.com/osism/osism-kubernetes/pull/322
        commit_id: 114cfad3d2820962ff146af00f90819add11925f
        patchset: 114cfad3d2820962ff146af00f90819add11925f
        project:
          canonical_hostname: github.com
          canonical_name: github.com/osism/osism-kubernetes
          name: osism/osism-kubernetes
          short_name: osism-kubernetes
        src_dir: src/github.com/osism/osism-kubernetes
        topic: null
      buildset: 24dacb5b0dba46b4ad5f18b5307e1723
      buildset_refs:
      - branch: main
        change: '322'
        change_message: "Apply the keycloak-operator CRDs from the role\n\nApply the
          Keycloak CRDs that the role already ships, so `osism apply k8s-keycloak-operator`\nproduces
          a working operator on a cluster that has never had Keycloak.\n\n### The
          problem\n\nThe role ships both CRDs in `roles/keycloak_operator/files/`:\n\n-
          `keycloaks.k8s.keycloak.org-v1.yml` (~205 KB)\n- `keycloakrealmimports.k8s.keycloak.org-v1.yml`
          (~176 KB)\n\nbut **no task ever applies them**. `tasks/main.yml` runs `config`
          \u2192 `namespace` \u2192 `deploy`,\nand `deploy.yml` applies only the rendered
          `keycloak-operator.yml`. The separate `crds` role\ncovers only the prometheus-operator
          CRDs \u2014 `roles/crds/tasks/main.yml` contains a single task,\ngated on
          `crds_prometheus_operator`.\n\nSo on a cluster where the CRDs are not already
          present, the play installs an operator with\nnothing to reconcile.\n\n###
          What this changes\n\n- adds `roles/keycloak_operator/tasks/crds.yml`, included
          from `tasks/main.yml` before\n  `namespace` and `deploy` so the CRDs exist
          by the time the operator starts\n- waits for both CRDs to report `Established`\n-
          adds `keycloak_operator_crd_directory`, `keycloak_operator_crds` and\n  `keycloak_operator_crd_names`
          to the role defaults, so the file list is not hardcoded in the\n  task\n\n###
          Note on server-side apply\n\n`crds.yml` uses `server_side_apply` rather
          than a plain apply. At this size a client-side\napply stores the entire
          object in the `kubectl.kubernetes.io/last-applied-configuration`\nannotation,
          which exceeds the metadata size limit and fails. This is the standard approach\nfor
          large CRDs.\n\n### Evidence\n\nVerified on a k3s 1.36.3 cluster with no
          prior Keycloak installation:\n\n- before: `osism apply k8s-keycloak-operator`
          leaves the operator running with no\n  `keycloaks.k8s.keycloak.org` CRD
          present\n- after: both CRDs reach `Established`, the operator reaches `1/1
          Running`, and a `Keycloak`\n  custom resource reconciles to `Ready=True`
          with a working instance behind it\n\n`ansible-lint roles/keycloak_operator/`
          reports the same single pre-existing\n`schema[meta]` violation before and
          after this change (an unrelated `meta/main.yml` platform\nschema issue)
          \u2014 no new violations are introduced.\n\n### Related\n\nThe role deploys
          only the operator: no `Keycloak` CR, no database, no TLS and no Service,
          all\nof which are needed for a usable Keycloak. That is arguably out of
          scope for this role, but\nworth either documenting or covering with an opinionated
          example. Happy to follow up\nseparately if useful."
        change_url: https://github.com/osism/osism-kubernetes/pull/322
        commit_id: 114cfad3d2820962ff146af00f90819add11925f
        patchset: 114cfad3d2820962ff146af00f90819add11925f
        project:
          canonical_hostname: github.com
          canonical_name: github.com/osism/osism-kubernetes
          name: osism/osism-kubernetes
          short_name: osism-kubernetes
        src_dir: src/github.com/osism/osism-kubernetes
        topic: null
      change: '322'
      change_message: "Apply the keycloak-operator CRDs from the role\n\nApply the
        Keycloak CRDs that the role already ships, so `osism apply k8s-keycloak-operator`\nproduces
        a working operator on a cluster that has never had Keycloak.\n\n### The problem\n\nThe
        role ships both CRDs in `roles/keycloak_operator/files/`:\n\n- `keycloaks.k8s.keycloak.org-v1.yml`
        (~205 KB)\n- `keycloakrealmimports.k8s.keycloak.org-v1.yml` (~176 KB)\n\nbut
        **no task ever applies them**. `tasks/main.yml` runs `config` \u2192 `namespace`
        \u2192 `deploy`,\nand `deploy.yml` applies only the rendered `keycloak-operator.yml`.
        The separate `crds` role\ncovers only the prometheus-operator CRDs \u2014
        `roles/crds/tasks/main.yml` contains a single task,\ngated on `crds_prometheus_operator`.\n\nSo
        on a cluster where the CRDs are not already present, the play installs an
        operator with\nnothing to reconcile.\n\n### What this changes\n\n- adds `roles/keycloak_operator/tasks/crds.yml`,
        included from `tasks/main.yml` before\n  `namespace` and `deploy` so the CRDs
        exist by the time the operator starts\n- waits for both CRDs to report `Established`\n-
        adds `keycloak_operator_crd_directory`, `keycloak_operator_crds` and\n  `keycloak_operator_crd_names`
        to the role defaults, so the file list is not hardcoded in the\n  task\n\n###
        Note on server-side apply\n\n`crds.yml` uses `server_side_apply` rather than
        a plain apply. At this size a client-side\napply stores the entire object
        in the `kubectl.kubernetes.io/last-applied-configuration`\nannotation, which
        exceeds the metadata size limit and fails. This is the standard approach\nfor
        large CRDs.\n\n### Evidence\n\nVerified on a k3s 1.36.3 cluster with no prior
        Keycloak installation:\n\n- before: `osism apply k8s-keycloak-operator` leaves
        the operator running with no\n  `keycloaks.k8s.keycloak.org` CRD present\n-
        after: both CRDs reach `Established`, the operator reaches `1/1 Running`,
        and a `Keycloak`\n  custom resource reconciles to `Ready=True` with a working
        instance behind it\n\n`ansible-lint roles/keycloak_operator/` reports the
        same single pre-existing\n`schema[meta]` violation before and after this change
        (an unrelated `meta/main.yml` platform\nschema issue) \u2014 no new violations
        are introduced.\n\n### Related\n\nThe role deploys only the operator: no `Keycloak`
        CR, no database, no TLS and no Service, all\nof which are needed for a usable
        Keycloak. That is arguably out of scope for this role, but\nworth either documenting
        or covering with an opinionated example. Happy to follow up\nseparately if
        useful."
      change_url: https://github.com/osism/osism-kubernetes/pull/322
      child_jobs: []
      commit_id: 114cfad3d2820962ff146af00f90819add11925f
      event_id: cfca7b50-954d-11f1-915f-51035c6d65be
      executor:
        hostname: 521e9411259a
        inventory_file: /var/lib/zuul/builds/33dfa1ae83904979837a93522156957a/ansible/inventory.yaml
        log_root: /var/lib/zuul/builds/33dfa1ae83904979837a93522156957a/work/logs
        result_data_file: /var/lib/zuul/builds/33dfa1ae83904979837a93522156957a/work/results.json
        src_root: /var/lib/zuul/builds/33dfa1ae83904979837a93522156957a/work/src
        work_root: /var/lib/zuul/builds/33dfa1ae83904979837a93522156957a/work
      include_vars: []
      items:
      - branch: main
        change: '322'
        change_message: "Apply the keycloak-operator CRDs from the role\n\nApply the
          Keycloak CRDs that the role already ships, so `osism apply k8s-keycloak-operator`\nproduces
          a working operator on a cluster that has never had Keycloak.\n\n### The
          problem\n\nThe role ships both CRDs in `roles/keycloak_operator/files/`:\n\n-
          `keycloaks.k8s.keycloak.org-v1.yml` (~205 KB)\n- `keycloakrealmimports.k8s.keycloak.org-v1.yml`
          (~176 KB)\n\nbut **no task ever applies them**. `tasks/main.yml` runs `config`
          \u2192 `namespace` \u2192 `deploy`,\nand `deploy.yml` applies only the rendered
          `keycloak-operator.yml`. The separate `crds` role\ncovers only the prometheus-operator
          CRDs \u2014 `roles/crds/tasks/main.yml` contains a single task,\ngated on
          `crds_prometheus_operator`.\n\nSo on a cluster where the CRDs are not already
          present, the play installs an operator with\nnothing to reconcile.\n\n###
          What this changes\n\n- adds `roles/keycloak_operator/tasks/crds.yml`, included
          from `tasks/main.yml` before\n  `namespace` and `deploy` so the CRDs exist
          by the time the operator starts\n- waits for both CRDs to report `Established`\n-
          adds `keycloak_operator_crd_directory`, `keycloak_operator_crds` and\n  `keycloak_operator_crd_names`
          to the role defaults, so the file list is not hardcoded in the\n  task\n\n###
          Note on server-side apply\n\n`crds.yml` uses `server_side_apply` rather
          than a plain apply. At this size a client-side\napply stores the entire
          object in the `kubectl.kubernetes.io/last-applied-configuration`\nannotation,
          which exceeds the metadata size limit and fails. This is the standard approach\nfor
          large CRDs.\n\n### Evidence\n\nVerified on a k3s 1.36.3 cluster with no
          prior Keycloak installation:\n\n- before: `osism apply k8s-keycloak-operator`
          leaves the operator running with no\n  `keycloaks.k8s.keycloak.org` CRD
          present\n- after: both CRDs reach `Established`, the operator reaches `1/1
          Running`, and a `Keycloak`\n  custom resource reconciles to `Ready=True`
          with a working instance behind it\n\n`ansible-lint roles/keycloak_operator/`
          reports the same single pre-existing\n`schema[meta]` violation before and
          after this change (an unrelated `meta/main.yml` platform\nschema issue)
          \u2014 no new violations are introduced.\n\n### Related\n\nThe role deploys
          only the operator: no `Keycloak` CR, no database, no TLS and no Service,
          all\nof which are needed for a usable Keycloak. That is arguably out of
          scope for this role, but\nworth either documenting or covering with an opinionated
          example. Happy to follow up\nseparately if useful."
        change_url: https://github.com/osism/osism-kubernetes/pull/322
        commit_id: 114cfad3d2820962ff146af00f90819add11925f
        patchset: 114cfad3d2820962ff146af00f90819add11925f
        project:
          canonical_hostname: github.com
          canonical_name: github.com/osism/osism-kubernetes
          name: osism/osism-kubernetes
          short_name: osism-kubernetes
          src_dir: src/github.com/osism/osism-kubernetes
        topic: null
      job: ansible-collection-ensure-readme
      jobtags: []
      max_attempts: 3
      message: QXBwbHkgdGhlIGtleWNsb2FrLW9wZXJhdG9yIENSRHMgZnJvbSB0aGUgcm9sZQoKQXBwbHkgdGhlIEtleWNsb2FrIENSRHMgdGhhdCB0aGUgcm9sZSBhbHJlYWR5IHNoaXBzLCBzbyBgb3Npc20gYXBwbHkgazhzLWtleWNsb2FrLW9wZXJhdG9yYApwcm9kdWNlcyBhIHdvcmtpbmcgb3BlcmF0b3Igb24gYSBjbHVzdGVyIHRoYXQgaGFzIG5ldmVyIGhhZCBLZXljbG9hay4KCiMjIyBUaGUgcHJvYmxlbQoKVGhlIHJvbGUgc2hpcHMgYm90aCBDUkRzIGluIGByb2xlcy9rZXljbG9ha19vcGVyYXRvci9maWxlcy9gOgoKLSBga2V5Y2xvYWtzLms4cy5rZXljbG9hay5vcmctdjEueW1sYCAofjIwNSBLQikKLSBga2V5Y2xvYWtyZWFsbWltcG9ydHMuazhzLmtleWNsb2FrLm9yZy12MS55bWxgICh+MTc2IEtCKQoKYnV0ICoqbm8gdGFzayBldmVyIGFwcGxpZXMgdGhlbSoqLiBgdGFza3MvbWFpbi55bWxgIHJ1bnMgYGNvbmZpZ2Ag4oaSIGBuYW1lc3BhY2VgIOKGkiBgZGVwbG95YCwKYW5kIGBkZXBsb3kueW1sYCBhcHBsaWVzIG9ubHkgdGhlIHJlbmRlcmVkIGBrZXljbG9hay1vcGVyYXRvci55bWxgLiBUaGUgc2VwYXJhdGUgYGNyZHNgIHJvbGUKY292ZXJzIG9ubHkgdGhlIHByb21ldGhldXMtb3BlcmF0b3IgQ1JEcyDigJQgYHJvbGVzL2NyZHMvdGFza3MvbWFpbi55bWxgIGNvbnRhaW5zIGEgc2luZ2xlIHRhc2ssCmdhdGVkIG9uIGBjcmRzX3Byb21ldGhldXNfb3BlcmF0b3JgLgoKU28gb24gYSBjbHVzdGVyIHdoZXJlIHRoZSBDUkRzIGFyZSBub3QgYWxyZWFkeSBwcmVzZW50LCB0aGUgcGxheSBpbnN0YWxscyBhbiBvcGVyYXRvciB3aXRoCm5vdGhpbmcgdG8gcmVjb25jaWxlLgoKIyMjIFdoYXQgdGhpcyBjaGFuZ2VzCgotIGFkZHMgYHJvbGVzL2tleWNsb2FrX29wZXJhdG9yL3Rhc2tzL2NyZHMueW1sYCwgaW5jbHVkZWQgZnJvbSBgdGFza3MvbWFpbi55bWxgIGJlZm9yZQogIGBuYW1lc3BhY2VgIGFuZCBgZGVwbG95YCBzbyB0aGUgQ1JEcyBleGlzdCBieSB0aGUgdGltZSB0aGUgb3BlcmF0b3Igc3RhcnRzCi0gd2FpdHMgZm9yIGJvdGggQ1JEcyB0byByZXBvcnQgYEVzdGFibGlzaGVkYAotIGFkZHMgYGtleWNsb2FrX29wZXJhdG9yX2NyZF9kaXJlY3RvcnlgLCBga2V5Y2xvYWtfb3BlcmF0b3JfY3Jkc2AgYW5kCiAgYGtleWNsb2FrX29wZXJhdG9yX2NyZF9uYW1lc2AgdG8gdGhlIHJvbGUgZGVmYXVsdHMsIHNvIHRoZSBmaWxlIGxpc3QgaXMgbm90IGhhcmRjb2RlZCBpbiB0aGUKICB0YXNrCgojIyMgTm90ZSBvbiBzZXJ2ZXItc2lkZSBhcHBseQoKYGNyZHMueW1sYCB1c2VzIGBzZXJ2ZXJfc2lkZV9hcHBseWAgcmF0aGVyIHRoYW4gYSBwbGFpbiBhcHBseS4gQXQgdGhpcyBzaXplIGEgY2xpZW50LXNpZGUKYXBwbHkgc3RvcmVzIHRoZSBlbnRpcmUgb2JqZWN0IGluIHRoZSBga3ViZWN0bC5rdWJlcm5ldGVzLmlvL2xhc3QtYXBwbGllZC1jb25maWd1cmF0aW9uYAphbm5vdGF0aW9uLCB3aGljaCBleGNlZWRzIHRoZSBtZXRhZGF0YSBzaXplIGxpbWl0IGFuZCBmYWlscy4gVGhpcyBpcyB0aGUgc3RhbmRhcmQgYXBwcm9hY2gKZm9yIGxhcmdlIENSRHMuCgojIyMgRXZpZGVuY2UKClZlcmlmaWVkIG9uIGEgazNzIDEuMzYuMyBjbHVzdGVyIHdpdGggbm8gcHJpb3IgS2V5Y2xvYWsgaW5zdGFsbGF0aW9uOgoKLSBiZWZvcmU6IGBvc2lzbSBhcHBseSBrOHMta2V5Y2xvYWstb3BlcmF0b3JgIGxlYXZlcyB0aGUgb3BlcmF0b3IgcnVubmluZyB3aXRoIG5vCiAgYGtleWNsb2Frcy5rOHMua2V5Y2xvYWsub3JnYCBDUkQgcHJlc2VudAotIGFmdGVyOiBib3RoIENSRHMgcmVhY2ggYEVzdGFibGlzaGVkYCwgdGhlIG9wZXJhdG9yIHJlYWNoZXMgYDEvMSBSdW5uaW5nYCwgYW5kIGEgYEtleWNsb2FrYAogIGN1c3RvbSByZXNvdXJjZSByZWNvbmNpbGVzIHRvIGBSZWFkeT1UcnVlYCB3aXRoIGEgd29ya2luZyBpbnN0YW5jZSBiZWhpbmQgaXQKCmBhbnNpYmxlLWxpbnQgcm9sZXMva2V5Y2xvYWtfb3BlcmF0b3IvYCByZXBvcnRzIHRoZSBzYW1lIHNpbmdsZSBwcmUtZXhpc3RpbmcKYHNjaGVtYVttZXRhXWAgdmlvbGF0aW9uIGJlZm9yZSBhbmQgYWZ0ZXIgdGhpcyBjaGFuZ2UgKGFuIHVucmVsYXRlZCBgbWV0YS9tYWluLnltbGAgcGxhdGZvcm0Kc2NoZW1hIGlzc3VlKSDigJQgbm8gbmV3IHZpb2xhdGlvbnMgYXJlIGludHJvZHVjZWQuCgojIyMgUmVsYXRlZAoKVGhlIHJvbGUgZGVwbG95cyBvbmx5IHRoZSBvcGVyYXRvcjogbm8gYEtleWNsb2FrYCBDUiwgbm8gZGF0YWJhc2UsIG5vIFRMUyBhbmQgbm8gU2VydmljZSwgYWxsCm9mIHdoaWNoIGFyZSBuZWVkZWQgZm9yIGEgdXNhYmxlIEtleWNsb2FrLiBUaGF0IGlzIGFyZ3VhYmx5IG91dCBvZiBzY29wZSBmb3IgdGhpcyByb2xlLCBidXQKd29ydGggZWl0aGVyIGRvY3VtZW50aW5nIG9yIGNvdmVyaW5nIHdpdGggYW4gb3BpbmlvbmF0ZWQgZXhhbXBsZS4gSGFwcHkgdG8gZm9sbG93IHVwCnNlcGFyYXRlbHkgaWYgdXNlZnVsLg==
      patchset: 114cfad3d2820962ff146af00f90819add11925f
      pipeline: check
      playbook_context:
        playbook_projects:
          trusted/project_0/github.com/osism/zuul-config:
            canonical_name: github.com/osism/zuul-config
            checkout: main
            commit: 71b711c422c10c242a8f785dc6d41ed9d12e9cd3
          trusted/project_1/github.com/osism/openinfra-zuul-jobs:
            canonical_name: github.com/osism/openinfra-zuul-jobs
            checkout: master
            commit: 242732586e2cba04d04867d3e302888c766bc231
          trusted/project_2/github.com/osism/zuul-jobs:
            canonical_name: github.com/osism/zuul-jobs
            checkout: main
            commit: b7c70f39598a39998dbbc6f833779355630f3a39
          untrusted/project_0/github.com/osism/zuul-jobs:
            canonical_name: github.com/osism/zuul-jobs
            checkout: main
            commit: b7c70f39598a39998dbbc6f833779355630f3a39
          untrusted/project_1/github.com/osism/zuul-config:
            canonical_name: github.com/osism/zuul-config
            checkout: main
            commit: 71b711c422c10c242a8f785dc6d41ed9d12e9cd3
          untrusted/project_2/github.com/osism/openinfra-zuul-jobs:
            canonical_name: github.com/osism/openinfra-zuul-jobs
            checkout: master
            commit: 242732586e2cba04d04867d3e302888c766bc231
        playbooks:
        - path: untrusted/project_0/github.com/osism/zuul-jobs/playbooks/ansible-collection-ensure-readme/run.yaml
          roles:
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/playbook_0/role_0/zuul-config
            link_target: untrusted/project_1/github.com/osism/zuul-config
            role_path: ansible/playbook_0/role_0/zuul-config/roles
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/playbook_0/role_1/openinfra-zuul-jobs
            link_target: untrusted/project_2/github.com/osism/openinfra-zuul-jobs
            role_path: ansible/playbook_0/role_1/openinfra-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/osism/zuul-jobs
            role_path: ansible/playbook_0/role_2/zuul-jobs/roles
      post_review: false
      post_timeout: 1800
      pre_timeout: null
      project:
        canonical_hostname: github.com
        canonical_name: github.com/osism/osism-kubernetes
        name: osism/osism-kubernetes
        short_name: osism-kubernetes
        src_dir: src/github.com/osism/osism-kubernetes
      projects:
        github.com/osism/osism-kubernetes:
          canonical_hostname: github.com
          canonical_name: github.com/osism/osism-kubernetes
          checkout: main
          checkout_description: zuul branch
          commit: 89bd302ab717c14a47eda845d3935b87fc1c9b3b
          name: osism/osism-kubernetes
          required: false
          short_name: osism-kubernetes
          src_dir: src/github.com/osism/osism-kubernetes
      ref: refs/pull/322/head
      resources: {}
      tenant: osism
      timeout: 1800
      topic: null
      voting: true
