Adding conditional Log Detective variables to configuration templates#687
Conversation
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 34s |
7d28372 to
d20dab9
Compare
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 34s |
d20dab9 to
ce3f8b7
Compare
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 34s |
ce3f8b7 to
0cc5678
Compare
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 34s |
0cc5678 to
8be2cce
Compare
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 33s |
8be2cce to
7c32a47
Compare
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 32s |
7c32a47 to
ba8fe10
Compare
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 32s |
ba8fe10 to
e054dbd
Compare
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 41s |
e054dbd to
8822b79
Compare
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 53s |
8822b79 to
f0dabff
Compare
Signed-off-by: Jiri Podivin <jpodivin@redhat.com>
f0dabff to
afb5b4f
Compare
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 37s |
|
Build succeeded (gate pipeline). ✔️ pre-commit SUCCESS in 1m 33s |
465f302
into
packit:main
I've used the same approach as utilized by other secrets. Both URL and token will be stored in bitwarden and rendered into template only if the URL is present. Log Detective interface server will always require authentication. Therefore, any configuration when URL is set, but the token is missing, is not viable.
Since removing the fields from configuration can be accomplished by just renaming, or removing, the variables in bitwarden, the fields were added to both prod and stage configuration templates.
RELEASE NOTES BEGIN
Log Detective URL and token are now conditional part of the service configuration.
RELEASE NOTES END