fabriziosalmi/certmate v2.2.3

v2.2.3 — fix RFC2136 account editing (issue #85)

on GitHub

What's Fixed

RFC2136 DNS Account Editing (#85)

• HTTP 405 on edit resolved — Added PUT /api/dns/{provider}/accounts/{account_id} handler to both the REST API (DNSAccountDetail resource) and the web routes layer. Attempting to save changes to any DNS provider account (RFC2136 in particular) previously returned HTTP 405 Method Not Allowed.
• Credential preservation on edit — The update handler merges incoming data with the existing account config, skipping any field whose value is the masked placeholder '********'. This prevents accidental corruption of secrets that are intentionally hidden in the UI.
• RFC2136 configured status now correct — Extended the credential key list used to determine whether an account is configured to include RFC2136-specific fields (nameserver, tsig_key, tsig_secret). Previously these accounts always showed as not configured.

Files Changed

• modules/api/resources.py — new put() method on DNSAccountDetail
• modules/web/settings_routes.py — PUT support added to api_dns_account_detail
• modules/core/dns_providers.py — RFC2136 keys added to configured check

Testing

All 153 unit tests + 12 UI tests pass.