Skip to content

Commit a57b666

Browse files
committed
Update secret usage docs
Signed-off-by: nscuro <nscuro@protonmail.com>
1 parent 50361fc commit a57b666

2 files changed

Lines changed: 4 additions & 10 deletions

File tree

3.31 KB
Loading

docs/usage/secret-management/overview.md

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
!!! note
2-
This feature is still being developed. While you can already *manage* secrets,
3-
you cannot *use* them anywhere yet.
4-
51
Dependency-Track integrates with various 3rd party systems,
62
most of which require some sort of credential to authenticate
73
with them: API keys, passwords, or access tokens. Such secrets
@@ -67,11 +63,9 @@ Deleted secrets cannot be restored. Proceed with caution.
6763

6864
## Using Secrets
6965

70-
!!! warning
71-
This is not yet implemented.
66+
Secrets can be used in configuration fields marked with :key:.
7267

73-
It will be possible to securely reference secrets in configuration using expressions, e.g.:
68+
![Secret input field in a configuration form](./images/use-secret.png)
7469

75-
```jinja linenums="1"
76-
{{ secret('OSSINDEX_API_KEY') }}
77-
```
70+
These fields offer dropdown and search capabilities,
71+
making it easy to discover available secrets.

0 commit comments

Comments
 (0)