fix: honour pgpass file in Change Server Password dialog (#10449) - #10451
MaybeSomeone-arc18 wants to merge 2 commits into
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: pgadmin-org/pgadmin4/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. WalkthroughThe change-password dialog now passes ChangesChange-password dialog
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix · Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to The pgpass-aware password dialog is mergeable after normal checks; no actionable risk remains identified. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Fixes #10449.
The Change Server Password dialog always required the current password, even when the server connects via a pgpass file. ChangePasswordContent never accepted the isPgpassFileUsed prop that showChangeServerPassword() passes, and built its schema with the value hardcoded to false.
isPgpassFileUsed(defaultfalse) and pass it toChangePasswordSchemapropTypesgettext()regression/javascript/Dialogs/ChangePasswordContent.spec.jscovering both the pgpass and the ordinary password caseThe new tests fail on master and pass with this change. I haven't touched the
hasCsrfTokenpoint mentioned in the issue, to keep this focused.Summary by CodeRabbit