Skip to content
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

Store project and region in state #784

Merged
merged 2 commits into from
Nov 28, 2017

Conversation

rosbo
Copy link
Contributor

@rosbo rosbo commented Nov 23, 2017

As of now, we store the project in region in the state for some resources and not for others.

This PR addresses this by consistently marking the project and region fields as Computed: true and storing it in the state inside the read method.

The main benefits apart from being consistent is that in acceptance tests, we can rely on the project property being set instead of having to do the same fallback logic that we do in the resource again (i.e. check in schema, if not set fallback to config.Project).

d.Set("project", varProject)
}

d.Set("project", varProject)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: the project parameter is unused now

@rosbo rosbo merged commit 6c5d6b7 into hashicorp:master Nov 28, 2017
@rosbo rosbo deleted the standardize-project-region-fields branch November 28, 2017 00:32
modular-magician added a commit to modular-magician/terraform-provider-google that referenced this pull request Sep 27, 2019
Signed-off-by: Modular Magician <magic-modules@google.com>
@ghost
Copy link

ghost commented Mar 30, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants