Role assignment retry for service principal #2204
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR looks to address issue https://github.com/terraform-providers/terraform-provider-azurerm/issues/1635, where a newly created service principal was not available for a role assignment.
There were a couple of merged PRs - PR #1647 and PR #1934 - that addressed issue https://github.com/terraform-providers/terraform-provider-azurerm/issues/1635. The role assignment create would retry, but it wouldn't retry on the error that was being returned when the created service principal wasn't available yet (400 PrincipalNotFound).
Test results for service principals:
Test results for role assignments:
I'm open to suggestions and ideas towards this possible fix.