[Issue] Prevent "Overwrite the existing configuration for db-ssl-verify?" question

[m2-assistant]

This issue is automatically created based on existing pull request: #26818: Prevent "Overwrite the existing configuration for db-ssl-verify?" question

---

Summary (*)

Magento 2.4-develop
This question is occurred every time I run:

$ ./bin/magento setup:config:set

after upgrade to 2.3.4

Also see #26762

We should ask this question only if new value of configuration option is not equal to the old value,.

Examples (*)

Proposed solution

[m2-assistant]

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

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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.

[magento-engcom-team]

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

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

[magento-engcom-team]

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

• 5f9897575102a63501d6909f3ac5a11a19969a3d
• cf1a716e7a40acc30e763b0b68ca2e6f9ba85cac
• 5c23f4d24d6ff9c95f50ba3378498676ba548eb4
• 23aa8067a9d5a5d99a7851d63bf5eb486508f168

The fix will be available with the upcoming 2.4.2 release.