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.

Sign up for GitHub

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

Jump to bottom

[Issue] Multiple arguments in module:status command #29344

Closed
4 tasks
m2-assistant bot opened this issue Jul 31, 2020 · 3 comments · Fixed by #28250
Closed
4 tasks

[Issue] Multiple arguments in module:status command #29344

m2-assistant bot opened this issue Jul 31, 2020 · 3 comments · Fixed by #28250
Assignees
@chandru-199
Labels
Component: Setup Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Priority: P3 May be fixed according to the position in the backlog. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. Triage: Done Has been reviewed and prioritized during Triage with Product Managers

Comments

@m2-assistant
Copy link

m2-assistant bot commented Jul 31, 2020 •
edited by engcom-Alfa
Loading

This issue is automatically created based on existing pull request: #28250: Multiple arguments in module:status command

Preconditions: (*)

As of now module:status command accepts only one parram. But module:enable and module:disable accepts multiple module names as argument. So, in same way module:status command also can accept multiple module names as argument.

Related Pull Requests

NA

Steps to reproduce (*)

  1. Run module:status command with multiple module names. ex php bin/magento module:status Magento_Version Magento_Wishlist.

Actual Result: ✖️ Too many arguments....

Screenshot from 2020-07-31 13-26-53

Expected Result: ✔️ We will get cli output in the following pattern.
Magento_Version : Module is disabled
Magento_Wishlist : Module is enabled

Screenshot from 2020-07-31 13-24-17

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)
@m2-assistant m2-assistant bot added Component: Setup Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Jul 31, 2020
@chandru-199 chandru-199 mentioned this issue Jul 31, 2020
Merged
5 tasks
@ghost ghost assigned chandru-199 Jul 31, 2020
@magento-engcom-team magento-engcom-team added the Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed label Jul 31, 2020
@magento-engcom-team magento-engcom-team added Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed and removed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed labels Jul 31, 2020
@engcom-Alfa engcom-Alfa added Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch labels Jul 31, 2020
@magento-engcom-team magento-engcom-team added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Jul 31, 2020
@magento-engcom-team
Copy link
Contributor

✅ Confirmed by @engcom-Alfa
Thank you for verifying the issue. Based on the provided information internal tickets MC-36380 were created

Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

@engcom-Alfa engcom-Alfa added Triage: Ready for Triage Issue is ready to me triaged with Product Manager Priority: P3 May be fixed according to the position in the backlog. Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. Triage: Done Has been reviewed and prioritized during Triage with Product Managers and removed Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. Triage: Ready for Triage Issue is ready to me triaged with Product Manager labels Jul 31, 2020
@slavvka slavvka added the Fixed in 2.4.x The issue has been fixed in 2.4-develop branch label Aug 8, 2020
@slavvka
Copy link
Member

slavvka commented Aug 8, 2020

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #28250 by @chandru-199 in 2.4-develop branch
Related commit(s):

The fix will be available with the upcoming 2.4.1 release.

@slavvka slavvka closed this as completed Aug 8, 2020
@ghost ghost removed the Progress: ready for dev label Aug 8, 2020
@ghost ghost added the Progress: done label Aug 8, 2020
@sdzhepa sdzhepa mentioned this issue May 10, 2022
Open
@DomPixie
Copy link
Contributor

Another solution is to use backticks and grep

php bin/magento module:status `bin/magento module:status | grep Swissup`

Swissup_Navigationpro : Module is enabled
Swissup_Ajaxpro : Module is enabled
Swissup_Core : Module is enabled
Swissup_Amp : Module is enabled
Swissup_Askit : Module is enabled
Swissup_Attributepages : Module is enabled

etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chandru-199 chandru-199

Labels
Component: Setup Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Priority: P3 May be fixed according to the position in the backlog. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. Triage: Done Has been reviewed and prioritized during Triage with Product Managers
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Multiple arguments in module:status command chandru-199/magento2
5 participants
@slavvka @magento-engcom-team @chandru-199 @engcom-Alfa @DomPixie