This repository has been archived by the owner on May 25, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is more or less a copy and paste of the service account data source, with minimal changes to support the differences for a user account.
The Full Name field from the API is referenced as display_name in the data source - I wasn't sure if it should stay as display_name to be more like other objects or if it should be named
full_name
to match the API - happy to change it if needed.I have also implemented a user resource, but since they can not be created via API at this time I wasn't sure how to handle that just yet. In my implementation an error is thrown if you attempt to create a resource, the expectation being that they would be imported using
terraform import
- Didn't include it here as it doesn't seem like the proper way to implement the resource - the only changeable field being the full name field a data source seems all thats likely needed for most