Skip to content
This repository has been archived by the owner on Jan 19, 2018. It is now read-only.

Check status of target environment before deploy #501

Open
dustymabe opened this issue Jan 12, 2016 · 1 comment
Open

Check status of target environment before deploy #501

dustymabe opened this issue Jan 12, 2016 · 1 comment
Assignees

Comments

@dustymabe
Copy link
Contributor

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.

@dustymabe
Copy link
Contributor Author

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)

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

No branches or pull requests

2 participants