The way things are right now, an update to docker-compose.yml will leak to main net, even if there is no release tag.
I scoped this taking into account the different "environments" we currently support. Note that this is a rather loose notion.
The gist here is to fetch the right tag/branch from Github and use that to scope the docker compose files to the desired environment.
We default to fetching the latest numeric tag (which is the case for main net);
For test net, we get whatever's on the main branch;
For canaries, we get the latest canary tag;
For core L1s, which have a slightly different config, we get whatever's on their branch (i.e. core-L1).
The way things are right now, an update to docker-compose.yml will leak to main net, even if there is no release tag. I scoped this taking into account the different "environments" we currently support. Note that this is a rather loose notion.
The gist here is to fetch the right tag/branch from Github and use that to scope the docker compose files to the desired environment.
core-L1).This PR works in tandem with https://github.com/filecoin-saturn/ansible/pull/2.
Also note this whole approach is only compatible with the way we tag right now. If there is any change, this will break.