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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: