Skip to content
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

[Feature Request] Support HTTP URL for userdata #114

Open
dpetzel opened this issue Oct 12, 2015 · 3 comments
Open

[Feature Request] Support HTTP URL for userdata #114

dpetzel opened this issue Oct 12, 2015 · 3 comments

Comments

@dpetzel
Copy link
Contributor

dpetzel commented Oct 12, 2015

In our environment we have some boilerplate userdata we need to inject into instances in order to prep them for TK testing. Right now we have userdata copied into a number of projects. It would very useful (and DRY) if we could configure the userdata to be fetched from an HTTP(s) endpoint. This would allow us to keep the userdata in a central place

@jjasghar
Copy link
Contributor

So it seems that user_data is an option in the https://github.com/fog/fog/blob/master/lib/fog/openstack/requests/compute/create_server.rb#L15. I have a running theory that we should be able to just hand off to that. I'm not sure how to make that happen but I'm pretty confident that is all we need to do.

@dpetzel
Copy link
Contributor Author

dpetzel commented Oct 13, 2015

If it helps, here is how kitchen-ec2 is handling the user_data currently: https://github.com/test-kitchen/kitchen-ec2/blob/master/lib/kitchen/driver/aws/instance_generator.rb#L144

@carpnick
Copy link
Contributor

carpnick commented Nov 4, 2015

That confirms I think what @jjasghar was saying. Looking at this line we are basically doing what ec2 is already doing. Only change would be to add an if/else where the else would say its not a file and just pass along the URL maybe.

Actually like this idea so then when teams are sharing scripts, they can be in a central repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants