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

Make email, project computed for GCE default service account #1690

Merged
merged 1 commit into from
Jun 22, 2018

Conversation

emilymye
Copy link
Contributor

Fixes #1686

@emilymye emilymye requested a review from danawillow June 21, 2018 23:04
@emilymye
Copy link
Contributor Author

TF_ACC=1 go test ./google -v --run="TestAccDataSourceGoogleComputeDefaultServiceAccount_basic" -timeout 120m
=== RUN TestAccDataSourceGoogleComputeDefaultServiceAccount_basic
=== PAUSE TestAccDataSourceGoogleComputeDefaultServiceAccount_basic
=== CONT TestAccDataSourceGoogleComputeDefaultServiceAccount_basic
--- PASS: TestAccDataSourceGoogleComputeDefaultServiceAccount_basic (1.35s)
PASS
ok github.com/terraform-providers/terraform-provider-google/google 1.548s

Copy link
Contributor

@paddycarver paddycarver left a comment

Choose a reason for hiding this comment

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

Why does this make email no longer user-specifiable? Isn't this a breaking change for users that would have had the email field specified?

I think it's justifiable in this case, as the field was documented to be un-specifiable. But I just wanted to check and see if my understanding of the situation was right, which is that it was Optional by mistake.

@danawillow
Copy link
Contributor

Yeah, if you look at the code email is never d.Get-ed (d.gotten?) so setting it wouldn't do anything anyway.

@emilymye
Copy link
Contributor Author

Should I still just go ahead and merge it in if it's a breaking change?

@danawillow
Copy link
Contributor

I'm very confident that this is not a breaking change.

@emilymye emilymye merged commit 2015b4a into hashicorp:master Jun 22, 2018
@paddycarver
Copy link
Contributor

Just chiming in late that now that I understand what's going on here, I also am 👍 on this being merged now and not considering it a breaking change.

@ghost
Copy link

ghost commented Nov 17, 2018

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 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Nov 17, 2018
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.

3 participants