Environment Strategy
Environment contract
Section titled “Environment contract”| Environment | Source | Primary purpose | Stability expectation |
|---|---|---|---|
| Dev | develop images | Integration of current work and fix validation | May change frequently |
| Test / Release | release/<version> images | Release hardening, regression, UAT, security validation | Stable except approved fixes |
| Prod | main or final release tag | Internal production and final verification | Controlled and recoverable |
- Environments are not personal sandboxes.
- Configuration differences are explicit and version-controlled.
- Production data is not copied into lower environments without approved masking and controls.
- A build must be traceable to commit SHA and image digest.
- Manual cluster changes are reconciled back to Git or reverted.
Current limitation
Section titled “Current limitation”Because Nexa does not yet provide ephemeral feature environments, a feature normally receives full integrated validation only after merge to develop. This is why PR quality and unit/component tests must be strong, and why develop is temporarily frozen during release hardening.