Fix
v0.0.16-beta·Per-project network isolation, connecting managed resources, multi-line secrets
Security
- Every project now has its own network to the managed database. A single network held them all: containers belonging to different customers sat on it together and could reach one another. The database now joins one network per project, and no network holds two customers. Applied to every existing project, with nothing for you to do.
- Your application's
/healthroute is yours again. Pierrr's proxy intercepted it and answered a constantOK: you never saw your own response, and outside monitoring could believe you were up while your application had stopped answering.
What's new
- Connecting a managed resource to a container happens on the resource's node in the Topology: database, cache and object storage each have their own list of connected containers. Object storage was missing from the map entirely; it is now a node of its own, with unlinking.
- Each container shows the resources it is connected to, or says plainly that it is connected to none. A forgotten container was indistinguishable from a connected one until its first failed start.
- Multi-line secret values are kept as they are, certificates and private keys included. The input field previously replaced line breaks with spaces.
- A promo code can finally be entered when changing plan, checked on the spot with the discount shown before you confirm.
- The build context is a switch, "Monorepo: build from the repository root", and an existing container's build paths can be edited without recreating it.
Fixes
- An application publishing a TCP port used to fail every redeploy while an instance was running, since a port cannot be held by two containers. Those applications now switch to a straight replacement: a brief interruption, but a deploy that goes through.
- A passing API outage no longer signs you out. A failed session call was treated as an invalid session, which sent you back to the sign-in screen and lost whatever you were typing.
- A build interrupted by a platform update now says so, instead of a build-tool message that read like a fault in your Dockerfile.
- Fixed the mobile rendering of several screens whose content overflowed its card: linked repositories, the secrets list, security scans, card headers.