1

we have multiple clusters - like 6 - and of course, as a dev makes changes to an application and it is deployed it will migrate the table data and so on by flyway/liquibase.

But what if there is the need for a new user?

Where does the dev "show up" to define the user needed for a specific task in the database?

Or say we need a new wholedatabase or so.

And will this migration work. Let's say we have a single microservice which did not need the user User in version 1.7.0. But now, in 1.8.0 it will need the user. So before we deploy 1.8.0 on a certain cluster, we will want to add the user.

How is it done in an Continuous Deployment environemtn?

Improve this question

1 Answer 1

Reset to default
0

You will add flyway migration as it is, nothing special and than this migration will be applied before the application is opened for service.

There is no specific difference between versions as far as flyway migrations concerns.

If they are master slave than migration can be applied on master instances only.

Improve this answer
3
  • But you won't add users or whole new databases by flyway right?
    – Chris Pillen
    Oct 4, 2021 at 7:07
  • we can add users, whole new database via flyway migration it all depends that do we have later available as migration. For large db we can write another job to copy from somewhere and push them in initdb script of docker etc
    – Siddique Ahmad
    Oct 4, 2021 at 10:32
  • Well, the latter is what interessts me. How is that done correctly?
    – Chris Pillen
    Oct 5, 2021 at 21:17

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.