-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
keycloak_realm: fix default groups and roles (#4241) #4719
keycloak_realm: fix default groups and roles (#4241) #4719
Conversation
Can you please add a changelog fragment? Thanks. |
done 👍 |
@@ -0,0 +1,2 @@ | |||
bugfixes: | |||
- "keycloak_realm - fix default groups and roles (https://github.com/ansible-collections/community.general/issues/4241)." |
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.
- "keycloak_realm - fix default groups and roles (https://github.com/ansible-collections/community.general/issues/4241)." | |
- "keycloak_realm - fix types for ``default_groups`` and ``default_roles`` options from lists of dictionaries to lists of strings (https://github.com/ansible-collections/community.general/issues/4241)." |
@eikef @kris2kris @ndclt could you please take a look at this change? Thanks. |
Hi, |
@kris2kris that makes sense, but it needs to be deprecated first so it can be removed in a later version. I suggest the following:
Does that sound good? |
If nobody complains until in ~4 hours I'll merge this. (I'm planing to do a 5.0.1 release today around then, then this can go into that release.) |
Backport to stable-4: 💚 backport PR created✅ Backport PR branch: Backported as #4753 🤖 @patchback |
Backport to stable-5: 💚 backport PR created✅ Backport PR branch: Backported as #4754 🤖 @patchback |
@adam-cleo thanks for fixing this! |
Hi @kris2kris , @felixfontein , default realms was removed from official documentation. But it still flies under the radar in the latest version. They map the legacy value here . I tested that with version 16.1.1 So the way in current keycloak is to have one default and then add composites . There are separate GET, POST, DELETE method to add the composites see here, but i guess it should be enough to send them in the main call with the RealmRepresentation ( |
SUMMARY
Fixes #4241
Fixed attributes
default_roles
anddefault_groups
to match Keycloak APIISSUE TYPE
COMPONENT NAME
keycloak_realm
ADDITIONAL INFORMATION
Only checked and fixed
default_roles
anddefault_groups