// the find
mitchellh/vagrant-google
Vagrant provider for GCE.
A Vagrant provider plugin for Google Compute Engine, letting you spin up and manage GCE VMs with the same Vagrantfile workflow you'd use for VirtualBox or AWS. It's for teams already invested in Vagrant who want to use GCE without switching tools. The README openly says it's looking for maintainers, which tells you most of what you need to know about its trajectory.
Zone-specific configuration overrides are well-thought-out — you can define different machine types and images per zone in a single Vagrantfile without duplication. OAuth2 scope aliases (e.g., 'bigquery' instead of the full URL) are a small but genuinely useful ergonomic touch. Service account JSON key auth works cleanly alongside application-default credentials, covering both local dev and CI use cases. Shielded VM options (Secure Boot, vTPM, integrity monitoring) and GPU accelerator support are there if you need them.
The plugin is actively looking for maintainers and hasn't had meaningful development in years — adopting it is effectively adopting maintenance burden. No native networking support: `config.vm.network` is silently ignored, which will surprise anyone used to other Vagrant providers. SSH key management is awkward by design — you have to manually upload your public key to GCE metadata before anything works, and the daemon-based approach is a footgun when keys don't have the right username prefix. The unit test suite covers only config; there are no unit tests for the actual action chain, so changes break silently until you run expensive live acceptance tests.