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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.
Description
When utilizing multiple subscriptions, generating a single service principal is beneficial for cross-subscription pipelines. This requires being able to reference the subscription on top-tier settings that can / may affect multiple subscriptions.
I would propose for the following resources:
azurerm_monitor_activity_log_alert
azurerm_key_vault_secret
If the subscription is Optional, then the client provider is taken, otherwise it uses the specified subscription.
With the azurerm_key_vault_secret, the secret can be created but then it reads it incorrectly so you have to use a provider alias on the module in order to report "no changes". otherwise, it will try to recreate the secret every time. Import was tried and that also failed.
Is there an existing issue for this?
Community Note
Description
When utilizing multiple subscriptions, generating a single service principal is beneficial for cross-subscription pipelines. This requires being able to reference the subscription on top-tier settings that can / may affect multiple subscriptions.
I would propose for the following resources:
azurerm_monitor_activity_log_alert
azurerm_key_vault_secret
A previous example is 23673 solved by 24258
If the subscription is Optional, then the client provider is taken, otherwise it uses the specified subscription.
With the azurerm_key_vault_secret, the secret can be created but then it reads it incorrectly so you have to use a provider alias on the module in order to report "no changes". otherwise, it will try to recreate the secret every time. Import was tried and that also failed.
New or Affected Resource(s)/Data Source(s)
azurerm_monitor_activity_log_alert, azurerm_key_vault_secret
Potential Terraform Configuration
References
#23673
#24258
The text was updated successfully, but these errors were encountered: