v0.13.1

A configurable control-plane mount point

Where the control plane serves its portal API is now something an operator sets rather than a constant the portal was built with. The configured control-plane URL carries that mount point, prefix and all, and the portal appends only the API version and the operation — so the route can move without a portal release, and no deployment has to expose it under one fixed path.

Breaking for deployments that turn authorization on: a control-plane URL that pointed at a bare host now has to name the prefix the control plane actually serves under. Authorization is opt-in, so a portal with none configured is unchanged.

See spec/14-interface-binding.md for the authorization binding. (#150)

Full Changelog: v0.13.0...v0.13.1