When you configure a chain of rig project scripts several layers deep, and the bottom-most layer fails, this will trigger failures up the stack. As a result, you will get multiple "shouty" outputs as each project script fails.
Solution: When rig-project script is invoked, have it set the power users environment variable such that only the outer-most script "shouts".
This will require taking care to merge the existing env vars from the environment with this new variable to avoid causing a regression.
When you configure a chain of rig project scripts several layers deep, and the bottom-most layer fails, this will trigger failures up the stack. As a result, you will get multiple "shouty" outputs as each project script fails.
Solution: When rig-project script is invoked, have it set the power users environment variable such that only the outer-most script "shouts".
This will require taking care to merge the existing env vars from the environment with this new variable to avoid causing a regression.