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
{{ message }}
This repository has been archived by the owner on Jan 19, 2018. It is now read-only.
We should check the status of the target environment before we start deploying artifacts. If we have 4 artifacts to deploy:
etherpad rc
etherpad svc
mariadb rc
mariadb svc
Then we should check to see what exists in the target environment before we start to deploy. If any of them exist before then we shouldn't attempt to deploy any of them.
The text was updated successfully, but these errors were encountered:
Anyone who picks up this issue should not worry about doing it on the kubernetes provider until we migrate kubernetes to use the API. (i.e. do kubernetes last)
We should check the status of the target environment before we start deploying artifacts. If we have 4 artifacts to deploy:
etherpad rc
etherpad svc
mariadb rc
mariadb svc
Then we should check to see what exists in the target environment before we start to deploy. If any of them exist before then we shouldn't attempt to deploy any of them.
The text was updated successfully, but these errors were encountered: