You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @erlacherl-city, thanks for requesting this! Good news - the azuread_service_principal data source happily supports this already. The attribute you want is application_id, which is just another name for client_id.
Additionally, we recently added support for the application_id (e.g. the client_id) argument to the azuread_application data source. This will be in our next release v0.11.0 - see #274
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
locked and limited conversation to collaborators
Jul 26, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Description
Azure supports querying service principals by client id:
The client id is also the only thing that the
data.azure_kubernetes_cluster
data provider surfaces for theservice_principal
.The
data.azuread_service_principal
data provider only supports using display name, object id, and application name.This means, there is no way to get from an existing aks cluster to the object id of its service principal.
New or Affected Resource(s)
Potential Terraform Configuration
The text was updated successfully, but these errors were encountered: