-
Notifications
You must be signed in to change notification settings - Fork 24
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
Allow pinning vm's machine image, instead of always using latest …stable/cos_cloud #112
Allow pinning vm's machine image, instead of always using latest …stable/cos_cloud #112
Conversation
19084e2
to
e7a3dfb
Compare
e7a3dfb
to
9ba6a75
Compare
Thanks for this PR 🙌 @dennislapchenko, currently on a trip - I'm back in 2 days! |
@bschaatsbergen so hopefully you will merge this in the coming days? On Monday is my last day at the place where I implemented this, would like to wean them off my personal fork before leaving 😁 |
Jumping on it now @dennislapchenko ! |
I would think that something like I did in #99 would be a good idea. You give the user the ability to overwrite the entire disk source image if they want too, or let them specify a specific COS version, or get the latest stable COS image. @dennislapchenko - thoughts? |
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.
LGTM 🚀
@bschaatsbergen agree this was the least confusing way. Thanks for finalising this 🙏 |
what
full
image name needs to be passed everytime. After the second commit you can just provide the short name and it will be verified. One drawback is that this it's not possible to move away from cos images, which probably is not desired anyway.why
cos
images work well with atlantis/secure vm configurations.. Just today i was making tweaks to the module and latest image got deployed too. As a result backend never could be reached.. could not find any logs as to why this happened, but reverting the image instantly fixed the issue.