This repository was archived by the owner on Mar 17, 2026. It is now read-only.
Merged
Conversation
clefrancq
approved these changes
Feb 24, 2025
damu46
force-pushed
the
fix/nonify_missing_attributes
branch
from
0d02cef to
7b65a96
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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
Currently, if a value is not specified in a configuration but existing in the target keycloak realm, it is marked as being removed when running the module in check mode.
However, when running the module in non-check mode, the value is not removed/cleared since the module does not set this existing value to "None" but instead simply send the "new configuration" without the corresponding key.
ISSUE TYPE
COMPONENT NAME
keycloak client module
ADDITIONAL INFORMATION