Allow overriding proxy setting in .lando.local.yml

[monroecg]

It is useful to have multiple instances of the same project as different lando instances. E.g.: one for current long term feature change and one for quick hot fixes/code review. Saves a lot of time on swapping code in and out as needed.

All the settings such as app name and ports can be changed via a .lando.local.yml file EXCEPT the proxy settings.

There is no way to override or remove proxy settings in the .lando.yml file. You can add additional settings, however this causes main app requests to randomly bounce between the two lando instances. E.G. the repo lando config has something like:

name: my-app
...
proxy:
  appserver:
    - "*.my-sites.lndo.site"
   pma:
    - phpmyadmin.lndo.site
  mailhog:
  - mailhog.lndo.site

The .lando.local.yml has:

name: my-app2
...
proxy:
  appserver:
    - "*.my-sites2.lndo.site"
   pma:
    - phpmyadmin2.lndo.site
  mailhog:
  - mailhog2.lndo.site

This causes my-app2 to have the additive proxy settings:

proxy:
  appserver:
    - "*.my-sites.lndo.site"
    - "*.my-sites2.lndo.site"
   pma:
    - phpmyadmin.lndo.site
    - phpmyadmin2.lndo.site
  mailhog:
  - mailhog.lndo.site
  - mailhog2.lndo.site

This causes proxy confusion as to which lando instance to route to.

There should be a way to tell lando that the local config section is a replacement for the main config. Maybe a flag under the proxy section, eg:

proxy:
  replace: true
  appserver:

This would mean that secondary instances could be used without editing the main .lando.yml file and eliminate the danger of checking the new proxy settings into the code by accident.