Fix for user custom attribute issues #173
Open
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.
Description
This PR fixes the issues I reported in #158, where defining
custom_attributes
that included a hypen-
in the name such asmsDS-SupportedEncryptionTypes
threw errors due to incorrect quoting of hashtable keys.It also fixes an (unreported?) bug where if a custom_attribute was a large number (e.g. uidNumber = 7333677) it ended up being formatted with an exponent which then threw an error.
Tested successfully on Windows 10 & Alpine with terraform 1.2.7 & 1.4.2
References
#158
Community Note