You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to contribute to this repo by creating an machine image gcp resource, basically is a clone of googlecompute but instead of saving as another gcp image, it will be saved as machine image.
Should i start creating another builder called googlecomputemachineimage?
The process will be basically the following:
Use the CreateImage part of the code to create a google compute instance and run provisioners.
Create the machine image based on the running google compute instance.
Delete the running instance.
The other option would be to extend the current googlecompute builder and add a conditional to create the machine image create_machine_image and the steps will basically create a new machine image and teardown the instance afterwards without creating a real gcp image.
The text was updated successfully, but these errors were encountered:
What would be your suggestion in order to support machine-images for google compute. Maybe a forked repo and keeping it up to date with the latest changes. The feature reuses most of the work already done by the regular google image golang code but I understand why it cannot be merged.
I would like to contribute to this repo by creating an machine image gcp resource, basically is a clone of
googlecompute
but instead of saving as another gcp image, it will be saved asmachine image
.https://cloud.google.com/compute/docs/machine-images
Should i start creating another builder called
googlecomputemachineimage
?The process will be basically the following:
The other option would be to extend the current
googlecompute
builder and add a conditional to create the machine imagecreate_machine_image
and thesteps
will basically create a new machine image and teardown the instance afterwards without creating a real gcp image.The text was updated successfully, but these errors were encountered: