Let a secret be marked as never expiring
The expiry date is now optional: no date means the secret never expires, gets the status "no expiry" and never raises an alert or reminder. The Secrets form has a "Never expires" checkbox. Certificates checked against a host keep their live expiry and can't be set to never expire. Migration 0016 makes secrets.expiry_date nullable. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
75f0a3d881
commit
3daec601fd
11 files changed
+2069
-36
No files matched your search
@@ -56,7 +56,9 @@ All modules from the original plan are built:
|
||||
real TLS connection (daily, and on demand via "Check now"), reads the
|
||||
certificate's actual expiry, and keeps the date current — so a renewed cert
|
||||
is picked up automatically and an unreachable host is flagged instead of
|
||||
silently going stale
|
||||
silently going stale. A secret that doesn't expire (a break-glass password,
|
||||
a key with no end date) can be ticked "Never expires": it is listed with the
|
||||
status "no expiry" and never raises an alert or reminder
|
||||
- **IP Addresses (IPAM)** — inventory of IPs across vendors/locations,
|
||||
with "Sync from Tailscale", "Sync from Proxmox", and "Sync from phpIPAM"
|
||||
actions to pull in tailnet device IPs, VM/LXC IPs, and phpIPAM's own
|
||||
|
||||
Reference in new issue
Block a user