chore(e2e): log resolved suite inputs to diagnose login mismatch (BUNYIP-167) #187
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/BUNYIP-167-log-resolved-config"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Temporary diagnostic to end the login-mismatch guessing.
preflight.setup.tsnow logslogResolvedConfig()(lib/env.ts) on every run:Non-secret values (URLs, the test email, tenant, OIDC client/redirect) in plaintext; password + TOTP only as length + sha256 prefix.
How to use
The pull_request CI run on this branch prints the
[config]block against staging. Then on c-01:email/baseURLto what you log into manually;'<the real password>' | hash sha256 | str substring 0..12and compare to thepasswordfingerprint.If the password fingerprint differs -> the secret is not the account password. If
email/baseURLare off -> wrong account / wrong deployment.Note
Temporary (BUNYIP-167); revert once the mismatch is found.
tsc --noEmitclean; output verified locally.#BUNYIP-167