You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed an issue when trying to use the lease-"monitoring":
➜ example node app.js
vault-env: fetching 3 secrets from http://localhost:8210/
vault-env: loading TEST_DB_USERNAME, TEST_DB_PASSWORD from postgres/creds/myrole ✓
Example app listening at http://localhost:8080
My test secret is: secret_value2
/Users/username/checkouts/vault/apps/node/example/app.js:22
vaultEnv.on("DATABASE_URL", function (newDB, oldDB) {
^
TypeError: vaultEnv.on is not a function
at Server.<anonymous> (/Users/username/checkouts/vault/apps/node/example/app.js:22:12)
at Object.onceWrapper (node:events:513:28)
at Server.emit (node:events:394:28)
at emitListeningNT (node:net:1349:10)
at processTicksAndRejections (node:internal/process/task_queues:82:21)
Is there something "obvious" to fix - either in the example in the README or in code...?
Running NodeJS v16.6.1 here.
The text was updated successfully, but these errors were encountered:
Hi!
I noticed an issue when trying to use the lease-"monitoring":
Is there something "obvious" to fix - either in the example in the README or in code...?
Running NodeJS v16.6.1 here.
The text was updated successfully, but these errors were encountered: