seaneagan/gist:d74d49e7d98b667e0f1c5357b1525f28

## gistfile1.txt
The main utility of chart groups seems to be specifying the order in which to install/upgrade/delete charts.  Armada chart configs already allow specifying dependencies.  The only thing that should really matter about the order is that dependencies are installed/upgraded before dependents, and the reverse for a delete.  Thus it should be possible to topologically sort the dependency graph to determine this order, with some tie breaker e.g. alphabitical order by chart or release name.  This chart order could then be further segmented into (unsequenced) chart groups whose members have no dependencies on each other, and thus whose charts can potentially be installed/upgrade/deleted in parallel.

This could all be exposed in a backward compatible way via a new "auto" value for the "chart_groups" key in the armada manifest, or by defaulting to this when "chart_groups" is omitted.
	The main utility of chart groups seems to be specifying the order in which to install/upgrade/delete charts. Armada chart configs already allow specifying dependencies. The only thing that should really matter about the order is that dependencies are installed/upgraded before dependents, and the reverse for a delete. Thus it should be possible to topologically sort the dependency graph to determine this order, with some tie breaker e.g. alphabitical order by chart or release name. This chart order could then be further segmented into (unsequenced) chart groups whose members have no dependencies on each other, and thus whose charts can potentially be installed/upgrade/deleted in parallel.

	This could all be exposed in a backward compatible way via a new "auto" value for the "chart_groups" key in the armada manifest, or by defaulting to this when "chart_groups" is omitted.