Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LB - Allow chaining of schema deployments for a release #83

Open
bferguso opened this issue May 24, 2023 · 0 comments
Open

LB - Allow chaining of schema deployments for a release #83

bferguso opened this issue May 24, 2023 · 0 comments

Comments

@bferguso
Copy link
Collaborator

Currently if there are multiple schema deployments happening for an application release the LB playbook needs to be run once per schema. This requires more effort and time because the local_vars.yml needs to be updated for every run. Possible improvement would be:

  1. Allow a list of schemas to be provided to the playbook
  2. Modify the liquibase playbook to take a list of schemas
  3. Change the pattern so that the ansible playbook reads variables from the local_vars.yml and then local_vars_.yml
  4. Modify the liquibase role so that it takes a list of schema names
  5. Modify the liquibase role so the cd-configure and jdk roles are dependancies of the liquibase role so that those roles are initiated every time (need to confirm that the dependency would run every time)
  6. Modify the playbook to list each application config before the first run of the chained set of deployments

Note that the chained applications will only continue as long as there are no errors in any of the runs. It will stop on the first error encountered so there is no additional risk by chaining them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant