Skip to content

Datasource for retrieving GCS service account #8

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

Merged
merged 1 commit into from
Feb 15, 2018

Conversation

ishashchuk
Copy link

Simple datasource to get a GCS service account

@ishashchuk ishashchuk requested a review from amoiseiev February 13, 2018 22:41
@ishashchuk ishashchuk force-pushed the data_gcs_account branch 3 times, most recently from 1262045 to 88790d3 Compare February 15, 2018 15:34
@amoiseiev amoiseiev merged commit 40a3cd2 into wayfair_master Feb 15, 2018

The following attributes are exported:

* `id` - The ID of the service account, which is its email_address

Choose a reason for hiding this comment

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

any particular reason we need two attributes that are the same?

Copy link
Author

Choose a reason for hiding this comment

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

All datasources have to have ID set, and that's how they get stored in state file. I wanted to have email_address as an additional attribute, since it's consistent with what API returns and with what people would probably be looking for intuitevely. No real reason to have "email_address", other than consistency with API. What do you think? Leave as is or remove it ?

@amoiseiev
Copy link

Open upstream issue: hashicorp#1105

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants