Skip to content

fix(entrypoint): skip bw config server while logged in#38

Closed
TaprootFreak wants to merge 1 commit into
developfrom
fix/minter-guard-bw-config-skip
Closed

fix(entrypoint): skip bw config server while logged in#38
TaprootFreak wants to merge 1 commit into
developfrom
fix/minter-guard-bw-config-skip

Conversation

@TaprootFreak

Copy link
Copy Markdown
Contributor

Summary

  • The bw CLI refuses config server <url> while logged in: error Logout required before server config update
  • After PR feat(monitoringV2): minter-guard auto-deny watcher #33 deployed, both jdt-monitoring and jdm-monitoring on dfxdev crash-loop on entrypoint with that error (host's copied bw data is already logged in)
  • This PR replaces the setter call with a getter that just verifies the URL matches; if it doesn't match we exit fast with a clear error

Test plan

  • dfxdev containers start successfully after deploy (no crash-loop)
  • MinterGuard ENABLED log line appears once the vault items exist

bw refuses `config server <url>` while logged in. The host's copied bw
data is already logged into VAULT_SERVER_URL, so we replace the setter
call with a getter+compare. Containers were crash-looping on dfxdev with
"Logout required before server config update" until the fix.
@TaprootFreak

Copy link
Copy Markdown
Contributor Author

Superseded by #39, which removes the bw integration entirely in favor of the standard .env pattern.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant