-
Notifications
You must be signed in to change notification settings - Fork 107
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
templates/openshift: make the maintenance template generic #4112
Conversation
9b4960d
to
3672996
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will the DB maintenance then be remove from the composer.yml?
exactly, we'll just deploy the maintenance template twice, once for composer and once for the workers.
this is what we'd do in app-intf |
We could deploy this job for both composer and each tenant's workers that's present in app-intf. Then we can remove the maintenance bits from the composer template.
3672996
to
43076a8
Compare
probably with
as ENABLE_DB_MAINTENANCE is mandatory, right? 🤔 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
yea but the template sets it to false by default (required & default value just prevent it from being set to "") |
We could deploy this job for both composer and each tenant's workers that's present in app-intf. Then we can remove the maintenance bits from the composer template.