Allow dot '.' in json key names #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bryanlarsen
added a commit
to bryanlarsen/ansible-ghetto-json
that referenced
this pull request
Nov 1, 2017
If the value contains an equal sign (`=`), we get a crash `ValueError: dictionary update sequence element FauxFaux#3 has length 3; 2 is required`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a positive lookbehind to add a slash '' before a dot '.' in json key names.
I needed this for openvpn config file
{ "Default": { "admin_ui.https.ip_address": "all", "admin_ui.https.port": "943" } }in your ansible yaml file
'Default.admin_ui\.https\.port'="944"The single quotes are needed around the parameter or else ansible escapes the backslash when passing as a parameter to ghetto-json