powerplatform_user: added retry when user is not yet added to the dataverse #622
+12
−0
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 pull request includes several changes to the
internal/services
directory, focusing on adding a retry mechanism and minor code updates. The most important changes are listed below:Enhancements:
.changes/unreleased/fixed-20250306-154637.yaml
: Added a retry mechanism when the user is not yet added to the dataverse, ensuring more robust user management.Code updates:
internal/services/authorization/api_user.go
: Implemented a retry mechanism in theGetDataverseUserByAadObjectId
function to handle cases where the user is not immediately found.internal/services/environment/resource_environment.go
: Removed an extra newline for code cleanliness in theupdateCadence
function.