-1 It'll actually be more work to drop backwards compatibility for the model as
we'd have to write a new "starting" point. For JSON representations it's
just messy and has deprecated stuff in it because I did a crap job at implementing it. If
we write a proper way to migrate json representations we won't need this and it'll
just be a transformation pipeline that transforms the json to match the representation
classes.
----- Original Message -----
From: "Marek Posolda" <mposolda(a)redhat.com>
To: "Bill Burke" <bburke(a)redhat.com>, keycloak-dev(a)lists.jboss.org
Sent: Friday, 17 July, 2015 8:24:50 AM
Subject: Re: [keycloak-dev] deprecated removals in future
+1
Hopefully we can drop backwards compatibility for JSON reps between 1.X
and 2.0 (ie. realm JSON representation exported in 1.X is not supposed
to work to be imported in 2.0). That will allow us to drop old metadata
from JSON and models and just create DB migration scripts for 1.X to 2.0
migration.
Marek
On 17.7.2015 02:29, Bill Burke wrote:
> We're accumulating deprecated metadata in models and data model.
> Eventually we should draw a line in the sand and say we will only
> support migration from a certain version to current.
>
> i.e. Keycloak 2.0 would only allow migration from the last 1.x version.
>
> We need to clean all the old stuff out prior to product.
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev