This repository has been archived by the owner on Feb 16, 2025. It is now read-only.
Rolling changes out to staging takes long due to canary #727
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Problem
When making changes to website or api, staging changes to stage environment takes as long as it takes to roll out to prod due to the canary trigger. Could we reduce the time required for rolling out to staging by skipping canary and reserving it only for prod rollouts?
Steps to Reproduce
Steps to reproduce the behavior:
From a standing instance of emblem
web-new-build
triggerweb-canary-staging
triggers show up.Expected behavior
Since
web-canary-staging
functions exactly asweb-canary-prod
(only difference being the triggering action), there's no value in demonstrating canary trigger twice unless we intend to illustrate a difference based on environment. For demonstration purposes, I'd rather changes roll out to staging at 100% immediately.The text was updated successfully, but these errors were encountered: