Reviewed: https://review.opendev.org/c/openstack/ansible-config_template/+/924217 Committed: https://opendev.org/openstack/ansible-config_template/commit/13b52a62cd35751b26be520a72214c2d10e8c471 Submitter: "Zuul (22348)" Branch: master
commit 13b52a62cd35751b26be520a72214c2d10e8c471 Author: Dmitriy Rabotyagov <email address hidden> Date: Tue Jul 16 13:26:14 2024 +0200
Respect yml_multilines for JSON configs
At the moment there is no good way to have new lines ("\n") in JSON files and not to convert the result to a list. In the meanwhile this can be totally expected/required thing to do, for example to define cloud-init vendor data [1]
[1] https://cloudinit.readthedocs.io/en/latest/reference/datasources/openstack.html#vendor-data
Related-Bug: #2073171 Change-Id: I00d74a26357a8458e38d9eb816a3f3eceeae1e0d
Reviewed: https:/ /review. opendev. org/c/openstack /ansible- config_ template/ +/924217 /opendev. org/openstack/ ansible- config_ template/ commit/ 13b52a62cd35751 b26be520a72214c 2d10e8c471
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 13b52a62cd35751 b26be520a72214c 2d10e8c471
Author: Dmitriy Rabotyagov <email address hidden>
Date: Tue Jul 16 13:26:14 2024 +0200
Respect yml_multilines for JSON configs
At the moment there is no good way to have new lines ("\n") in JSON
files and not to convert the result to a list.
In the meanwhile this can be totally expected/required thing to do,
for example to define cloud-init vendor data [1]
[1] https:/ /cloudinit. readthedocs. io/en/latest/ reference/ datasources/ openstack. html#vendor- data
Related-Bug: #2073171 58e38d9eb816a3f 3eceeae1e0d
Change-Id: I00d74a26357a84