Jira (PUP-11870) Modify CRLs and CAs "last updated" attribute after successful update instead of before

['Tony Vu (Jira)' via Puppet Bugs]

Title: Message Title

Tony Vu created an issue   Puppet / PUP-11870 Modify CRLs and CAs "last updated" attribute after successful update instead of before Issue Type: Improvement Assignee: Unassigned Created: 2023/06/06 11:48 AM Priority: Normal Reporter: Tony Vu Currently, we update the CA and CRL `last_updated` time before we try to actually acquire them from the server; if a problem occurs and the actual crl/ca does not successfully update, puppet will not try again until we hit the interval for updates. We initially wrote it this way to prevent possible churn in errors if we somehow errored out prior to updating/touching the files on disk. Now that the code has been proven to be more stable after release, we could change the update time to happen after successfully updating the CA/CRL. This way, if puppet does error out during a run and not update the CA/CRL successfully, it will try again on the subsequent puppet run, and not wait for the respective refresh intervals. Add Comment   This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.486493.1686077330000.5220.1686077340103%40Atlassian.JIRA.