Artem Yakimenko
Artem Yakimenko
Just tested on Ruby 3.0 and it seems to work now 🤔 Let's release and check.
So this failed here: ``` image = env[:google_compute].images.get(image, image_project_id).self_link ``` This means that the image specified could probably not be found. Can I have your `Vagrantfile` to look at? You...
@scottbrumley Your Vagrantfile looks correct, I have been able to launch a machine with it. Can you provide full output of `vagrant up --debug` ? This should give me a...
@cometta We're switching to Vagrant's standard rsync transport again in #181 Vagrant doesn't implement bi-directional sync yet. However, if you take a look at the FR for it, lower down...
@BirkhoffLee Can you tell me which permissions you were lacking? Perhaps we can add better error messages here.
@Jazzo Thanks for reporting this! Acknowledged, let me try to reproduce.
@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.
@fatmcgav what you've experienced is actually a regression, apologies - see #206. I'll roll out a fix today.
Thanks for using vagrant-google @suhongs! :) So, this is actually already supported, just specify: ``` google.machine_type = "custom-NUMBER_OF_CPUS-AMOUNT_OF_MEMORY_IN_MEGABYTES" ``` , for example: ``` google.machine_type = "custom-4-5120" ``` The underlying API...
@suhongs That is not implemented yet, I'm afraid. Fog supports it but plumbing is still needed for vagrant. This seems to be a popular request so I'll try to take...