Factory environments and promotion

An environment chain connects separate factories in one workspace, such as Dev → Staging → Production. Promotion copies a factory definition to the next stage. It does not deploy your application or provision infrastructure.

Create a chain

Open Factory settings → Environments. Name the chain, choose a factory for each stage, and give each stage a label. A chain has two to five stages; a factory belongs to at most one chain.

Use Add stage, Move earlier, Move later and Remove stage to arrange it, then Save chain. You need write access to every factory in the chain to edit its configuration.

For destination stages, choose whether promotion requires another person’s approval. The first stage has no incoming promotion.

Compare and promote

Each adjacent pair reports whether its definitions match. Select Preview promotion to read the changes and Test factory result against the destination’s context. Resolve missing configuration and inspect other pending changes in the destination before proceeding.

Promotion goes one stage at a time. A Dev factory cannot skip Staging to reach Production. A simulation that is not ready requires a written acknowledgement if you proceed.

If the destination requires approval, Request promotion creates a change request there. A second person reviews and publishes it through Changes. Otherwise, Promote definition creates a version in the destination.

No way round the approval

In a factory that is a stage requiring another person's approval, the other doors that change its definition go through the same review. Saving the factory's policy (or copying another factory's policy onto it), rolling back to an earlier version, applying an optimizer recommendation, installing a blueprint, updating from the blueprint it came from, and changing a station's permission switches each open a change request, already sent for review, instead of writing directly. That holds whether the change comes from a settings panel, the optimizer or the concierge. A second person approves and publishes it in Changes, with the diff and Test factory result. In a factory with no such stage, these changes apply directly, as before.

What stays in the destination

Cards, run history, people and credentials stay with their factory. Worker references are matched or installed as supported by the definition restore process. Runtimes and other connections must exist in the destination; promotion does not invent credentials.

This separation lets you try a definition with test work before promoting it into a factory handling different cards.

History and removal

Expand Promotion history to see published versions and promotions waiting for review. The list shows only stages you may read.

Remove environment chain asks for confirmation and removes the chain, not its factories, cards or versions. Use Versions when the goal is to undo a published definition change.