Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Add Functionality to allow CodePipeline Event to Manage Output Artifacts #5447

Open
2 tasks done
mw-root opened this issue Oct 24, 2024 · 1 comment · May be fixed by #5448
Open
2 tasks done

Feature request: Add Functionality to allow CodePipeline Event to Manage Output Artifacts #5447

mw-root opened this issue Oct 24, 2024 · 1 comment · May be fixed by #5448
Assignees
Labels
event_sources Event Source Data Class utility feature-request feature request

Comments

@mw-root
Copy link
Contributor

mw-root commented Oct 24, 2024

Use case

CodePipelineJobEvent allows us to retrieve input artifacts, but does not have functionality to manage and upload output artifacts.

Since the CodePipeline artifact buckets can be very strict, and the event provides credentials, it makes sense to add methods to interact with, and upload, output artifacts.

Solution/User Experience

I believe this should be a new method like event.put_artifact and whatever methods are required to support this.

The bucket, credentials, and encryption configuration should all be auto-magic.

Alternative solutions

No response

Acknowledgment

@leandrodamascena
Copy link
Contributor

Assing to @anafalcao.

@leandrodamascena leandrodamascena added event_sources Event Source Data Class utility and removed triage Pending triage from maintainers labels Nov 7, 2024
@leandrodamascena leandrodamascena moved this from Triage to Working on it in Powertools for AWS Lambda (Python) Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
event_sources Event Source Data Class utility feature-request feature request
Projects
Status: Working on it
Development

Successfully merging a pull request may close this issue.

3 participants