Ensure that first/last host detection is deterministic
With ansible-core 2.16 a breaking changes landed [1] to some filters making their result returned in arbitrary order. With that, we were relying on them to always return exactly same ordered lists. With that we need to ensure that we still have determenistic behaviour where this is important. [1] https://github.com/ansible/ansible/issues/82554 Change-Id: I93c3b386388195b5b51c0d2c64864458bcfed326
This commit is contained in:
parent
f6d1ea1ca7
commit
5a34d2f0f1
@ -16,7 +16,7 @@
|
||||
_cloudkitty_is_first_play_host: >-
|
||||
{{
|
||||
(cloudkitty_services['cloudkitty-api']['group'] in group_names and inventory_hostname == (
|
||||
(groups[cloudkitty_services['cloudkitty-api']['group']] | intersect(ansible_play_hosts)) | list)[0]) | bool
|
||||
(groups[cloudkitty_services['cloudkitty-api']['group']] | select('in', ansible_play_hosts)) | list)[0]) | bool
|
||||
}}
|
||||
|
||||
_cloudkitty_oslomsg_rpc_vhost_conf: >-
|
||||
|
Loading…
x
Reference in New Issue
Block a user