Václav Muzikář
Václav Muzikář
Test results: https://github.com/vmuzikar/keycloak/actions/runs/20141187429/job/57810082705 (green)
Added some notes to the desc, fixed spotless. This should be now ready for full review. Thanks.
> However it does complicate the logic a little, and allows for name conflicts in the Kubernetes resources (without webhooks, you can have client type x and y with the...
@shawkins IMHO separate CRs are a better approach than a single one. It's better UX for the users that they see only fields relevant to given client type. If the...
> I could confirm in the openshift console how it presents structural schema in the editor Ok, let's explore that.
@shawkins Thanks for looking into this further. Sounds like the separate CRs is the way forward then?
@shawkins @mabartos @Pepo48 Wanted to ask for the review here.
@ahus1 We should probably try and test the new H2 version first in Keycloak to double check the original issue is truly gone.
Just to add a bit more context to what @shawkins stated. The current Admin REST API suffers from numerous issues and inconsistencies. Instead of trying to navigate the possible fixes...
@cherifyazid Thanks for understanding. Can we close this PR then?