project: required field is not set about pulumi-gcp HOT 10 CLOSED

You can set this via config with pulumi config set gcp:project. I’ll leave this issue open to track how we can make sure the error messages and/or documentation are clearer as this has been a common tripping point.

from pulumi-gcp.

Hmm, the error message makes it look like a property of the bucket object? Does it default to the provider config or something like that?

from pulumi-gcp.

P.s. if this config really is required -- or even just recommended -- let's make sure this page covers it, as Luke suggested: https://pulumi.io/reference/gcp.html

from pulumi-gcp.

@lukehoban @joeduffy thanks for the quick reply. I am already setting the google credentials like so export GOOGLE_CREDENTIALS=$(cat credentials.json) and this json does contain the project id. So I dont completly understand what exactly to set here pulumi config set gcp:project?... is it project name or project id?

UPDATE:

OK, so its not the project name. Its the project id.. and this seems kind of redundant because the credentials.json already contains the required fields.

from pulumi-gcp.

Also, how can I set these config programmatically?

from pulumi-gcp.

I wrote some of this down in the installation section, but I'll add it to the reference page too - it's not very clear.

Any resource that requires a project, region, or zone accepts an optional project, region, or zone property. These fields are marked as optional because, if they are not set, we pull default values for them from the GOOGLE_PROJECT, GOOGLE_REGION, and GOOGLE_ZONE environment variables. You can also use gcp:project, gcp:region, and gcp:zone config keys if you don't want to use environment variables. I'll document this better on the website since it's not obvious.

from pulumi-gcp.

Thanks, @swgillespie for the update.

However, I still think its good to pull in the values from the credentials.json if it already exists. One has an option to override it for whatsoever reason, however, using the default values (from the gcp generated credential file) is more meaningful.

from pulumi-gcp.

Thank you for trying this out! 😄

However, I still think its good to pull in the values from the credentials.json if it already exists.

It's true that there's a project ID in the credentials file, but the project in there is the project to which the service account belongs, which is not necessarily the one into which you want to deploy resources.

Honestly, I'm not familiar enough with GCP to know if that's a reasonable default. Do you think that people will be (in general) expecting to deploy resources into the same project that their service account belongs to?

from pulumi-gcp.

@swgillespie... the service account credentials most likely wont even have access to other projects, so I think that it is a reasonable default.

Apart from this, if anyone wants to change it, they do have this option using the environment variables, but for people like me (I am so lazy LOL) it would be nice to use this as a default value.

You may close the issue if you think otherwise and/or implement this as a default :)
Thanks.

from pulumi-gcp.

This is now fixed.

from pulumi-gcp.