Explicitly mount tokens #1421
Merged
Explicitly mount tokens #1421
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
…enabling them at the service account level
atoulme
force-pushed
the
explicitly_mount_tokens
branch
3 times, most recently
from
d8043a4 to
1848bad
Compare
atoulme
force-pushed
the
explicitly_mount_tokens
branch
from
1848bad to
d6a1d42
Compare
dmitryax
approved these changes
Aug 28, 2024
pjanotti
approved these changes
Aug 28, 2024
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.
Description:
Explicitly mount service tokens in specific tokens rather than enabling them at the service account level