Copied from Slack discussion:
For deploys to BRC environments the HST host configuration needs to be part of the distribution.
To allow for different environment names currently the bootstrap configuration uses a property for one url element ${od2_environment} that is replaced by Maven during the build fo the distribution. This hard-binds a distribution to a specific environment name

Instead of doing a build time replacement, we can also support it more flexible: Keep it as ${od2_environment} in the dist, and just bootstrap the jcr node as ${od2_environment} : then the HST can replace this runtime with a system property or an hst-config property provided by BRC.
Support for this in the HST should not be so hard (of course only the jcr path is then ${od2_environment} while host path is replaced so have to make sure never a jcr node lookup is done by the replaced node name...think this happens perhaps when adding new channel from blueprint)

Note that ${od2_environment} contains only environment name, the rest parts of the url are hardcoded like (onehippo/io). Ideally we would need to provide full host name in the runtime and get the hst configuration based on that. It also would be good to get that property from BRC when they run new environment because they have all the parts so we do not need to do anything in the script. We could leave the runtime property for the script for flexibility, but HST should take it and build entire host configuration

Addendum

we should bootstrap

${brc.environmentname}-${brc.stack}

where these placeholders are replaced with system properties. Note that brc.environmentname is present already by default as system prop in BRC