Onboard new backport-pr re-usable github workflow (data-prepper)#6939
Merged
dlvenable merged 1 commit intoJun 30, 2026
Merged
Conversation
- Replace old backport workflow with reusable workflow from opensearch-build - Remove obsolete backport-related workflows Signed-off-by: Peter Zhu <zhujiaxi@amazon.com>
peterzhuamazon
requested review from
divbok,
san81,
sb2k16 and
srikanthjg
as code owners
peterzhuamazon
requested review from
KarstenSchnitter,
Zhangxunmt,
dinujoh,
dlvenable,
graytaylor0,
kkondaka,
oeyh and
srikanthpadakanti
as code owners
github-project-automation
Bot
moved this to Backlog
in OpenSearch Engineering Effectiveness
peterzhuamazon
moved this from Backlog
to In review
in OpenSearch Engineering Effectiveness
dlvenable
reviewed
Jun 29, 2026
| github_token: ${{ steps.github_app_token.outputs.token }} | ||
| branch_name: backport/backport-${{ github.event.number }} No newline at end of file | ||
| if: github.repository == 'opensearch-project/data-prepper' | ||
| uses: opensearch-project/opensearch-build/.github/workflows/backport-pr.yml@main |
Member
There was a problem hiding this comment.
Should this be a specific SHA? We've recently moved to using SHAs instead of friendly version numbers due to a learning from the recent JS attack?
Member
Author
There was a problem hiding this comment.
Not for re-usable workflow tho if you are concern you can feel free to change to SHA.
Which lose the benefit of receiving latest update.
These re-usable workflows are store in build repo, not in any random repo by other authors.
Member
There was a problem hiding this comment.
Reusable workflow can use branches. Since this is controlled by our org should be safe to accept.
dlvenable
approved these changes
Jun 30, 2026
github-project-automation
Bot
moved this from 👀 In Review
to ✅ Done
in Engineering Effectiveness Board
github-project-automation
Bot
moved this from In review
to Done
in OpenSearch Engineering Effectiveness
kkondaka
pushed a commit
to kkondaka/kk-data-prepper-f2
that referenced
this pull request
Jul 1, 2026
…nsearch-project#6939) - Replace old backport workflow with reusable workflow from opensearch-build - Remove obsolete backport-related workflows Signed-off-by: Peter Zhu <zhujiaxi@amazon.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
3 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
Onboard new backport-pr re-usable github workflow (data-prepper)
Issues Resolved
opensearch-project/opensearch-build#6270
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.