[FEATURE]: conditionally deploy services that have a dependency on another service when it is deployed

[tedchang77]

Feature Request

Background / Motivation

we have service-b that has a dependencies on service-a and also consumes an output from service a.. for example a dns entry. when we change service-a's outputs and re-deploy service-a, service-b has stale values causing it to not be able to connect to service-a. we need to then redeploy service-b to pick up the new output values.

What should the user be able to do?

automatically deploy services that have a dependency on the service that is being deployed. should be able to specify if you only want to deploy if the dependent service is already running or deploy if its missing.

Why do they want to do this? What problem does it solve?

not having to redeploy dependent services yourself

Suggested Implementation(s)

a couple of options added to the deploy command: --with-dependants and --update-only, the rormer willatter indicating that missing services should not be deployed.

How important is this feature for you/your team?

🌵 Not having this feature makes using Garden painful

[stale]

This issue has been automatically marked as stale because it hasn't had any activity in 90 days. It will be closed in 14 days if no further activity occurs (e.g. changing labels, comments, commits, etc.). Please feel free to tag a maintainer and ask them to remove the label if you think it doesn't apply. Thank you for submitting this issue and helping make Garden a better product!

[stale]

This issue has been automatically marked as stale because it hasn't had any activity in 90 days. It will be closed in 14 days if no further activity occurs (e.g. changing labels, comments, commits, etc.). Please feel free to tag a maintainer and ask them to remove the label if you think it doesn't apply. Thank you for submitting this issue and helping make Garden a better product!

[stale]

This issue has been automatically marked as stale because it hasn't had any activity in 90 days. It will be closed in 14 days if no further activity occurs (e.g. changing labels, comments, commits, etc.). Please feel free to tag a maintainer and ask them to remove the label if you think it doesn't apply. Thank you for submitting this issue and helping make Garden a better product!

[Orzelius]

@tedchang77 sorry for taking so long with this, but it has been implemented via #4786.

For the --update-only flag could you perhaps create a separate issue if you still feel the need for it.