From 255d98c4d76359d59fcd440f1dde7893e8c86810 Mon Sep 17 00:00:00 2001 From: felixfontein Date: Tue, 30 Apr 2024 08:28:36 +0000 Subject: [PATCH] deploy: 6d4fc589aee55b81bb0717eed6dd12401785f20c --- pr/739/acme_certificate_module.html | 1 + pr/739/searchindex.js | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/pr/739/acme_certificate_module.html b/pr/739/acme_certificate_module.html index 8754f88e..bc06feab 100644 --- a/pr/739/acme_certificate_module.html +++ b/pr/739/acme_certificate_module.html @@ -426,6 +426,7 @@ see never never sends the certificate ID of the certificate to renew. always will always send it.

when_ari_supported only sends the certificate ID if the ARI endpoint is found in the ACME directory.

Generally you should use when_ari_supported if you know that the ACME service supports a compatible draft (or final version, once it is out) of the ARI extension. always should never be necessary. If you are not sure, or if you receive strange errors on invalid replaces values in order objects, use never, which also happens to be the default.

+

ACME servers might refuse to create new orders with replaces for certificates that already have an existing order. This can happen if this module is used to create an order, and then the playbook/role fails in case the challenges cannot be set up. If the playbook/role does not record the order data to continue with the existing order, but tries to create a new one on the next run, creating the new order might fail. For this reason, this option should only be set to a value different from never if the role/playbook using it keeps track of order data accross restarts.

Choices: