azurerm_role_management_policy - Support for resource scope

[swupdiedoowap]

Community Note

• Please vote on this PR by adding a 👍 reaction to the original PR to help the community and maintainers prioritize for review
• Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for PR followers and do not help prioritize for review

Description

As described in the documentation provided by Microsoft, role management policies can be configured on resource scope.
Currently the resource will fail with an error saying it is not an valid management group id:
parsing "/subscriptions/xxxx/resourceGroups/xxxx/providers/Microsoft.KeyVault/vaults/xxx": parsing segment "providers": parsing the ManagementGroup ID: the segment at position 0 didn't match.
Since resource scope is actually valid, I made the scope validation the same as of the other 'role type' resources, in order to allow it.

PR Checklist

• I have followed the guidelines in our Contributing Documentation.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.
• I have checked if my changes close any open issues. If so please include appropriate closing keywords below.
• I have updated/added Documentation as required written in a helpful and kind way to assist users that may be unfamiliar with the resource / data source.
• I have used a meaningful PR title to help maintainers and other users understand this change and help prevent duplicate work.

Changes to existing Resource / Data Source

• I have added an explanation of what my changes do and why I'd like you to include them (This may be covered by linking to an issue above, but may benefit from additional explanation).
• I have written new tests for my resource or datasource changes & updated any relevent documentation.
• I have successfully run tests with my changes locally. If not, please provide details on testing challenges that prevented you running the tests.
• (For changes that include a state migration only). I have manually tested the migration path between relevant versions of the provider.

Testing

• My submission includes Test coverage as described in the Contribution Guide and the tests pass. (if this is not possible for any reason, please include details of why you did or could not add test coverage)

--- PASS: TestAccRoleManagementPolicyDataSource_resource (125.02s)
--- PASS: TestAccRoleManagementPolicy_resource (162.81s)

side note: I had to ran the test with the primary_approver.object_id hardcored, since I don't have admin access to an Entra ID tenant in which I can create groups.

Change Log

Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.

• azurerm_role_management_policy - Support for resource scope

This is a (please select all that apply):

• Bug Fix
• New Feature (ie adding a service, resource, or data source)
• Enhancement
• Breaking Change

Related Issue(s)

closes #26396

[leonardotbo]

+1 for this PR
I cannot properly use the resource azurerm_role_management_policy until this is merged.

[katbyte]

Thanks @swupdiedoowap , LGTM 🎲

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.