Closed geronimo-iia closed 6 years ago
To continue, we can with Jinga we can do things like:
{% set bucket_name = 'testing-plateform' if (env('SELECTOR') == 'test') else 'other-plateform' %}
So, a configuration selector is not so "nice to have". May just adding some doc in readme for this use case
Yes I think the docs should be clearer about the possibilities of the configuration file.
for more complexe usage like call an update on a substack with feed of their dynamic parameter, it's more simple to define another yaml file. https://github.com/flou/brume/pull/6
With a second pull, I like to add a way to define parameter from outputs of another stack
Hi, I thing an optional configuration file selector could be a nice to have. Something like
By this way, we can use same set of troposhere template against several aws account.
If you're agree i can make a pull request :)
See you