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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reference users by on-prem SAM account name, when defining an azuread_group #709

Open
daramir opened this issue Jan 3, 2022 · 1 comment 路 May be fixed by #707
Open

Reference users by on-prem SAM account name, when defining an azuread_group #709

daramir opened this issue Jan 3, 2022 · 1 comment 路 May be fixed by #707

Comments

@daramir
Copy link
Contributor

daramir commented Jan 3, 2022

Community Note

  • Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritise this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritise the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

One of our requirements is to be able to lookup users by on-prem SAM account name, given it's the attribute that changes the least for a user across the organisation. For example, mail nickname might not be deterministic and email/UPN might vary across AD Domains for a single user.

Being able to rely on a more deeply rooted (and hence static-ish) field to reference a user by, simplifies the process of creating config "variations" such as test environments.

In order to achieve this, the User and Users Data Sources, have to support looking up users by on-premise SAM account name.

New or Affected Resource(s)

Data Sources

  • azuread_user
  • azuread_users

Potential Terraform Configuration

Ommited, will link a Pull Request

References

@daramir
Copy link
Contributor Author

daramir commented Jan 3, 2022

Have submitted a Pull Request for this: #707

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

Successfully merging a pull request may close this issue.

2 participants