feat(access-list): add optional note field to access list clients#5540
feat(access-list): add optional note field to access list clients#5540TheMazeIsAmazing wants to merge 13 commits into
Conversation
… widen modal - Add optional note property to access list clients in backend model and schema - Extend OpenAPI schemas (common + access-list endpoints) to support note - Created necessary migration to add the note row to access_list_client table - Persist note in access_list_client inserts/updates - Render note in nginx config as inline comment for access rules (when present) - Extend frontend AccessListClient model with optional note - Add note input field to Access List modal (Rules tab) - Only include note in payload when non-empty - Add i18n placeholder for note field - Increase Access List modal width for improved usability
update working repo
Merge into local branch
Code ReviewThanks for the PR and for keeping it up-to-date with Blocking IssueGlobal CSS override in .modal-dialog {
max-width: 700px !important;
}This widens every modal in the application, not just the Access List modal. Bootstrap's default is 500px. This needs to be scoped to only the Access List modal — e.g. via a dedicated CSS class applied through Minor Issues
What's Good
Fix the global CSS scope and this is good to go. |
|
CI Error: |
Why
This PR introduces an optional “note” field for access list client rules to improve clarity when managing multiple IP entries. It allows users to annotate each rule (e.g. “Home” or “Office”) without affecting current behaviour.
(See feat-req: #5277)
Front-end change:

Note added to the generated Nginx files (e.g.

/data/nginx/proxy_host/X.conf):Type of Change
AI Usage
Misc.
I'm sorry, this is a new version of #5333. Wanted to make sure it was up-to-date with current
developbranch and resolve merge conflicts. Guess I did it wrong and accidentally removed my PR 🥲.