feat: update roleAssignments to the newest specs - batch 2

[krbar]

Description

roleAssignments - Update to newest specs (see #2008 for details)

Pipeline Reference

Pipeline

Type of Change

• Update to CI Environment or utilities (Non-module affecting changes)
• Azure Verified Module updates:
  • Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:
    • Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
    • The bug was found by the module author, and no one has opened an issue to report it yet.
  • Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
  • Breaking changes and I have bumped the MAJOR version in version.json.
  • Update to documentation

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• I have run Set-AVMModule locally to generate the supporting module files.
• My corresponding pipelines / checks run clean and green without any errors or warnings

[ahmadabdalla]

@krbar quick question: if someone was using a previous version of a module and used role assignments, has it been tested that their existing role assignments are not impacted and they won't get a duplicate RBAC error? Doesn't sound it should be an issue based on the updates, but just double checking. Thank you 🙏🏻

[AlexanderSehr]

@krbar quick question: if someone was using a previous version of a module and used role assignments, has it been tested that their existing role assignments are not impacted and they won't get a duplicate RBAC error? Doesn't sound it should be an issue based on the updates, but just double checking. Thank you 🙏🏻

Hey @ahmadabdalla,
it absolutely will be an issue. To help this, I tagged the corresponding issue and added a workaround for existing role assignments that are impacted here, essentially making use of the explicit name parameter.
Role assignments that would be affected are all that did not previously use the full role definition Id, but just the GUID or the name.