You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Allow a list of schemas to be provided to the playbook
Modify the liquibase playbook to take a list of schemas
Change the pattern so that the ansible playbook reads variables from the local_vars.yml and then local_vars_.yml
Modify the liquibase role so that it takes a list of schema names
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)
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: