Codeac GitHub Integration: State Persistence Across Ephemeral Environment Recreation

Integration Challenge: State Persistence in Codeac GitHub Ephemeral Environments

The Codeac platform uses GitHub repositories to provision ephemeral development environments defined by codeac.yaml. When an environment is destroyed and recreated from a specific branch, the system restores runtime and dependencies but does not automatically address stateful data such as database schemas or persistent volumes that lie outside source code.

The interoperability requirement is that environment recreation must preserve external state without manual intervention, relying solely on the configuration file and Git history.

• Goal: Ensure that stateful migrations are handled consistently when environments are rebuilt from different branches.
• Constraint: The repeatability of the environment depends on accurate container definitions and external scripts in codeac.yaml.
• Uncertainty: The platform’s handling of complex stateful migrations during environment recreation is undocumented.

Specific Questions

1. How does codeac manage persistence of stateful data (e.g., database schemas, volumes) when an environment is destroyed and recreated from a different git branch?
2. Is there a built‑in mechanism to synchronize or migrate external state across environment lifecycles?
3. What configuration patterns or hooks does codeac provide to address state drift in repeatable development workflows?