-
Notifications
You must be signed in to change notification settings - Fork 310
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
New root level resource for Application Required Resource Access #800
Comments
Are there any plans on introducing this to the provider? |
Error: Invalid resource type on latestB2B.tf line 348, in resource "azuread_application_required_resource_access" "resource_appid": The provider hashicorp/azuread does not support resource type "azuread_application_required_resource_access". |
This is not an existing resource type, it was my suggestion for how this potentially could be implemented. |
We'll be adding the |
Incase others are looking for it, it seems to be here in the latest version: https://registry.terraform.io/providers/hashicorp/azuread/latest/docs/resources/application_api_access |
Community Note
Description
As a user of the provider, I would like the Application's required_resource_access to also be configurable as a root level resource, so I can have a template that deploys two separate applications that have required resource access permissions to each other.
Currently when attempting to do this, Terraform correctly throws an error that a circular dependency exists. However this is the desired state and it can be configured using the portal manually.
New or Affected Resource(s)
Potential Terraform Configuration
The text was updated successfully, but these errors were encountered: