This works, but it would be a lot slicker if we could tag stages rather than overload the project name.
To take this one step further, it would be good to be able to not have to duplicate config, as it's only the stage that changes. Specifying this directly in the stage file rather than creating new config files would be ideal.
We're using capify-cloud and it's working well. We're also using multistage and we've found a way to get it working with capify-cloud:
Our stage files look like:
This allows us to load different configs for each stage where we're then overloading the project tag with an appended stage identifier:
This works, but it would be a lot slicker if we could tag stages rather than overload the project name.
To take this one step further, it would be good to be able to not have to duplicate config, as it's only the stage that changes. Specifying this directly in the stage file rather than creating new config files would be ideal.