Open simon360 opened 11 months ago
Just experienced this same issue for the first time. Another potential solution would be to expose a new command gcp-cli/setup-no-install
/ gcp-cli/setup-only
which executes the setup step without attempting to perform an install. Instead, it assumes that gcloud is already properly installed
Orb version
3.1.1
What happened
We've been using this orb, with the CLI version set to
latest
and the executor set togcp-cli/google
. However, this leads to an issue every few weeks where either:When that happens, our deploys are blocked with an error along these lines:
There's no way to get past this, unless we hard-set the CLI version to whatever's in the Docker image. This is frequently leading to our deploys being blocked for hours, sometimes up to a day.
In our case, we'd be more than happy to simply use whatever version is provided by the latest Google Cloud SDK docker image. We know it'll be the newest version the vast majority of the time, and if it's not the newest version, it'll be very, very close. And the docs for this orb's
install
command suggest that this is the intended behaviour (emphasis mine):Expected behavior
When using the
gcp-cli/google
executor and thelatest
version is specified for the CLI, don't try to uninstall/reinstall a different version, because doing so will always fail with permission errors anyway.(I'd be happy enough to put together a PR for this, but I wanted to open the discussion first to make sure I wouldn't be wasting any work putting forward a fix for this)