-
Notifications
You must be signed in to change notification settings - Fork 9.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hash custom_data in state storage #12214
Conversation
This also switches to helpers for b64.
v = base64Encode(v) | ||
} | ||
|
||
v = base64Encode(v) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Helper does this check now
data = *osProfile.CustomData | ||
} | ||
result["custom_data"] = data | ||
result["custom_data"] = *osProfile.CustomData |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This I'm not sure about. I tried this with b64 and non-b64 encoded data, and it worked both times. I'm not sure what this code was attempting to do?
Looks awesome @sethvargo This is going to be a 0.9 only feature just incase it causes any upgrade issues ;) |
This also switches to helpers for b64.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
This PR changes custom_data to be hashed in the statefile instead of plain-textified. This reduces the size of the statefile and is more in line with how other providers behave.
This also switches to helpers for b64.
/cc @stack72