Giving deployment plugins the power to spin up and shut down infrastructure would be fantastic. To accomplish this, we need to track what infrastructure is deployed, so it can be shut down when no longer declared and so duplicate deployment can be easily avoided.
My proposal is to use a dedicated git branch (named cloud maybe? or infrastructure? could be customizable).
This branch would store a YAML list of deployed infrastructure along with any necessary metadata, such as the plugin that was used to deploy it. If a plugin is uninstalled before shutting down its deployed infrastructure, an error will occur the next time saus deploy is run.
The saus deploy command would manage this git branch for you.
Giving deployment plugins the power to spin up and shut down infrastructure would be fantastic. To accomplish this, we need to track what infrastructure is deployed, so it can be shut down when no longer declared and so duplicate deployment can be easily avoided.
My proposal is to use a dedicated git branch (named
cloud
maybe? orinfrastructure
? could be customizable).This branch would store a YAML list of deployed infrastructure along with any necessary metadata, such as the plugin that was used to deploy it. If a plugin is uninstalled before shutting down its deployed infrastructure, an error will occur the next time
saus deploy
is run.The
saus deploy
command would manage this git branch for you.