[Feature Request] Preserve variables set by previous corrals in order to `daisychain` corral runs

[slickwarren]

Use case:

• say we have 2 corral packages, corral1 and corral2.
• Corral2 depends on some variables to be set that corral1 creates
• if we run corral1 without cleaning up, the vars are not set for corral2 to use

example:

• corral package create_rancher_server with --skip-cleanup set runs on a given setup
  • this sets the kubeconfig value
• user runs a second corral package that uses the kubeconfig to modify the cluster
  • currently, user gets an error that the value is not set

this might be a limitation of TF, but maybe there's a way to get corral to work. I found that you can pull variables from other modules, but this isn't quite what I'm looking for, as I still want corral2 to be used without depending solely on corral1

[git-ival]

This isn't a limitation of TF, since you can add an output for anything you may want to make availabe for other modules to consume. AFAIK a possible workaround would be to have an overlay script that runs corral set <your corral variable> for each variable you want to consume as part of the chain of templates, it should set the global corral config for each variable