OpenStack YAML output problem

[rickogg]

When running openstack commands (I was using server show action) if the output is in yaml format I attempt either
str( result() ) - or - '{{ result() | to_yaml_string }}' and I output this is a variable; however, I can not use
'{{ ctx().variable | from _yaml_string }}' to output this back to a json object, as it's throwing the following error.

"JinjaEvaluationException: Unable to evaluate expression '{{ ctx().variable | from_yaml_string }}'. ScannerError: mapping values are not allowed in this context\n in "", line 1, column 57"

if however, I send the yaml output to a file (action core.local command - server show > yaml.txt)
I'm able to "cat" the files contents and use '{{ result().stdout | from_yaml_string }}' and the output looks perfect.

Understood that I can output json instead of yaml from the original command; however, the json output does not provide access to the values within the object - for example (please ignore appropriate json formatting)

addresses = { network1: 1.1.1.1 network2: 2.2.2.2 etc...}
The object addresses just produces a long string of text that we need to parse through using regex

if I import from yaml I'm able to address sub-objects directly - for example

result().addresses.network1 = 1.1.1.1
result().addresses.network2 = 2.2.2.2

this would be much simpler to just reference the object directly as the network name never changes but openstack's output changes the order of the "networks" listed which make regex matching all the more difficult.

Certainly would welcome any guidance

[jamesdreid]

Have you tried to pass the "addresses" variable to the "from_json" to convert the value from a sting to an object that can be accessed directly without a regex? Something like:

address_object: "{{ ctx().result.networks | from_json_string }}"

Assuming the output is valid JSON, you should be able to get each network address individually by name:

"{{ ctx().address_object.network1 = 1.1.1.1 }}"

[rickogg]

Thanks for the suggestion. Yes, but unfortunately the output remains the same. The addresses object remains just one long string of text rather than outputting "sub-objects" that we can reference directly.