Edit Sandbox

When a sandbox is created from a Template, it receives its own copy of the sandbox definition from that template. This definition can be edited independently and the changes are reflected immediately in the running sandbox.

Edits can be made from the Web UI or using the cs sandbox edit command.

Caution

After editing, any workloads or resources that are no longer present in the new definition will be permanently removed. Renaming a workload or resource is not supported — it is treated as removing the old one and creating a new one.

Effects of Editing

Some changes cannot be applied to a running sandbox. For example, changing the path or repository of a checkout is not supported. Removing a checkout from the definition is allowed; the files already on the filesystem will be left untouched.

Changes to environment variables will trigger a restart of all running daemons, but not other running processes. Existing terminal sessions must be exited and restarted to pick up updated environment variables.

For container workloads, changes to env, entrypoint, args, image, and similar fields will cause the container to restart. During the restart, the image may also be re-pulled if the same image tag now points to a different image.

Resync from Template

A sandbox can be resynced from the Template it was created from. When doing so, all previous edits to the sandbox definition are discarded — workloads and resources not present in the Template will be permanently deleted.

See Sandbox Resync for details on how resyncing works.