You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally it was decided to error out if REPL_ACCOUNT was defined in the replacements file since the value will not be used. The account supplied to serve the components under always takes precedence and I believed not throwing an error would lead to confusion where a user doesn't realize their value in the replacements file is being ignored.
This has proven to be a headache, since replacement files may be shared between bos-loader and CI but REPL_ACCOUNT must be supplied in CI. In https://github.com/near/near-discovery-components we find ourselves needing to locally delete the REPL_ACCOUNT line from the replacements file in order to run bos-loader and then revert that change before committing.
If REPL_ACCOUNT is defined in the replacements file, we should print a warning message that the value is not being used but otherwise proceed with normal execution
The text was updated successfully, but these errors were encountered:
Originally it was decided to error out if
REPL_ACCOUNT
was defined in the replacements file since the value will not be used. The account supplied to serve the components under always takes precedence and I believed not throwing an error would lead to confusion where a user doesn't realize their value in the replacements file is being ignored.This has proven to be a headache, since replacement files may be shared between bos-loader and CI but
REPL_ACCOUNT
must be supplied in CI. In https://github.com/near/near-discovery-components we find ourselves needing to locally delete theREPL_ACCOUNT
line from the replacements file in order to run bos-loader and then revert that change before committing.If
REPL_ACCOUNT
is defined in the replacements file, we should print a warning message that the value is not being used but otherwise proceed with normal executionThe text was updated successfully, but these errors were encountered: