feat(sdk): add environment and secret management - #63
Merged
Conversation
justusschock
marked this pull request as ready for review
July 30, 2026 15:52
justusschock
requested review from
ethanwharris,
k223kim,
owbone and
tchaton
as code owners
July 30, 2026 15:52
k223kim
approved these changes
Jul 30, 2026
tejapulagam
approved these changes
Jul 30, 2026
ethanwharris
approved these changes
Jul 31, 2026
owbone
approved these changes
Jul 31, 2026
justusschock
enabled auto-merge (squash)
July 31, 2026 09:24
tchaton
approved these changes
Jul 31, 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
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
Why
Configuration management should follow backend-supported resource scopes without exposing secret values or conflating generic and typed secrets.
Commands
User secrets
Without
--value-stdin,setreads the secret from a hidden interactive prompt.Teamspace secrets
--teamspacedefaults to the current Teamspace. Without--value-stdin,setreads the secret from a hidden interactive prompt.Studio environment variables
--namefalls back to the current Studio or configured default.--teamspacedefaults to the current Teamspace.Deployment environment variables
--nameis required.--teamspacedefaults to the current Teamspace.User impact
Users can manage supported secrets and direct environment variables through SDK resources and the
lightningCLI. Studio and organization secret stores remain out of scope because those APIs do not exist.