Comments
1 comment
-
The workflow piece (approval process) is down to how you setup and use Github so I'd familiarize myself with that first ("can I get a GH action to run when someone commits something ?") - something like this maybe: https://docs.github.com/en/actions/quickstart
It's going to be the same sequence for a Flyway migration as for any other commit.
There is also some simple information on using the Flyway docker image here: https://documentation.red-gate.com/fd/quickstart-docker-205226373.html
I'm suggesting docker as it makes updating easy and your GH action can get the tools it needs easily.
Once you're familiar with that side we have some examples for using Flyway in GH too - https://documentation.red-gate.com/fd/github-dockerized-yml-pipeline-using-github-actions-188645384.html
This demonstrates everything Flyway can do and it and assumes you have a license key - the license key isn't required for basic operations like info and migrate though. I'd use this as inspiration rather than a immediate solution though.
Add comment
Please sign in to leave a comment.
I'm new to setting up and using source control. I have been experimenting with Flyway and have a project setup and ready to share with a couple of developers to test it out. I'm not clear on setting up the actual deployment of the changes. For example, can we setup and approval process? If a developer makes a change, pushes it to Github, can we send a notification there is a new object there? Once reviewed, can we push it to prod? Can we setup an approval process for the developers and allow them to push it when approved? If this is all in a manual or doc I would be fine reading it through. But I'm just not sure where to look for all this.
Thanks everyone.