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

Status check default behavior #10

Open
Shrobs opened this issue Mar 8, 2017 · 0 comments
Open

Status check default behavior #10

Shrobs opened this issue Mar 8, 2017 · 0 comments

Comments

@Shrobs
Copy link
Owner

Shrobs commented Mar 8, 2017

The current status check default behaviour is getting all the services that are running in the cluster, and checking their deployment status.
Also, if the used Master Configuration File only contains a small subsets of the services that are running in a cluster, we are still gonna check on services that are not defined in the MCF.
If we are deploying a single services, it doesn't make much sense to check all of the services.

The new default behaviour should be to check all of the services that are in the MCF, and not in the ECS cluster. We will also add an option that will specify a subset of services to check.

@Shrobs Shrobs changed the title Status check default behavior Status check/decommission default behavior Apr 11, 2017
@Shrobs Shrobs changed the title Status check/decommission default behavior Status check default behavior Apr 11, 2017
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