Closed rmott-littler closed 6 months ago
Nifty; thanks for the PR!
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 91.18%. Comparing base (
54694fb
) to head (9031159
). Report is 1 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Motivation As a manager of a dozen applications at Acquia, I want to use
acli remote:drush
to perform routine tasks (especiallyuli
login) on multiple remote applications without remembering to type the correct--uri
every time. Previously with Drupal 7/drush 8/Acquia Cloud API v1 one could usedrush acquia-update
to easily keep local aliases up-to-date, but this is no longer an option.Proposed changes Since
remote:drush
is already fetching the Acquia environment information behind the scenes for the alias provided, it should pass along thedefault_domain
parameter when none is given by the user. Allow the user to continue to provide their own--uri
parameter if the default isn't sufficient (on a drush command, the last duplicate parameter wins).Alternatives considered Manually typing the correct
--uri
flag when needed for a drush command likeuli
is redundant and painful.Testing steps/example usage
acli remote:drush site.dev -- status --fields=uri
acli remote:drush site.dev -- uli
acli remote:drush site.dev -- uli --uri=https://example.com