app:config:import not works in 2.4.6-p9

[gdecaceresrES]

Preconditions and environment

• Magento version 2.4.6-p9
• Anything else that would help a developer reproduce the bug

Steps to reproduce

1. Change params in env.php file
2. go to frontend and view error : execute command line "app:config:import"
3. go to command line and execute the command "app:config:import"
4. review in the database the values are change with env.php file
5. In database not view the changes
6. in app:config:dump the changes are applied

Expected result

Update the system value in database

Actual result

No view changes in database

Additional information

Example System section in env.php

'system' => [
'default' => [
'catalog' => [
'search' => [
'engine' => 'opensearch',
'opensearch_server_hostname' => 'localhost',
'opensearch_server_port' => '9200',
'opensearch_index_prefix' => 'magento2',
'opensearch_enable_auth' => '0',
'opensearch_server_timeout' => '15'
]
],
'web' => [
'url' => [
'use_store' => 0
],
'unsecure' => [
'base_url' => 'https://my-domain.de/de/',
'base_link_url' => '{{unsecure_base_url}}',
],
'secure' => [
'base_url' => 'https://my-domain.de/de/',
'base_link_url' => '{{secure_base_url}}'
]
]
]

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 @gdecaceresrES. 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.

[hostep]

I think you have a misunderstanding of what app:config:import does. It doesn't replace the values in the database table core_config_data. It just ensures that all necessary steps are made so that the values defined in your env.php are being used in your shop instead of the values from your database.

So the config values from env.php (or config.php) will have a higher precedence over the config values in your database. But the values in the database won't be changed at all.

[gdecaceresrES]

thanks 4 your reply, i think the same, but in the pas, other teamates confirm executing app:config:import replace the values in the database.

i execute the dump and i see my changes, and its works, but i prefer confirm, yes or not replace the values in the database.
thanks 4 your support :)

[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.

[engcom-Hotel]

Hello @hostep,

Thank you very much for the clarification!

@gdecaceresrES as the issue is resolved for you, we are closing this.

Thanks for the collaboration!