magento2: undefined index db-ssl-verify
Preconditions (*)
- current 2.4-develop
- ddev setup
Steps to reproduce (*)
Follow the install instructions at https://ddev.readthedocs.io/en/latest/users/cli-usage/#magento-2-quickstart and then try to change the backend frontend name using the ssh container.
bin/magento setup:config:set --backend-frontname=admin
Overwrite the existing configuration for backend-frontname?[Y/n]y
Overwrite the existing configuration for db-ssl-verify?[Y/n]n
In ErrorHandler.php line 61:
Notice: Undefined index: db-ssl-verify in /var/www/html/setup/src/Magento/Setup/Model/ConfigOptionsList/DriverOptions.php on line 49
Expected result (*)
- Result with no errors
Actual result (*)
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 18 (10 by maintainers)
Commits related to this issue
- ENGCOM-7236: fix: prevent undefined index error - closes #26762 #26763 - Merge Pull Request magento/magento2#26763 from DanielRuf/magento2:fix/26762-check-driver-option-exists - Merged commits: ... — committed to magento/magento2 by magento-engcom-team 4 years ago
- ENGCOM-7236: fix: prevent undefined index error - closes #26762 #26763 — committed to magento/magento2 by slavvka 4 years ago
Hi, I had the same problem while configuring Redis using Magento Dev Docs as a guide. Turns out thar by declaring these values in command line I could go further.
bin/magento setup:config:set --page-cache=redis --page-cache-redis-server=127.0.0.1 --page-cache-redis-db=1is the proposed command by Magento Dev Docs I wrote it like thisbin/magento setup:config:set --page-cache=redis --page-cache-redis-server=127.0.0.1 --page-cache-redis-db=1 --db-ssl-verify=/path-to/mysql/my.pemI don’t remember exactly which where the missing index, but it was a total of 4. So you can declare each one in command line. For me it worked. like thisbin/magento setup:config:set --page-cache=redis --page-cache-redis-server=127.0.0.1 --page-cache-redis-db=1 --db-ssl-verify=/path-to/mysql/my.pem --db-(other index)=path-to --db-(another index)=path-toBoth PRs will make it more stable and prevent such cases or errors that are not catched and cause issues in a later step.
I’m not from Magento team, I’m just sharing with you how I solved a similar error calling config:setup. I did some research on that new feature and I didn’t open an issue. I just said for you to try to declare those index while using config:setup. The same values that are declared in your env.php. I just think it is missing in Dev Docs files. So, you PR is relevant if you think so, but then it is up to Magento Administrators accept it or not according to their milestones and plans.