Parity::Environment requires that --forced must be provided in order
to allow restoring the production database from a local backup, but it
is also passing that argument to Heroku CLI, which fails due to an
unexpected flag (see image below). Issue tested with:
heroku-toolbelt/3.43.13 (x86_64-linux)
heroku-cli/5.7.5-18ff676 (linux-amd64)
This change addresses the issue by:
Refactoring Parity::Environment to explicitly exclude --force from
the list of arguments passed to Heroku CLI.
Why:
--forced
must be provided in order to allow restoring the production database from a local backup, but it is also passing that argument to Heroku CLI, which fails due to an unexpected flag (see image below). Issue tested with:This change addresses the issue by:
--force
from the list of arguments passed to Heroku CLI.