Staged changes
Changes to a service's settings, its variables and its environment wait until you apply them, so they land together as one.
All pages
Each environment has one list of staged changes. A change you stage joins that list and changes nothing yet. When you apply the list, every change in it applies together.
| Change | Waits until you apply it | Applying it deploys |
|---|---|---|
| A variable | yes | yes |
| The branch or a build setting | yes | yes |
| Size, replicas and routing | yes | no |
| Database readers | yes | no |
| A bucket connection | yes | yes |
| Access | yes | no |
| Deleting a service | yes | no |
Applying a change to a variable, a bucket connection, the branch or a build setting starts a deploy of each website it changes. The rest take effect as soon as they apply. A database's nightly backups switch applies at once. Adding a service or a database also acts at once.
Press ⌘K and choose Review changes. Press ⌘↵, or choose Apply changes. To drop some, select them and choose Discard selected. Apply changes walks through it.
With the CLI, show, apply or discard one environment's list:
ghaym cloud changes show --project shop
ghaym cloud changes apply --project shop --env staging
ghaym cloud changes discard --project shopA command that stages a change, such as services scale, access set or vars set, takes --apply to apply it in the same run.
A new environment copies production's settings and access once, when it is created. After that each environment keeps its own, and a change staged in one never reaches another.