1.10.0+ breaks corporate proxy solution #236
Description
This recent change appears to break a known solution for working in a corporate proxy environment (https://docs.lando.dev/guides/lando-corporate-network-tips.html#add-cert-to-individual-lando-containers).
Up until now, I have been able to use build_as_root as a way to get our corporate cert into the appserver container prior to the tool downloading phase so that curl requests complete successfully.
With this change, user defined build_as_root commands appear to run after tool installation resulting in SSL errors. I confirmed this by adding an echo statement to the start of my user defined build_as_root commands and noting that it appeared after the failed composer download.
Example (without SSL errors, demonstrating order only):
services:
appserver:
build_as_root:
- echo "USER DEFINED BUILD AS ROOT"
✔ Container test_appserver_1 Started 0.4s
All settings correct for using Composer
Downloading...
Composer (version 2.9.5) successfully installed to: /usr/local/bin/composer
Use it: php /usr/local/bin/composer
Installing MySQL 8.0 client...
MySQL 8.0 client activated from pre-downloaded binaries
mysql Ver 8.0.45 for Linux on aarch64 (MySQL Community Server - GPL)
USER DEFINED BUILD AS ROOT
Example with prior release:
✔ Container test_appserver_1 Started 0.4s
USER DEFINED BUILD AS ROOT
All settings correct for using Composer
Downloading...
Composer (version 2.9.5) successfully installed to: /usr/local/bin/composer
Use it: php /usr/local/bin/composer
Drush Commandline Tool 13.6.2.0