2 years ago
Staged changes allow you to make a bunch of changes to your environment, review the changes, and then deploy them all at once. This removes the annoying toast that keeps letting you know a redeploy will happen.
It is available to anyone by enabling the feature flag
As part of this feature
There is a new settings page
All changes to a service are scoped to the current environment
You can see all the changes that were committed in the activity feed
You can import services from other environments
Here are some screenshots
Staged changes also lays the groundwork for many other environment-based changes that we will soon be making. Please let us know if you have any feedback or suggestions!
0 Threads mention this feature
6 Replies
2 years ago
😅
Status changed to Completed jr • about 2 years ago
2 years ago
It seems that im not able to change the deployment region when this feature-flag is activated. Therefore I had to disable the feature and then change the region afterwards
2 years ago
It seems that im not able to change the deployment region when this feature-flag is activated. Therefore I had to disable the feature and then change the region afterwards
What was the error you were seeing?
2 years ago
This is a fantastic feature, we're using it flat out and asked all team members to start using it to avoid premature application when making bulk changes.
Super happy!
2 years ago
It seems that im not able to change the deployment region when this feature-flag is activated. Therefore I had to disable the feature and then change the region afterwards
Are you still seeing this issue? It should be all fixed now
2 years ago
Is this affecting PR Environments from Github? Before activing this feature all was working just fine but now it does not clone the template env and just creates an empty env for the PR, with no deployment
If the setting is off then all works as expteced, otherwise the env is created empty.
2 years ago
Is this affecting PR Environments from Github? Before activing this feature all was working just fine but now it does not clone the template env and just creates an empty env for the PR, with no deployment
If the setting is off then all works as expteced, otherwise the env is created empty.
This should be all fixed now!
Status changed to In Progress chandrika • 11 months ago
Status changed to Completed chandrika • 11 months ago