fix: fix TestAcc_ResourceMoveState_DirectoryRoleMember - #142
Draft
QixiaLu wants to merge 2 commits into
Draft
Conversation
QixiaLu
changed the title
TestAcc_ResourceMoveState_DirectoryRoleMember and the remaining TestAcc_ResourceMoveState_*TestAcc_ResourceMoveState_DirectoryRoleMember
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
1 participant
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.
There is a bug in the external
hashicorp/azureadprovider, which the move-state acceptancetests pinned to
3.0.2. In that version,azuread_directory_roleonly activates the rolewhen the Graph
ListDirectoryRolescall returns404. Graph actually returns200with anempty collection for a role that has not been activated in the tenant, so the provider fell
through to the
result was nilerror instead of activating the role.HashiCorp fixed this in azuread
3.3.0:Bump to 3.3.0 to fix relevant acctests