feat: support uploading artifacts to AWS S3 in action.yml #22
Conversation
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
Signed-off-by: quic-rnamburi <rnamburi@qti.qualcomm.com>
Signed-off-by: quic-rnamburi <rnamburi@qti.qualcomm.com>
quic-rnamburi
commented
Dec 26, 2025
Contributor
Author
quic-rnamburi
left a comment
quic-rnamburi
left a comment
There was a problem hiding this comment.
Adding missing commit message
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.
This PR introduces an S3 upload step and aligns the CI workflow:
Adds an optional step in the CI workflow to upload ARMOR outputs to AWS S3 for persistent storage and traceability.
Artifacts are organized using a structured, time-based hierarchy to support dashboards and lifecycle policies.
This change is backward compatible and does not affect existing workflows unless enabled.