Fixes an issue where microsoft.ad.user module failed on first run when adding a path value#246
Open
AllRWeak wants to merge 1 commit into
Open
Conversation
…hen adding a `path` value
|
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 55s |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
SUMMARY
This PR fixes an issue where the
microsoft.ad.usermodule fails on first run when adding thepathparameter to an a already existing user.ISSUE TYPE
COMPONENT NAME
microsoft.ad.userADDITIONAL INFORMATION
How to reproduce the error this PR fixes:
microsoft.ad.domainmodulemicrosoft.ad.usermodule to reconfigure any of the accounts created before DC promotion that are now domain accounts. Make sure the use thepathparameterThe module will fail but will still move the user to the
pathdefined. On second run of the module everything works.