Guard app access replacements with an expected revision - #6
Closed
nathan-thillairajah wants to merge 1 commit into
Closed
nathan-thillairajah wants to merge 1 commit into
nathan-thillairajah wants to merge 1 commit into
Conversation
nathan-thillairajah
marked this pull request as ready for review
September 24, 2026 17:50
jsibbison-square
approved these changes
Sep 24, 2026
Contributor
Author
|
🤖 Closing this PR because it guards the existing account-ID viewer command, while the pilot CLI should grant access to a non-personal Builderlab workspace. The existing |
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
2 participants
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.
An owner or agent can read an app's viewer list, edit it, and unknowingly overwrite a change made in the meantime.
bl apps access set --expected-revisionlets them require that the policy still matches the version they reviewed.The CLI refuses the update if the server doesn't support that guarantee. A conflict requires reading and reviewing the policy again; it never retries with an unguarded replacement. Existing commands without the flag keep their current behavior.