-
Notifications
You must be signed in to change notification settings - Fork 102
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
Add guard method for image_family selector #192
Labels
Comments
Should update the docs example aswell to account for this.. I got the example working by adding:
|
@fatmcgav Thank you for this. I missed a piece of logic here. Default image project id's should be autopopulated. I'll address this in the nearest patch. |
Cool, cheers for confirming.
…On Sat, 6 Oct 2018, 13:02 Artem Yakimenko, ***@***.***> wrote:
@fatmcgav <https://github.com/fatmcgav> what you've experienced is
actually a regression, apologies - see #206
<#206>. I'll roll out a
fix today.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#192 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACIbIhXcEP2c587mMGuaOW8HKDI6nFZtks5uiJvBgaJpZM4TN2V7>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If image family does not exist we trace back:
Need a guard method that rolls back the process of machine creation here:
vagrant-google/lib/vagrant-google/action/run_instance.rb
Line 103 in f870d7c
The text was updated successfully, but these errors were encountered: