Environment Approvals
Manage the permission an environment file needs to receive secrets you hold. An approval ties the file and its environment name to a secret's stable ID. Another path, a changed environment name, or a replaced secret needs a new approval. Edits at the same path and name keep the permission, so review the file before you run it.
Add an Approval
lnk env approval add records your permission before a non-interactive run.
The file must name the secret under [secrets], and you must already hold
it. The approval rules explain how Local Link identifies a
file and how field overrides count.
lnk env approval add NPM_TOKEN --spec env.tomlList Approvals
lnk env approval list lists your saved approvals. Add --spec env.toml to
limit the list to one file, or --json when another program needs the
records. Neither view shows secret values.
lnk env approval list --spec env.tomlShow an Approval
lnk env approval show checks whether you approved the named secret for the
environment file. An approval is permission for a later run. It does not
show that the environment has run or used the secret.
lnk env approval show NPM_TOKEN --spec env.tomlRemove an Approval
lnk env approval remove revokes the saved permission. The next run must ask
again before it gets that secret. A non-interactive run without an approval
refuses the secret.
lnk env approval remove NPM_TOKEN --spec env.toml