Actually, it looks like our default output format is yaml. This means that all output, filtered or not, from 'juju config' command is in yaml output.
You might find it easier to use '--format=json'?
I have proposed a PR against 2.4 to remove hard-coding of yaml for filtered output given a key though: https://github.com/juju/juju/pull/9026.
All other characters, like newline breaking of a long value or character escaping, is dictated by upsteam yaml and json formatters, external to Juju.
Actually, it looks like our default output format is yaml. This means that all output, filtered or not, from 'juju config' command is in yaml output.
You might find it easier to use '--format=json'?
I have proposed a PR against 2.4 to remove hard-coding of yaml for filtered output given a key though: https:/ /github. com/juju/ juju/pull/ 9026.
All other characters, like newline breaking of a long value or character escaping, is dictated by upsteam yaml and json formatters, external to Juju.