Kickstart-style migrations

Open atrauzzi opened this issue 5 years ago • 8 comments

Kickstart-style Migrations

Problem

Kickstarting is so helpful for the first-run setup, but I think what would be better is if we had a way to also provide configuration changes over time.

Solution

Similar to how there are migration libraries for databases, the kickstart process should support running and tracking the "ran-state" of timestamped kickstart scripts, in order.

Alternatives/workarounds

Right now I think the only way to make changes after a kickstart has happened is to do so manually through the UI, via direct SQL (unsupported) or via the API.
Use the terraform provider instead of kickstart

Additional context

Given that kickstart already exists, this seems like a sensible addition. Configuration upgrades would be possible by restarting the container with the additional files bound in.

https://github.com/FusionAuth/fusionauth-issues/issues/1379
https://github.com/FusionAuth/fusionauth-issues/issues/526

How to vote

Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.

Apr 18 '20 15:04 atrauzzi

Kickstart-style migrations