Allow renewal of staging certs and honor --staging/--test flags. #6464
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It is nice to be able to reliably test cert renewals, such as when a cert is requested in an application using a different method than it is being renewed as, such as when a cert is obtained through standalone mode, and then expected to renew through nginx/apache.
Testing renewals by running the cron command swaps out staging cert requests for production ones.
Operators may want to test the renewal command and append --force --test of the form:
acme.sh --cron --home="/home/letsencrypt" --force --test
make the --test flag (or --staging) flag on this command honor the request to continue to use staging servers for renewals when requested.
related to #6368