Re: [keycloak-dev] 1.2.beta1 planning, need you to defer things
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: "Stian Thorgersen" <stian(a)redhat.com>
Cc: keycloak-dev(a)lists.jboss.org
Sent: Thursday, 12 March, 2015 3:57:30 PM
Subject: Re: [keycloak-dev] 1.2.beta1 planning, need you to defer things
On 3/12/2015 10:41 AM, Stian Thorgersen wrote:
>>
>>> Before we can do a release we need to make sure that database migration
>>> works (I know they don't atm as social providers and social links are
>>> lost). We also need to add transformation of JSON exports and
>>> representations so older versions can be imported into 1.2.0.Beta1.
>>>
>>
>> Not sure, but json imports from older versions should be backwards
>> compatible. We're just doing migrations via json export/import right?
>
> No, we migrate the database directly.
> https://github.com/keycloak/keycloak/blob/master/misc/UpdatingDatabaseSch...
>
This direct database migration is just schema changes correct? I
already updated the 1.2.x liquibase migrater to put in my db schema
changes for protocol mappers.
No it should migrate data as well. We can write custom migration tasks for Liquibase and
Mongo that takes care of translating the data. It's just going to be much simpler and
quicker for users to upgrade that way than having to export/import to json. Especially if
they have a large db.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com