decentraland / worlds-content-server / 29527244710

91%

main: 91%

Pull #509

github

feat: add ?singleWorldScene deploy option that preserves the world place

A default (non-multi-scene) world deploy today deletes every scene first via the
world-wide undeploy, which publishes a WorldUndeploymentEvent. Downstream (the
places service) reacts by disabling ALL of the world's places, so the redeploy
mints a brand-new placeId — and anything bound to the old placeId (notably the
world's env variables in world-storage-service) is orphaned.

Add a `?singleWorldScene=true` query flag to POST /entities. When set on a world
deploy, after the new scene lands the handler removes every OTHER scene in the
world via the per-scene undeploy path (undeployOtherWorldScenes ->
undeployWorldScenes), which publishes a WorldScenesUndeploymentEvent — never a
WorldUndeploymentEvent. The world is never emptied, so the deployed scene's place
stays enabled and keeps its placeId; env vars bound to it survive the redeploy.

Because it removes scenes beyond the deployed parcels, the flag requires world
ownership or world-wide deployment permission (checked up front, fail fast),
mirroring the world-wide undeploy endpoint. The cleanup itself is best-effort:
the deploy is already committed and the place is preserved regardless, so a
cleanup failure only leaves stale scenes, never a 5xx.

Adds unit coverage for undeployOtherWorldScenes and the handler's authorize/cleanup branches.

1463 of 1713 branches covered (85.41%)

Branch coverage included in aggregate %.

20 of 21 new or added lines in 2 files covered. (95.24%)

3145 of 3356 relevant lines covered (93.71%)

67.8 hits per line