Magento option --magento-init-params never used when running cli?

[stijnveeke]

Preconditions and environment

• Magento version: 2.4.7-p2
• Default magento example project.

Steps to reproduce

1. Create a new Magento project
2. Enable Xdebug or any other tool to debug the CLI process
3. Setup breakpoint in the execute function of the command you want to run.
4. Execute command with the --magento-init-params option.

For my command I used the setup:upgrade command with the init params following the example.
magento setup:upgrade --magento-init-params="MAGE_MODE=production"
I also tried to run it without "In both instances, the command is run, but the params never change," following the exact example given when running setup:upgrade --help.

Expected result

I expect a change in the MAGE_MODE to production instead of development.

Actual result

MAGE_MODE does not change.

Additional information

I placed a breakpoint in the framework/console/Cli.php file on line 82. On line 81, a variable named $application is created, which contains another variable called serviceManager. Inside serviceManager, there is an array called services. Within this array is a key named config, which includes a key called magento-init-params. This key, in turn, contains argv, where the entire command is present.

This confirms that the parameters are correctly passed to the serviceManager, but they are not being utilized for some reason.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @stijnveeke. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[engcom-Hotel]

Hello @stijnveeke,

Thanks for the report and collaboration!

We have tried to reproduce the issue in the latest development branch i.e. 2.4-develop and the issue is reproducible for us. Please refer to the below screenshot for reference:

Hence confirming the issue.

Thanks

[m2-assistant]

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-13231 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Hotel. Thank you for verifying the issue.
Issue Available: @engcom-Hotel, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[stijnveeke]

Hey @engcom-Hotel, Can I get an update on this issue? Is it currently being worked on? It is confirmed, but I've not received feedback since last week. Is the removal from the Issue Confirmation and Triage Board a mistake or as intended? (I ask this because I see different issues that already have a PR, like Issue 39262, and they are still in the Triage Board, so the removal of this issue confuses me.)

[engcom-Hotel]

Hello @stijnveeke,

As I checked in its related JIRA i.e. https://jira.corp.adobe.com/browse/AC-13231, the status is implementation. But it is still waiting for the developer from internal and community.

Issue removal from Issue confirmation and triage board is expected, confirmed issue has been moved as per the process. And the #39262 is On hold that's why it is in this board.

Thanks