keycloak-operator
keycloak-operator copied to clipboard
#508 Add identityProviderMappers to KeycloakRealm CR
Related GH Issue
Closes #508
I am very interested in this change, and I can work to add the needed test(s). Would you prefer I create my own fork from main
and copy in the changes that @Robbilie has already provided?
@zonybob @Robbilie Any of you guys working on the tests? Would be nice to have this feature.
@zonybob @Robbilie Any of you guys working on the tests? Would be nice to have this feature.
I really would like to work on these... I have two concerns about my path forward that have kept me from touching it...
- I know this project corresponds to the legacy/deprecated operator. Is there a path to make sure this feature is available in the new one as well?
- We use the OpenShift SSO operator, and given the legacy deprecation, I don't even know if fixing this here will ever make its way to an OpenShift SSO release?
@zonybob @Robbilie Any of you guys working on the tests? Would be nice to have this feature.
I really would like to work on these... I have two concerns about my path forward that have kept me from touching it...
- I know this project corresponds to the legacy/deprecated operator. Is there a path to make sure this feature is available in the new one as well?
- We use the OpenShift SSO operator, and given the legacy deprecation, I don't even know if fixing this here will ever make its way to an OpenShift SSO release?
I think the new Operator will have the feature, at least from the looks of their example CRD. The documentation of the Import CRD also specifies This CR should be created in the same namespace as the Keycloak Deployment CR, defined in the field keycloakCRName. The realm field accepts a full RealmRepresentation.
Regarding the OpenShift SSO, are refering to RH-SSO?
@zonybob @Robbilie Any of you guys working on the tests? Would be nice to have this feature.
I really would like to work on these... I have two concerns about my path forward that have kept me from touching it...
- I know this project corresponds to the legacy/deprecated operator. Is there a path to make sure this feature is available in the new one as well?
- We use the OpenShift SSO operator, and given the legacy deprecation, I don't even know if fixing this here will ever make its way to an OpenShift SSO release?
I think the new Operator will have the feature, at least from the looks of their example CRD. The documentation of the Import CRD also specifies This CR should be created in the same namespace as the Keycloak Deployment CR, defined in the field keycloakCRName. The realm field accepts a full RealmRepresentation.
Regarding the OpenShift SSO, are refering to RH-SSO?
Ok thanks... and yes, sorry, I meant RH SSO
This is being ported to the Realm Operator here: https://github.com/keycloak/keycloak-realm-operator/pull/4