Skip to content

Commit

Permalink
docs: extend docs by specific secret templates (#40)
Browse files Browse the repository at this point in the history
  • Loading branch information
MarcScheib committed Feb 21, 2024
1 parent ad826ec commit 9ddd34e
Showing 1 changed file with 22 additions and 1 deletion.
23 changes: 22 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,28 @@ QUARKUS_OIDC_IDENTITY_SERVICE_SECRET=$clients["identity-service"].secret
The `client_id` variable can be used within the filename of secret templates as well.
In comparison to the usage in templates, the `$` must be omitted.
Each client is exported to a separate file then. Otherwise, multiple clients will
overwrite each other. For example, as possible name could be `client_id-oidc.env`.
overwrite each other. For example, a possible name could be `client_id-oidc.env`.
If there are two clients, `client-a` and `client-b`, the following files are created:

- `client-a-oidc.env`
- `client-b-oidc.env`

It is possible to provide multiple secret templates at once. The configurator will
generate a file for each client and secret template combination. If a secret template
has the same name as an expanded file would have, this file has precedence. For example,
if the following secrets templates are provided for the clients `client-a` and `client-b`:

- `client-a-oidc.env`
- `client_id-oidc.env`
- `client_id-oidc.json`

The following files are created:

- `client-a-oidc.env` (based on `client-a-oidc.env`)
- `client-b-oidc.env` (based on `client_id-oidc.env`)
- `client-a-oidc.json` (based on `client_id-oidc.json`)
- `client-b-oidc.json` (based on `client_id-oidc.json`)


### Sub-Command `rotate-secrets`

Expand Down

0 comments on commit 9ddd34e

Please sign in to comment.