Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Allow to use --all-yes (-y) for plugins mass-update #985

Closed
memtkmcc opened this issue Aug 17, 2016 · 7 comments
Closed

Feature: Allow to use --all-yes (-y) for plugins mass-update #985

memtkmcc opened this issue Aug 17, 2016 · 7 comments

Comments

@memtkmcc
Copy link

It could be very useful for unattended upgrades we would like to include as an option in BOA support for Grav.

Currently it will still ask for confirmation per package, even if you will attempt to run bin/gpm update -f -y, like in the example below:

The package admin is already installed, overwrite? [y|N] y
Preparing to install Admin Panel [v1.1.4]
  |- Downloading package...   100%
  |- Checking destination...  ok
  |- Installing package...    ok
  '- Success!

The package login is already installed, overwrite? [y|N] y
Preparing to install Login [v2.0.1]
  |- Downloading package...   100%
  |- Checking destination...  ok
  |- Installing package...    ok
  '- Success!

The package email is already installed, overwrite? [y|N] y
Preparing to install Email [v2.4.3]
  |- Downloading package...   100%
  |- Checking destination...  ok
  |- Installing package...    ok
  '- Success!

The package form is already installed, overwrite? [y|N] y
Preparing to install Form [v1.3.2]
  |- Downloading package...   100%
  |- Checking destination...  ok
  |- Installing package...    ok
  '- Success!

It is also not immediately clear from the docs, that --all-yes (-y) is not expected to work for plugins updates, while it is supported for install, self-upgrade and even uninstall.

@rhukster
Copy link
Member

Yes, some consistency in options is needed I think. Thanks for the reminder! 👍

@rhukster
Copy link
Member

This is fixed for install but I know it's also broken in uninstall and i'll double check selfupgrade

@omega8cc
Copy link

Thank you! Would it be possible to do the same for update ? I think that it already works for selfupgrade, at least it worked for us, while trying to run packages update still asked question-per-package.

@rhukster
Copy link
Member

Yup, will check update also.

@rhukster
Copy link
Member

ok update also works now.

@omega8cc
Copy link

Amazing! Thank you :)

@memtkmcc
Copy link
Author

Works like a charm! Thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants