feat(dedicated-server): adopt plannedChange apiv6 route behind feature flag#23011
Merged
qpavy merged 2 commits intoJul 16, 2026
Merged
Conversation
qpavy
previously approved these changes
Jul 9, 2026
mhelhali-soufien
previously approved these changes
Jul 9, 2026
…e flag Gate the new /dedicated/server/:serviceName/plannedChange apiv6 route (DC360, INTERNAL rollout) behind the dedicated-server:plannedChange feature flag, falling back to the legacy /plannedIntervention route when the flag is off. When the flag is on, upgradeTask reads task.changeUuid and calls /plannedChange/:changeUuid; otherwise it reads task.plannedInterventionId and calls /plannedIntervention/:interventionId. PlannedChange exposes the same wantedStartDate the UpgradeTask.scheduledTimeSlot getter reads, so the model is unchanged. Applied identically to the server dashboard and the cluster-node dashboard resolvers; flag id added to both features batches. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ref: #PUBM-54260 Signed-off-by: soufien mhelhali <soufien.mhelhali.ext@ovhcloud.com>
mhelhali-soufien
force-pushed
the
feat/dedicated-planned-change-route
branch
from
July 15, 2026 04:45
17d877a to
8856b46
Compare
qpavy
approved these changes
Jul 15, 2026
EdDonald
approved these changes
Jul 15, 2026
qpavy
merged commit Jul 16, 2026
d1ad4a9
into
release/bm-dc360-plannedchanges
11 of 13 checks passed
acavalloni
pushed a commit
that referenced
this pull request
Jul 16, 2026
…e flag (#23011) switch api route from plannedIntervention to plannedChange ref: #PUBM-54260 Signed-off-by: soufien mhelhali <soufien.mhelhali.ext@ovhcloud.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: charles ilief <charles.ilieff@ovhcloud.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Gate the new /dedicated/server/:serviceName/plannedChange apiv6 route (DC360, INTERNAL rollout) behind the dedicated-server:plannedChange feature flag, falling back to the legacy /plannedIntervention route when the flag is off.
When the flag is on, upgradeTask reads task.changeUuid and calls /plannedChange/:changeUuid; otherwise it reads task.plannedInterventionId and calls /plannedIntervention/:interventionId. PlannedChange exposes the same wantedStartDate the UpgradeTask.scheduledTimeSlot getter reads, so the model is unchanged.
Applied identically to the server dashboard and the cluster-node dashboard resolvers; flag id added to both features batches.
Ticket Reference: #PUBM-54260