GCE: Error "Required 'Alpha Access' for the Compute API"

[Akatama]

Hey everyone,
I am using mash to help the openSUSE Cloud team. I am working on the mash job for Google Cloud Platform (referred to as GCE in the mash documentation).

When I try to use the mash job, however, I get errors. The first one I encountered was before I set skip_rollout to true:

Exception in create: <HttpError 403 when requesting https://compute.googleapis.com/compute/alpha/projects/opensuse-test/zones?alt=json returned \"Required 'Alpha Access' permission for 'Compute API'\". Details: \"[{'message': \"Required 'Alpha Access' permission for 'Compute API'\", 'domain': 'global', 'reason': 'forbidden'}]

This API appears to be equivalent to gcloud CLI gcloud compute zones list which does not require the alpha API. I did look through the code in mash to confirm this.

Once I set skip_rollout, I get a different, yet similar error:

Exception in create: <HttpError 403 when requesting https://compute.googleapis.com/compute/alpha/projects/opensuse-test/global/images?alt=json returned \"Required 'Alpha Access' permission for 'Compute API'\". Details: \"[{'message': \"Required 'Alpha Access' permission for 'Compute API'\", 'domain': 'global', 'reason': 'forbidden'}]

Best I can figure is that this seems to be required to create the actual image from the uploaded .tar.gz file.

However, I have used the gcloud CLI to upload and create an image manually before I tried to use mash to do that same job, and I did not require access to the alpha API. I did look into gaining access, but from what I can find, access is only granted to corporations that have specific reasons for needing alpha access, not a singular person using a brand new Google Cloud account to do some open source work.

Suggestion: either stop using the alpha version of the API, or provide a new argument in the gce mash job: something like use_alpha_version, which could default to true for people who need the alpha version of the api for their work.

Just in case I have missed something in the gce schema, I have provided my current mash job, with some specific info replaced. I will note that it does successfully upload the image, so I know that step is configuring correctly. Note that I had to upload as a .txt because I guess Github does not allow .job files.

gce_x86_64_example.txt

[smarlowucf]

Thanks for the report @Akatama . The alpha api is related to rollout access. We could add an argument to disable this which would allow mash to use the v1 api instead. I will look into this.