all: children: zuul_unreachable: hosts: {} hosts: controller: ansible_connection: ssh ansible_host: 162.253.55.49 ansible_port: 22 ansible_python_interpreter: auto ansible_user: zuul nodepool: az: nova cloud: ansible-vexxhost external_id: 108fa731-ded4-47e8-a2e3-be7daded172e host_id: f75cfb10284b46a2b5ebf7cec9b228a5fb63e55dbeeaea30be382d21 interface_ip: 162.253.55.49 label: ansible-fedora-37-1vcpu private_ipv4: 192.168.0.156 private_ipv6: null provider: ansible-vexxhost-ca-ymq-1 public_ipv4: 162.253.55.49 public_ipv6: 2604:e100:1:0:f816:3eff:fe11:a912 region: ca-ymq-1 slot: null zuul_use_fetch_output: true vars: zuul: _inheritance_path: - '' - '' - '' ansible_version: '8' artifacts: - branch: main change: '488' job: build-ansible-collection metadata: type: zuul_manifest name: Zuul Manifest patchset: 8e2d09739b2d82ad2ba8598da1422efce14dc0ae project: ansible-collections/community.hashi_vault url: https://d421561f778074d60525-f1526c455a905d76d98b2245a8d84653.ssl.cf5.rackcdn.com/ansible/9f4977a0a5ce41b38ec874ce772430ad/zuul-manifest.json - branch: main change: '488' job: build-ansible-collection metadata: type: ansible_collection version: 7.2.0 name: community.hashi_vault patchset: 8e2d09739b2d82ad2ba8598da1422efce14dc0ae project: ansible-collections/community.hashi_vault url: https://d421561f778074d60525-f1526c455a905d76d98b2245a8d84653.ssl.cf5.rackcdn.com/ansible/9f4977a0a5ce41b38ec874ce772430ad/artifacts/community-hashi_vault-7.2.0.tar.gz attempts: 1 branch: main build: 462d97e76db84725b5fe5c07eca04ba1 build_refs: - branch: main change: '488' change_message: "Address sanity test failures and docs for `keys` return fields\n\n##### SUMMARY\r\n\r\nSee:\r\n- https://github.com/ansible/ansible/pull/86079\r\n\r\nSome of the database APIs return a sub-key named `keys` which is one of the values that's inaccessible via jinja2 dot `.` notation due to it to being a method on the underlying `dict` object in python.\r\n\r\nA new sanity test now fails when these values are defined in return values, even if they are only describing a field that is returned from upstream. There is no way to tell the test that these are intentional or incidental (while others may not be), so as I see it the options were:\r\n- Remove the description from return values (which makes the documentation less useful)\r\n- Add these to sanity ignores forever\r\n\r\nI chose the latter even though it's more annoying to maintain. We don't have control over what Vault returns and it's probably better to document the values that are relevant.\r\n\r\nWe already had notes in the docs explaining how to access `keys` correctly.\r\n\r\nWe're already \"aliasing\" these values in the module for convenience purposes, like providing a `roles` return value that is the same as `data.keys` and recommending its use, so we're already providing a more straightforward way to access the data being asked for, but it makes sense to not only return the full data structures but describe them accurately so that when people compare to the CLI or the HTTP API they can clearly map these values.\r\n\r\nThe one other change I've made here is to change markup return values from like `RV(raw.data.keys)` to `RV(raw.data['keys'])`. This renders as written, but technically does not link to the right place, since it will link to the \"parent\" value in the HTML.\r\n\r\nI think this is better since the anchors have limited use in our docs where they pretty much all fit within view.\r\n\r\n\r\n\r\n\r\n##### ISSUE TYPE\r\n\r\n- Documentation Pull Request\r\n\r\n" change_url: https://github.com/ansible-collections/community.hashi_vault/pull/488 commit_id: 8e2d09739b2d82ad2ba8598da1422efce14dc0ae patchset: 8e2d09739b2d82ad2ba8598da1422efce14dc0ae project: canonical_hostname: github.com canonical_name: github.com/ansible-collections/community.hashi_vault name: ansible-collections/community.hashi_vault short_name: community.hashi_vault src_dir: src/github.com/ansible-collections/community.hashi_vault topic: null buildset: a3eb9df9a582484fadf8b2b4e84d20d6 buildset_refs: - branch: main change: '488' change_message: "Address sanity test failures and docs for `keys` return fields\n\n##### SUMMARY\r\n\r\nSee:\r\n- https://github.com/ansible/ansible/pull/86079\r\n\r\nSome of the database APIs return a sub-key named `keys` which is one of the values that's inaccessible via jinja2 dot `.` notation due to it to being a method on the underlying `dict` object in python.\r\n\r\nA new sanity test now fails when these values are defined in return values, even if they are only describing a field that is returned from upstream. There is no way to tell the test that these are intentional or incidental (while others may not be), so as I see it the options were:\r\n- Remove the description from return values (which makes the documentation less useful)\r\n- Add these to sanity ignores forever\r\n\r\nI chose the latter even though it's more annoying to maintain. We don't have control over what Vault returns and it's probably better to document the values that are relevant.\r\n\r\nWe already had notes in the docs explaining how to access `keys` correctly.\r\n\r\nWe're already \"aliasing\" these values in the module for convenience purposes, like providing a `roles` return value that is the same as `data.keys` and recommending its use, so we're already providing a more straightforward way to access the data being asked for, but it makes sense to not only return the full data structures but describe them accurately so that when people compare to the CLI or the HTTP API they can clearly map these values.\r\n\r\nThe one other change I've made here is to change markup return values from like `RV(raw.data.keys)` to `RV(raw.data['keys'])`. This renders as written, but technically does not link to the right place, since it will link to the \"parent\" value in the HTML.\r\n\r\nI think this is better since the anchors have limited use in our docs where they pretty much all fit within view.\r\n\r\n\r\n\r\n\r\n##### ISSUE TYPE\r\n\r\n- Documentation Pull Request\r\n\r\n" change_url: https://github.com/ansible-collections/community.hashi_vault/pull/488 commit_id: 8e2d09739b2d82ad2ba8598da1422efce14dc0ae patchset: 8e2d09739b2d82ad2ba8598da1422efce14dc0ae project: canonical_hostname: github.com canonical_name: github.com/ansible-collections/community.hashi_vault name: ansible-collections/community.hashi_vault short_name: community.hashi_vault src_dir: src/github.com/ansible-collections/community.hashi_vault topic: null change: '488' change_message: "Address sanity test failures and docs for `keys` return fields\n\n##### SUMMARY\r\n\r\nSee:\r\n- https://github.com/ansible/ansible/pull/86079\r\n\r\nSome of the database APIs return a sub-key named `keys` which is one of the values that's inaccessible via jinja2 dot `.` notation due to it to being a method on the underlying `dict` object in python.\r\n\r\nA new sanity test now fails when these values are defined in return values, even if they are only describing a field that is returned from upstream. There is no way to tell the test that these are intentional or incidental (while others may not be), so as I see it the options were:\r\n- Remove the description from return values (which makes the documentation less useful)\r\n- Add these to sanity ignores forever\r\n\r\nI chose the latter even though it's more annoying to maintain. We don't have control over what Vault returns and it's probably better to document the values that are relevant.\r\n\r\nWe already had notes in the docs explaining how to access `keys` correctly.\r\n\r\nWe're already \"aliasing\" these values in the module for convenience purposes, like providing a `roles` return value that is the same as `data.keys` and recommending its use, so we're already providing a more straightforward way to access the data being asked for, but it makes sense to not only return the full data structures but describe them accurately so that when people compare to the CLI or the HTTP API they can clearly map these values.\r\n\r\nThe one other change I've made here is to change markup return values from like `RV(raw.data.keys)` to `RV(raw.data['keys'])`. This renders as written, but technically does not link to the right place, since it will link to the \"parent\" value in the HTML.\r\n\r\nI think this is better since the anchors have limited use in our docs where they pretty much all fit within view.\r\n\r\n\r\n\r\n\r\n##### ISSUE TYPE\r\n\r\n- Documentation Pull Request\r\n\r\n" change_url: https://github.com/ansible-collections/community.hashi_vault/pull/488 child_jobs: [] commit_id: 8e2d09739b2d82ad2ba8598da1422efce14dc0ae event_id: 55507eb0-c27b-11f0-9a7f-56d0a5d8e224 executor: hostname: ze04.softwarefactory-project.io inventory_file: /var/lib/zuul/builds/462d97e76db84725b5fe5c07eca04ba1/ansible/inventory.yaml log_root: /var/lib/zuul/builds/462d97e76db84725b5fe5c07eca04ba1/work/logs result_data_file: /var/lib/zuul/builds/462d97e76db84725b5fe5c07eca04ba1/work/results.json src_root: /var/lib/zuul/builds/462d97e76db84725b5fe5c07eca04ba1/work/src work_root: /var/lib/zuul/builds/462d97e76db84725b5fe5c07eca04ba1/work items: - branch: main change: '488' change_message: "Address sanity test failures and docs for `keys` return fields\n\n##### SUMMARY\r\n\r\nSee:\r\n- https://github.com/ansible/ansible/pull/86079\r\n\r\nSome of the database APIs return a sub-key named `keys` which is one of the values that's inaccessible via jinja2 dot `.` notation due to it to being a method on the underlying `dict` object in python.\r\n\r\nA new sanity test now fails when these values are defined in return values, even if they are only describing a field that is returned from upstream. There is no way to tell the test that these are intentional or incidental (while others may not be), so as I see it the options were:\r\n- Remove the description from return values (which makes the documentation less useful)\r\n- Add these to sanity ignores forever\r\n\r\nI chose the latter even though it's more annoying to maintain. We don't have control over what Vault returns and it's probably better to document the values that are relevant.\r\n\r\nWe already had notes in the docs explaining how to access `keys` correctly.\r\n\r\nWe're already \"aliasing\" these values in the module for convenience purposes, like providing a `roles` return value that is the same as `data.keys` and recommending its use, so we're already providing a more straightforward way to access the data being asked for, but it makes sense to not only return the full data structures but describe them accurately so that when people compare to the CLI or the HTTP API they can clearly map these values.\r\n\r\nThe one other change I've made here is to change markup return values from like `RV(raw.data.keys)` to `RV(raw.data['keys'])`. This renders as written, but technically does not link to the right place, since it will link to the \"parent\" value in the HTML.\r\n\r\nI think this is better since the anchors have limited use in our docs where they pretty much all fit within view.\r\n\r\n\r\n\r\n\r\n##### ISSUE TYPE\r\n\r\n- Documentation Pull Request\r\n\r\n" change_url: https://github.com/ansible-collections/community.hashi_vault/pull/488 commit_id: 8e2d09739b2d82ad2ba8598da1422efce14dc0ae patchset: 8e2d09739b2d82ad2ba8598da1422efce14dc0ae project: canonical_hostname: github.com canonical_name: github.com/ansible-collections/community.hashi_vault name: ansible-collections/community.hashi_vault short_name: community.hashi_vault src_dir: src/github.com/ansible-collections/community.hashi_vault topic: null job: ansible-galaxy-importer jobtags: [] max_attempts: 3 message: QWRkcmVzcyBzYW5pdHkgdGVzdCBmYWlsdXJlcyBhbmQgZG9jcyBmb3IgYGtleXNgIHJldHVybiBmaWVsZHMKCiMjIyMjIFNVTU1BUlkNCjwhLS0tIERlc2NyaWJlIHRoZSBjaGFuZ2UgYmVsb3csIGluY2x1ZGluZyByYXRpb25hbGUgYW5kIGRlc2lnbiBkZWNpc2lvbnMgLS0+DQpTZWU6DQotIGh0dHBzOi8vZ2l0aHViLmNvbS9hbnNpYmxlL2Fuc2libGUvcHVsbC84NjA3OQ0KDQpTb21lIG9mIHRoZSBkYXRhYmFzZSBBUElzIHJldHVybiBhIHN1Yi1rZXkgbmFtZWQgYGtleXNgIHdoaWNoIGlzIG9uZSBvZiB0aGUgdmFsdWVzIHRoYXQncyBpbmFjY2Vzc2libGUgdmlhIGppbmphMiBkb3QgYC5gIG5vdGF0aW9uIGR1ZSB0byBpdCB0byBiZWluZyBhIG1ldGhvZCBvbiB0aGUgdW5kZXJseWluZyBgZGljdGAgb2JqZWN0IGluIHB5dGhvbi4NCg0KQSBuZXcgc2FuaXR5IHRlc3Qgbm93IGZhaWxzIHdoZW4gdGhlc2UgdmFsdWVzIGFyZSBkZWZpbmVkIGluIHJldHVybiB2YWx1ZXMsIGV2ZW4gaWYgdGhleSBhcmUgb25seSBkZXNjcmliaW5nIGEgZmllbGQgdGhhdCBpcyByZXR1cm5lZCBmcm9tIHVwc3RyZWFtLiBUaGVyZSBpcyBubyB3YXkgdG8gdGVsbCB0aGUgdGVzdCB0aGF0IHRoZXNlIGFyZSBpbnRlbnRpb25hbCBvciBpbmNpZGVudGFsICh3aGlsZSBvdGhlcnMgbWF5IG5vdCBiZSksIHNvIGFzIEkgc2VlIGl0IHRoZSBvcHRpb25zIHdlcmU6DQotIFJlbW92ZSB0aGUgZGVzY3JpcHRpb24gZnJvbSByZXR1cm4gdmFsdWVzICh3aGljaCBtYWtlcyB0aGUgZG9jdW1lbnRhdGlvbiBsZXNzIHVzZWZ1bCkNCi0gQWRkIHRoZXNlIHRvIHNhbml0eSBpZ25vcmVzIGZvcmV2ZXINCg0KSSBjaG9zZSB0aGUgbGF0dGVyIGV2ZW4gdGhvdWdoIGl0J3MgbW9yZSBhbm5veWluZyB0byBtYWludGFpbi4gV2UgZG9uJ3QgaGF2ZSBjb250cm9sIG92ZXIgd2hhdCBWYXVsdCByZXR1cm5zIGFuZCBpdCdzIHByb2JhYmx5IGJldHRlciB0byBkb2N1bWVudCB0aGUgdmFsdWVzIHRoYXQgYXJlIHJlbGV2YW50Lg0KDQpXZSBhbHJlYWR5IGhhZCBub3RlcyBpbiB0aGUgZG9jcyBleHBsYWluaW5nIGhvdyB0byBhY2Nlc3MgYGtleXNgIGNvcnJlY3RseS4NCg0KV2UncmUgYWxyZWFkeSAiYWxpYXNpbmciIHRoZXNlIHZhbHVlcyBpbiB0aGUgbW9kdWxlIGZvciBjb252ZW5pZW5jZSBwdXJwb3NlcywgbGlrZSBwcm92aWRpbmcgYSBgcm9sZXNgIHJldHVybiB2YWx1ZSB0aGF0IGlzIHRoZSBzYW1lIGFzIGBkYXRhLmtleXNgIGFuZCByZWNvbW1lbmRpbmcgaXRzIHVzZSwgc28gd2UncmUgYWxyZWFkeSBwcm92aWRpbmcgYSBtb3JlIHN0cmFpZ2h0Zm9yd2FyZCB3YXkgdG8gYWNjZXNzIHRoZSBkYXRhIGJlaW5nIGFza2VkIGZvciwgYnV0IGl0ICBtYWtlcyBzZW5zZSB0byBub3Qgb25seSByZXR1cm4gdGhlIGZ1bGwgZGF0YSBzdHJ1Y3R1cmVzIGJ1dCBkZXNjcmliZSB0aGVtIGFjY3VyYXRlbHkgc28gdGhhdCB3aGVuIHBlb3BsZSBjb21wYXJlIHRvIHRoZSBDTEkgb3IgdGhlIEhUVFAgQVBJIHRoZXkgY2FuIGNsZWFybHkgbWFwIHRoZXNlIHZhbHVlcy4NCg0KVGhlIG9uZSBvdGhlciBjaGFuZ2UgSSd2ZSBtYWRlIGhlcmUgaXMgdG8gY2hhbmdlIG1hcmt1cCByZXR1cm4gdmFsdWVzIGZyb20gbGlrZSBgUlYocmF3LmRhdGEua2V5cylgIHRvIGBSVihyYXcuZGF0YVsna2V5cyddKWAuIFRoaXMgcmVuZGVycyBhcyB3cml0dGVuLCBidXQgdGVjaG5pY2FsbHkgZG9lcyBub3QgbGluayB0byB0aGUgcmlnaHQgcGxhY2UsIHNpbmNlIGl0IHdpbGwgbGluayB0byB0aGUgInBhcmVudCIgdmFsdWUgaW4gdGhlIEhUTUwuDQoNCkkgdGhpbmsgdGhpcyBpcyBiZXR0ZXIgc2luY2UgdGhlIGFuY2hvcnMgaGF2ZSBsaW1pdGVkIHVzZSBpbiBvdXIgZG9jcyB3aGVyZSB0aGV5IHByZXR0eSBtdWNoIGFsbCBmaXQgd2l0aGluIHZpZXcuDQoNCg0KPCEtLS0gSElOVDogSW5jbHVkZSAiRml4ZXMgI25ubiIgaWYgeW91IGFyZSBmaXhpbmcgYW4gZXhpc3RpbmcgaXNzdWUgLS0+DQoNCiMjIyMjIElTU1VFIFRZUEUNCjwhLS0tIFBpY2sgb25lIGJlbG93IGFuZCBkZWxldGUgdGhlIHJlc3QgLS0+DQotIERvY3VtZW50YXRpb24gUHVsbCBSZXF1ZXN0DQoNCg== patchset: 8e2d09739b2d82ad2ba8598da1422efce14dc0ae pipeline: third-party-check playbook_context: playbook_projects: trusted/project_0/github.com/ansible/zuul-config: canonical_name: github.com/ansible/zuul-config checkout: master commit: 3e667f4d3a5f14620cbe10b052c77698fa883471 trusted/project_1/opendev.org/zuul/zuul-jobs: canonical_name: opendev.org/zuul/zuul-jobs checkout: master commit: ca9686a93bf15ac1c0497871dba7eb1018c93d4e untrusted/project_0/github.com/ansible/ansible-zuul-jobs: canonical_name: github.com/ansible/ansible-zuul-jobs checkout: master commit: e7ff49de526383ec1701720d6aed921160ec3931 untrusted/project_1/github.com/ansible/zuul-config: canonical_name: github.com/ansible/zuul-config checkout: master commit: 3e667f4d3a5f14620cbe10b052c77698fa883471 untrusted/project_2/opendev.org/zuul/zuul-jobs: canonical_name: opendev.org/zuul/zuul-jobs checkout: master commit: ca9686a93bf15ac1c0497871dba7eb1018c93d4e playbooks: - path: untrusted/project_0/github.com/ansible/ansible-zuul-jobs/playbooks/ansible-galaxy-importer/run.yaml roles: - checkout: master checkout_description: playbook branch link_name: ansible/playbook_0/role_0/zuul-jobs link_target: untrusted/project_0/github.com/ansible/ansible-zuul-jobs role_path: ansible/playbook_0/role_0/zuul-jobs/roles - checkout: master checkout_description: project default branch link_name: ansible/playbook_0/role_1/zuul-config link_target: untrusted/project_1/github.com/ansible/zuul-config role_path: ansible/playbook_0/role_1/zuul-config/roles - checkout: master checkout_description: project default branch link_name: ansible/playbook_0/role_2/zuul-jobs link_target: untrusted/project_2/opendev.org/zuul/zuul-jobs role_path: ansible/playbook_0/role_2/zuul-jobs/roles post_review: false project: canonical_hostname: github.com canonical_name: github.com/ansible-collections/community.hashi_vault name: ansible-collections/community.hashi_vault short_name: community.hashi_vault src_dir: src/github.com/ansible-collections/community.hashi_vault projects: github.com/ansible-collections/community.hashi_vault: canonical_hostname: github.com canonical_name: github.com/ansible-collections/community.hashi_vault checkout: main checkout_description: zuul branch commit: 8e2d09739b2d82ad2ba8598da1422efce14dc0ae name: ansible-collections/community.hashi_vault required: false short_name: community.hashi_vault src_dir: src/github.com/ansible-collections/community.hashi_vault github.com/ansible-network/releases: canonical_hostname: github.com canonical_name: github.com/ansible-network/releases checkout: master checkout_description: project default branch commit: 646b310655c531e4904be07f4ff8fc3a29addd09 name: ansible-network/releases required: true short_name: releases src_dir: src/github.com/ansible-network/releases ref: refs/pull/488/head resources: {} tenant: ansible timeout: 1800 topic: null voting: true zuul_use_fetch_output: true