You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the "nodes" key, Ansible treats it as a re-organization of the elements in the data structure. Instead of simply renaming the key, Ansible considers it a new key with an associated value, and it re-arranges the other keys around this new key in the YAML output.
PS: check about map('combine') in ansible.
The text was updated successfully, but these errors were encountered:
I have to say I'm not exactly sure where the problem is. Yes, Ansible indeed reorganizes the keys, but the resulting yaml still represents the same structure. You can try parsing the resulting yaml and the yaml you expected by any yaml parser and you'll get the same results (at least I did, I might have missed something). Can you explain exactly what problem you're seeing with the config that you get?
This looks related to #557. It's still unclear how the reordering "breaks" anything but it looks like it does confuse some people; I'll create a backlog card to look at this.
EDIT: I'll also rename this issue to better represent the issue at hand.
alopezz
changed the title
datadog_checks rabbitmq, cannot configure node.
The generated integration configs don't honor the order set in the playbook
Jul 19, 2024
Datadog rabbitmq node configuration will generate a wrong config.yaml file when we use node in datadog_checks variable.
Example:
Will generate this wrong config.yaml file:
When we expect this config.yaml file:
When using the "nodes" key, Ansible treats it as a re-organization of the elements in the data structure. Instead of simply renaming the key, Ansible considers it a new key with an associated value, and it re-arranges the other keys around this new key in the YAML output.
PS: check about map('combine') in ansible.
The text was updated successfully, but these errors were encountered: