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

config:show command doesn't work with partial paths in newer versions #39610

Open
5 tasks
ioweb-gr opened this issue Feb 7, 2025 · 13 comments
Open
5 tasks

config:show command doesn't work with partial paths in newer versions #39610

ioweb-gr opened this issue Feb 7, 2025 · 13 comments
Labels
Area: Payments Component: Payment Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Reported on 2.4.x Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@ioweb-gr
Copy link
Contributor

ioweb-gr commented Feb 7, 2025

Preconditions and environment

  • 2.4.7-p2 doesn't work
  • 2.3.2 works

Steps to reproduce

Execute command

php bin/magento config:show payment

If you're in 2.3 versions like 2.3.2 this used to provide all the options under path payment

If you're in 2.4.x versions like 2.4.7 this fails with error The "payment" path doesn't exist. Verify and try again.

Expected result

All the options under the payment path show up.

Actual result

The "payment" path doesn't exist. Verify and try again.

Additional information

No response

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”.
Copy link

m2-assistant bot commented Feb 7, 2025

Hi @ioweb-gr. 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.


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-Bravo engcom-Bravo self-assigned this Feb 7, 2025
Copy link

m2-assistant bot commented Feb 7, 2025

Hi @engcom-Bravo. 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.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.x Indicates original Magento version for the Issue report. label Feb 7, 2025
@judelaw618
Copy link

In Magento 2.4.7, config:show no longer works with partial paths like payment, returning "The path doesn't exist" error. In 2.3.2, it worked as expected, listing all options under the given path.

Workaround:
Use the full path instead:

bash
Copy
Edit
php bin/magento config:show payment/<specific_option>
Or export all configurations and filter manually:

bash
Copy
Edit
php bin/magento config:show > config_dump.txt
This is a breaking change, affecting critical functionality with no direct workaround. Meanwhile, take a break and watch free movies online on FreeCine.

@engcom-Bravo
Copy link
Contributor

Hi @ioweb-gr,

Thanks for your reporting and collaboration.

As per this Magento devdocs https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/paths/config-reference-payment#international-paths we have to provide full path.Could you please refer the document and please let us know if you are still facing any issue.

Thanks.

@engcom-Bravo engcom-Bravo added the Issue: needs update Additional information is require, waiting for response label Feb 10, 2025
@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board Feb 10, 2025
@engcom-Bravo engcom-Bravo moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Feb 10, 2025
@ioweb-gr
Copy link
Contributor Author

Hi

I don't see any reference in the provided page about config:show with Ctrl+F

Just a list of configuration paths.

The issue I mentioned is the different behavior between versions.

In the past on 2.3.x it would work with partial paths but on 2.4.x it won't.

I believe partial paths were helpful as you wouldn't need to dump the whole config and use grep to find what you need which takes more time

@devchris79
Copy link

Easy workaround:

php bin/magento config:show | grep payment/

@ioweb-gr
Copy link
Contributor Author

I believe partial paths were helpful as you wouldn't need to dump the whole config and use grep to find what you need which takes more time

Yes yes @devchris79 as mentioned earlier that's the current workaround, just interested in why the behavior changed from 2.3 to 2.4

@engcom-Bravo
Copy link
Contributor

@hostep
Copy link
Contributor

hostep commented Feb 11, 2025

@engcom-Bravo: I don't see how bin/magento app:config:dump is relevant in scope of this conversation here.

@ioweb-gr: be careful with running bin/magento app:config:dump, it will update your app/etc/env.php and app/etc/config.php files, so make sure you keep a backup of those in case you want to revert them back to the original state.

@ioweb-gr
Copy link
Contributor Author

ioweb-gr commented Feb 11, 2025

Thanks @hostep I'm aware of app:config:dump and how it works. My question was about config:show which is supposed to retrieve the values of a configuration path for quick display. I'm curious why it changed how it works between 2.3 and 2.4 because ScopeConfigInterface can retrieve partial paths perfectly fine.

@engcom-Bravo
Copy link
Contributor

Hi @ioweb-gr,

Thanks for your Update.

We have tried to reproduce the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Image

The "payment" path doesn't exist. Verify and try again.

Hence Confirming the issue.

Thanks.

@engcom-Bravo engcom-Bravo added Component: Payment 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 Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Area: Payments and removed Issue: needs update Additional information is require, waiting for response labels Feb 12, 2025
@github-jira-sync-bot
Copy link

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

Copy link

m2-assistant bot commented Feb 12, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Payments Component: Payment Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Reported on 2.4.x Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
None yet
Development

No branches or pull requests

6 participants