[keycloak-dev] deprecated removals in future
stian at redhat.com
Fri Jul 17 09:21:03 EDT 2015
Yeah, so let's drop the SQL stuff. We'll only have one single realm provider which is backed by json representations. Then we store json representations in Mongo or as blobs in the database.
After that we only have to deal with one migration.
----- Original Message -----
> From: "Bill Burke" <bburke at redhat.com>
> To: "Stian Thorgersen" <stian at redhat.com>, "Marek Posolda" <mposolda at redhat.com>
> Cc: keycloak-dev at lists.jboss.org
> Sent: Friday, 17 July, 2015 2:33:31 PM
> Subject: Re: [keycloak-dev] deprecated removals in future
> I'm not spending a week+ writing error prone raw JDBC and generic JSON
> scripts. There's a lot of model migration code that would be a shit ton
> of raw SQL if you wanted to convert it. A new starting point would be
> half a days work.
> On 7/17/2015 2:28 AM, Stian Thorgersen wrote:
> > -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 at redhat.com>
> >> To: "Bill Burke" <bburke at redhat.com>, keycloak-dev at 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 at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/keycloak-dev
> Bill Burke
> JBoss, a division of Red Hat
More information about the keycloak-dev