Skip to content

Overview

Rollout ramps (#4653, #5180) on a resolved flag and environment: list, get, start on a targeting rule or on the default rule, then pause, resume, advance and abort. {project}, {flag} and {env} accept a key or a guid, resolved like FlagTargetingController; {ruleId} and {rampId} are guid-only, and a ramp on another flag is the same 404 as a missing one. Writes need at least Member, and a change reason when the environment requires one.

Every ramp response carries an ETag; pause, resume, advance and abort take an optional strong If-Match and answer 412 when the ramp has moved since (each step the job applies moves it). The check runs in the handler against the ramp it loads, and the ramp’s version token catches a change after that. Starting is refused (400 FEATURE_NOT_ENABLED) while the rollout-ramps gate is off; pause and abort stay open, also for a read-only organization, so a ramp can always be stopped.