Cannot set config for admin/url/use_custom using Magento CLI

[tylers-username]

Preconditions (*)

1. Magento 2.2.4
2. OS: Debian (Docker PHP)

Steps to reproduce (*)

1.Set the custom admin URL: bin/magento config:set admin/url/custom "https://admin.example.com/"
2. Enable the new custom URL path: bin/magento config:set admin/url/use_custom 1

Expected result (*)

1. Given that an admin URL has been defined, I expected the admin/url/use_custom to pass validation and to be added to core_config_data table with a value of 1.

Actual result (*)

1. The Magento Cli throws the exception message:

   Please specify the admin custom URL.

[m2-assistant]

Hi @tylerssn. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@tylerssn do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[tylers-username]

@magento give me 2.2.4 instance

[magento-engcom-team]

Hi @tylerssn. Thank you for your request. I'm working on Magento 2.2.4 instance for you

[magento-engcom-team]

Hi @tylerssn, here is your Magento instance.
Admin access: https://i-23232-2-2-4.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[tylers-username]

Can only confirm locally on a fresh 2.2.4 instance since I do not have shell access to the staging environment.

[m2-assistant]

Hi @shikhamis11. 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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[sunilit42]

@magento give me 2.3.1 instance

[magento-engcom-team]

Hi @sunilit42. Thank you for your request. I'm working on Magento 2.3.1 instance for you

[magento-engcom-team]

Hi @sunilit42, here is your Magento instance.
Admin access: https://i-23232-2-3-1.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.