Repository navigation
docs(compadre): document native input object permissions - #57
Merged
Merged
Conversation
github-actions
Bot
added
vouch:trusted
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.
The live 20 MiB image canary exposed a missing IAM grant for the new native-input prefix. HeadBucket and central uploads succeeded, but native PutObject failed safely before run creation.
The existing CompadreAttachmentBucketAccess policy now additionally allows only GetObject/PutObject on compadre/attachments/native-inputs/v1/*, preserving existing grants and public-access blocks. Document the exact scope and require a real native upload in the deployment preflight. No credentials, deletion grants, or public access changed.
Model/harness: GPT-5 / Codex.