Make nettest address overridable
Clarification and motivation
After #417 (closed) and #391 (closed) nettest
constant alias should never appear in the interface, rather be provided to the scenario by nettest machinery. So I think we can make this alias parametrized.
Use case for that is the following: taking into account that we use one common node (separate for each protocol) by the entire Tezos team, sometimes I observe the issue with that my operations fail with counter mismatch - this is common when someone uses the same address in parallel. The only way to achieve the use of completely non-overlapping set of addresses in scenarios is to make it possible to use a different alias as a "rich address".
Acceptance criteria
-
nettestAddress
nettestAddressAlias
constant is renamed to serve only as a default value; all its usages are smartly updated (e.g.nmiResolveAddress
probably shouldn't exist at this moment); - It is possible to provide nettest address as parameter via tasty's CLI / env vars.
-
TODO
s in code are resolved, if any.
Edited by Konstantin Ivanov