Summary
mw domain virtualhost supports create / delete / get / list, but there's no way to update the paths of an existing virtual host.
Why this is a problem
Re-pointing a path to a different app or URL — common during a migration cutover or reconfiguration — currently requires either delete + recreate (disruptive: drops the ingress and momentarily its cert association) or dropping to the raw API:
PATCH /v2/ingresses/{ingressId}/paths — see Update the paths of an Ingress.
Proposed solution
Add mw domain virtualhost update (or a mw domain virtualhost paths subcommand) that wraps PATCH /v2/ingresses/{ingressId}/paths, so the path → target mappings of an existing virtual host can be edited in place — reusing the --path-to-app / --path-to-url flags already accepted by mw domain virtualhost create.
Impact
Lets routing changes happen in place during migrations and reconfigurations, without a delete/recreate cycle or hand-rolled API calls.
CLI version: 1.18.0.
Summary
mw domain virtualhostsupportscreate/delete/get/list, but there's no way to update the paths of an existing virtual host.Why this is a problem
Re-pointing a path to a different app or URL — common during a migration cutover or reconfiguration — currently requires either delete + recreate (disruptive: drops the ingress and momentarily its cert association) or dropping to the raw API:
PATCH /v2/ingresses/{ingressId}/paths— see Update the paths of an Ingress.Proposed solution
Add
mw domain virtualhost update(or amw domain virtualhost pathssubcommand) that wrapsPATCH /v2/ingresses/{ingressId}/paths, so the path → target mappings of an existing virtual host can be edited in place — reusing the--path-to-app/--path-to-urlflags already accepted bymw domain virtualhost create.Impact
Lets routing changes happen in place during migrations and reconfigurations, without a delete/recreate cycle or hand-rolled API calls.
CLI version: 1.18.0.