-
Notifications
You must be signed in to change notification settings - Fork 304
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
azuread_access_package_catalog_role not supporing AccessPackage assignment manager as display_name #1319
Comments
The correct syntax for the display names for these roles is Can be checked with GET on "/roleManagement/entitlementManagement/roleDefinitions" (https://learn.microsoft.com/en-us/graph/api/rbacapplication-list-roledefinitions?view=graph-rest-1.0&tabs=http) |
Thanks for the reply.
It works for "AccessPackages manager" but "AccessPackage assignment manager" throws: It works however with using the object id of the role: I will update the issue |
I tested the filter directly with the Graph API and it returned an empty list. Filtering on So seems like the issue is with the Graph API, not the provider. Perhaps there should be a note in the documentation warning about this, suggesting to use your workaround using the object ID directly (which is the same in all tenants, it seems). |
Thanks for reporting this @sklakegg, it does look like this is an API issue as we rely on query filters to do the heavy lifting here. |
Community Note
Terraform (and AzureAD Provider) Version
hashicorp/azuread v2.47.0
Affected Resource(s)
azuread_access_package_catalog_role
Terraform Configuration Files
Debug Output
Expected Behavior
Role is found, see docs: https://learn.microsoft.com/en-us/graph/api/rbacapplication-list-roledefinitions?view=graph-rest-1.0&tabs=http
Actual Behavior
Role is not found. It works however to use object_id:
Steps to Reproduce
Create a azuread_access_package_catalog_role data source with either "Access package manager" or "Access package assignment manager"
The text was updated successfully, but these errors were encountered: