From 9005ea4658555190ad9577da5ff83406256966b7 Mon Sep 17 00:00:00 2001 From: bertrandp Date: Tue, 1 Oct 2024 17:12:31 +0200 Subject: [PATCH] Update README.md, clarify use of BW_RELOGIN_INTERVAL BW_RELOGIN_INTERVAL default value is `3600` seconds. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ab35946..cecfdfd 100644 --- a/README.md +++ b/README.md @@ -204,4 +204,4 @@ Please note that the rendering engine for this template is jinja2, with an addit The operator uses the bitwarden cli in the background and does not communicate to the api directly. The cli mirrors the credential store locally but doesn't sync it on every get request. Instead it will sync each secret every 15 minutes (900 seconds). You can adjust the interval by setting `BW_SYNC_INTERVAL` in the values. If your secrets update very very frequently, you can force the operator to do a sync before each get by setting `BW_FORCE_SYNC="true"`. You might run into rate limits if you do this too frequent. -Additionally the bitwarden cli session may expire at some time. In order to create a new session, the login command is triggered from time to time. In what interval exactly can be configured with the env `BW_RELOGIN_INTERVAL` which defaults to 3600s. +Additionally the bitwarden cli session may expire at some time. In order to create a new session, the login command is triggered from time to time. In what interval exactly can be configured with the env `BW_RELOGIN_INTERVAL` which defaults to `3600` seconds.