-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Yong Sheng Tan
committed
Jul 21, 2023
1 parent
822f46e
commit 21748a7
Showing
1 changed file
with
17 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,18 @@ | ||
# Symphony WDK Loader | ||
This loader allows WDK to be run in API mode while deploying SWADL files once from a designated location at startup. | ||
This allows secrets to be used in production when API-based deployments are not preferred. | ||
|
||
## Configuration | ||
1. Enable WDK API mode by setting `wdk.workflows.path` to an empty string and enabling the `monitoring-token` and `management-token` | ||
2. Set `wdk.loader.path` to the actual path of where the SWADL files should be loaded from | ||
````yaml | ||
wdk: | ||
workflows.path: "" | ||
loader.path: ./workflows | ||
encrypt.passphrase: mysecretpassphrase | ||
properties: | ||
monitoring-token: mysecretpassphrase | ||
management-token: mysecretpassphrase | ||
```` | ||
3. Add secrets via environment variables prefixed with `WDK_` in the runtime location | ||
- e.g. adding a `WDK_secretToken` environment variable with a `abc` value will create a WDK secret at startup named `secretToken` with a value of `abc` |