This repository was archived by the owner on Apr 28, 2025. It is now read-only.
Rename deb to apt-multi-iam-s3 from apt-transport-s3 #2
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
Xenial includes an S3 apt transport helper that only supports using one IAM credential for all your S3-backed apt repositories. This reduces the granularity of permissions you can apply to machines, and isn't acceptable in our security model. I'm renaming the deb so that I can use it on Xenial machines without having a namespace collision with the naive upstream transport tool.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Xenial includes an S3 apt transport helper that only supports using one IAM credential for all your S3-backed apt repositories. This reduces the granularity of permissions you can apply to machines, and isn't acceptable in our security model.
I'm renaming the deb so that I can use it on Xenial machines without having a namespace collision with the naive upstream transport tool.
If you've got a better idea for coping with this, I'm open to suggestions.