-
Notifications
You must be signed in to change notification settings - Fork 45
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
Use URL safe Base64 encoding for user data #50
Use URL safe Base64 encoding for user data #50
Conversation
Older version of CloudStack may complain about non-printable ASCII characters in user data unless URL safe Base64 encoding is used.
@petrhosek what versions does this apply to? |
This is probably the correct way to do it. We need to make sure this works with the current release of cloudstack and hopefully be future proof. This this also work with newer cloudstack versions? |
This was tested against 4.1.1 which is also the version that fails with the current implementation. Unfortunately I don't have access to newer versions, but in general I believe this is the correct way as we are sending these arguments in URL. |
@petrhosek We are running 4.3.x internally so we should be able to test it out(?) |
If it works, it will get merged for the next release. |
@petrhosek could you provide us with a minimal Vagrantfile that is broken with the current code, but works with your code? That would be aweome! |
LET'S GO! |
Use URL safe Base64 encoding for user data
I'm sorry about the delay, I had to wait till my pull requests were merged into CoreOS, which only happened yesterday, since this is where I was experiencing the issue. I've created a reproducer which consists of a Packer template that builds a CloudStack template which is then used in the Vagrantfile that triggers the issue. Please note that you need to use @mindjiver's version of Packer which has the CloudStack support. I have tested this against CloudStack versions 4.1.1 and 4.2.1 and experienced the issue in both versions, i.e. without
|
Older version of CloudStack may complain about non-printable ASCII
characters in user data unless URL safe Base64 encoding is used.