[Plugin/SDK] Add DeployTargetStatus and extend ExecuteStageResponse#6861
Merged
Warashi merged 2 commits intoMay 26, 2026
Merged
Conversation
Signed-off-by: Mohammed Firdous <124298708+mohammedfirdouss@users.noreply.github.com>
Warashi
approved these changes
May 26, 2026
Contributor
|
Thank you for contributing to PipeCD! The changes in this pull request will be part of the upcoming release! |
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
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.
What this PR does:
Adds a
DeployTargetStatustype and extendsExecuteStageResponsewith aDeployTargetStatuses []DeployTargetStatusfield inpkg/plugin/sdk/deployment.go.Why we need it:
Plugins that deploy to multiple clusters in parallel (e.g.
kubernetes_multicluster) need to report per-target outcomes alongside the overall stage status. When a stage deploys to N clusters and one fails, operators currently see only "stage failed" with no indication of which cluster. The new field surfaces the per-cluster result.This change to
pkg/plugin/sdk/will be picked up by the sync bot and propagated topipe-cd/piped-plugin-sdk-go, after which a new SDK release tag can be cut and PR #6812 can drop itssdk_local/shim.Which issue(s) this PR fixes:
Related to #6446. Companion plugin PR: #6812.
Does this PR introduce a user-facing change?:
Statusfield is unchanged.