aws-encryption-provider
aws-encryption-provider copied to clipboard
Release an official container
What would you like to be added:
I'd like to use a pre-built container of this provider. I know this was requested before, twice... But maybe things have changed since? I'm also happy to contribute this.
Why is this needed:
Lower barrier for usage, if you can just use an existing one.
Happy to PR a GH workflow which would publish a latest on every push to master into the GH registry on this repo?
Also happy to PR whatever is needed to publish tagged releases, if there's someone willing to walk through the preferred workflow/requirements.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale
I can see a relevant PR #72 got merged - is there anything I can do to help move this forward?
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-contributor-experience at kubernetes/community. /close
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-contributor-experience at kubernetes/community. /close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/reopen /remove-lifecycle rotten
For anyone willing to help out, we'd appreciate community contribution here. The work involved requires following the guide in kubernetes/k8s.io and starts out by making a PR to that repo similar to kubernetes/k8s.io#2274 (owner references would be the folks listed in this repos OWNERS_ALIASES)
@dominykas are you working on this issue? If not I can try to give this a go.
I'm not working on this, no - I missed the response, but I'm also not able to take this right now, so please do!
/assign
/assign
I can help on this @micahhausler @dims
go for it. thanks @xdu31
Hi, any progress on this issue? Thanks
/assign
I see this has been completed and merged, but nowhere in the docs can I find the location of the official container... can someone point me to it? Happy to open a PR to update the README, if I can only find the location...