refactor: remove elevation package and simplify secret access#324
Merged
Conversation
Co-authored-by: frodesundby <frode.sundby@nav.no>
jhrv
force-pushed
the
cleanup-elevation
branch
from
bc394f4 to
722a6a5
Compare
frodesundby
approved these changes
Jan 30, 2026
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.
Summary
Removes the elevation package and API, replacing it with the simpler
viewSecretValuesmutation.Changes
internal/elevation/packagecreateElevationmutationelevationsquery on UserviewerCanElevatefield on Teamvaluesresolver on SecretElevationCreatedActivityLogEntry) moved to activitylog packageBreaking Changes
Clients must use
viewSecretValuesmutation instead of:createElevation+secret.valuesviewerCanElevateConsole and CLI are already migrated.