fixed the user data encoding by using the proper base64 #541
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.
The function
base64.urlsafe_b64encode()
would fail to properly encode the>
character, as stated in #540That affected the Elastigroup creation whenever the
>
was present in the user data.For the CloudFormation template the fix was to use the same deferred call to
Fn::Base64
, just like for the native Auto Scaling Groups.The patch command was changed to use the correct
base64.b64encode()
function.