fix: harden e2e-test workflow to install requirements.txt from trusted default branch instead#105
Merged
Merged
Conversation
…d default branch instead Signed-off-by: Frank Kong <frkong@redhat.com>
Contributor
Container Image PublishedMulti-platform container images are now available.
Expires: July 14, 2026 Pull Commands# Multi-platform (auto-selects correct architecture)
podman pull quay.io/rhdh-community/dynamic-plugins-factory:pr-105
# Or with specific commit SHA
podman pull quay.io/rhdh-community/dynamic-plugins-factory:pr-105-4213b50Traceability
|
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
1 participant
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
Updates the e2e-test workflow to no longer install requirements.txt from PR branch for better security. As a tradeoff, this means PRs that update requirements.txt will need to have that merged first. Also restricts the branches where the cascaded workflows can be triggered from.
Which issue(s) does this PR fix
PR acceptance criteria
Please make sure that the following steps are complete:
How to test changes / Special notes to the reviewer