Re: [keycloak-dev] issue supporting older migrations
The generic migration is very cool, but there is problem that it has
hard dependency on the API, so you can't easily remove the stuff from
model API...
How about deprecate UserFederationProviderModel and deprecate all
UserFederationProviderModel CRUD methods on RealmModel? Or maybe even
remove those CRUD methods from RealmModel, but keep them just on JPA
RealmAdapter and Mongo RealmAdapter? The MigrateTo1_3_0 would need to
cast the RealmModel somehow to particular RealmAdapter though.
Marek
On 23/11/16 16:35, Bill Burke wrote:
Not sure I have time to port those migration scripts to Liquibase
and
Mongo specific migration scripts. Its a day or more of work to
implement and manually test.
FYI, its actually any version < 1.9.0 as there are generic LDAP
migration scripts for 1.8.0 as well.
On 11/23/16 4:05 AM, Stian Thorgersen wrote:
> I vote against that. There's a lot of users that are still on older
> versions. We could ask them to upgrade to 1.9.8 first, but there's a
> chance that could fail (we've seen this a few times) and as they can't
> upgrade to the most recent version we can't fix it either.
>
>
> On 22 Nov 2016 21:57, "Bill Burke" <bburke(a)redhat.com
> <mailto:bburke@redhat.com>> wrote:
>
> In removing UserFederationModel I found that we have generic Migration
> objects that use this api to upgrade LDAP. Specifically in
>
> 1.3.0
>
> 1.4.0
>
> I vote we don't support migration anymore for anything older than
> 1.9.8
>
>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org <mailto:keycloak-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
> <https://lists.jboss.org/mailman/listinfo/keycloak-dev>
>
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev