-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't create resource in GCP #2632
Comments
Hi @cvatsops. Thanks for posting your problem here. The error message suggests you need to set a project for your bucket. Did that not work? |
Hi @VenelinMartinov I have already set the gcp project using pulumi config set gcp:project project_name. |
Can you instead provide the example for GCP. |
Yeah, it looks like you are using Automation API. Please take a look at https://www.pulumi.com/docs/iac/packages-and-automation/automation-api/getting-started-automation-api/#configure-your-provider-plugins Also, a great place to find help with questions related to pulumi is the pulumi community slack channel: https://slack.pulumi.com/ |
You'd need to adapt the instructions for the GCP provider: https://www.pulumi.com/registry/packages/gcp/installation-configuration/#authenticate-using-the-cli to work with the automation API: https://www.pulumi.com/docs/iac/packages-and-automation/automation-api/getting-started-automation-api/#configure-your-provider-plugins something like: stack.set_config("gcp:project", auto.ConfigValue(value="my_project")) Note that the Automation API is a somewhat advanced feature, you might have an easier time starting off with one of the "Getting Started" guides. |
What happened?
Hello Team ,
I am trying to create a GCS bucket using pulumi as backend code which is serving via a fast api server .
Here's the request i am using to create the resource:
I have even setup the gcp project using pulumi config set gcp:project $projectname.
And below is the error i am facing:
Example
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: