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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1012 remote state managed scopes #1176
1012 remote state managed scopes #1176
Changes from all commits
1eb26a4
bac397d
454e84a
bf63f23
620fe86
045f0e7
f87dcf5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why remove the test implimentation for the scope-mapping ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the Test Was Changed:
Why the Test Was Changed:
The test was updated to reflect the expected behavior after the import, where the scope-mapping for
scope-mapping-client
should remain in the scope mappings. This aligns with the updated configuration, wherescope-mapping-client
is not deleted during the import.The number of scope mappings has increased to 3 because the deletion of
scope-mapping-client
was not expected, and we need to accurately represent the realm's state after the import.Additionally, the change in the CLI option
--import.managed.scope-mapping
fromfull
tono-delete
was causing conflicts in the test. The updated test now reflects this change and ensures that the scope-mapping forscope-mapping-client
remains, as intended by the configuration.