You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you have an input variable to the module that has a $ and this variable gets passed into a terraform template file it can end up being dynamically redacted to an empty string.
For example if the db_password starts with a $ the config that lands on the scale-set will have the password read as "".
One strategy to prevent this issue would be to base64 encode the config in Terraform, pass it to the user-data script, then base64 decode it there to avoid the inference.
The text was updated successfully, but these errors were encountered:
Currently if you have an input variable to the module that has a $ and this variable gets passed into a terraform template file it can end up being dynamically redacted to an empty string.
For example if the
db_password
starts with a$
the config that lands on the scale-set will have the password read as""
.One strategy to prevent this issue would be to base64 encode the config in Terraform, pass it to the user-data script, then base64 decode it there to avoid the inference.
The text was updated successfully, but these errors were encountered: