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
{{ message }}
This repository has been archived by the owner on Apr 3, 2020. It is now read-only.
Hi, I'm trying to deploy the setup in GCP, using version 0.20.2. I followed the docs and created a service account, and assigned Project Owner permissions to it (+Storage Admin+Storage Object Admin). However when running the following:
I'm not sure why concourse-up is failing to find the config. I'm still investigating that.
One problem I can see with your command is that the domain should not include the protocol. So in your case it should be --domain concourse.xxx.xxx.xx.
@crsimmons I actually fixed it by setting my GCP user to be able to use the service account (during service account creation). I thought we could just use the service account without any user?
You don't need to associate the service account with a user. When you create the account you just need to give it Project Owner permissions then generate a JSON key file. Then you can export GOOGLE_APPLICATION_CREDENTIALS=<path/to/creds.json> and deploy.
glend
changed the title
GCE empty bucket name
GCP empty bucket name
Feb 28, 2019
Hi, I'm trying to deploy the setup in GCP, using version 0.20.2. I followed the docs and created a service account, and assigned Project Owner permissions to it (+Storage Admin+Storage Object Admin). However when running the following:
I get the following:
If I remove the
--iaas
flag it tries to deploy to my AWS account and doesn't have an issue determining the bucket name.The text was updated successfully, but these errors were encountered: