Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: set acme_account_url even if some DNS records are not set #423

Merged
merged 1 commit into from
Oct 15, 2024

Conversation

link2xt
Copy link
Contributor

@link2xt link2xt commented Oct 15, 2024

perform_initial_checks may exit early
and not add acme_account_url if required DNS
records are not found.
In this case other cmdeploy run fails
with KeyError.

To avoid this, acme_account_url should always be set.

Unlike DNS checks, running acmetool
may not fail due to network errors,
so it is more reliable and should be checked first.

perform_initial_checks may exit early
and not add `acme_account_url` if required DNS
records are not found.
In this case other `cmdeploy run` fails
with KeyError.

To avoid this, `acme_account_url` should always be set.

Unlike DNS checks, running acmetool
may not fail due to network errors,
so it is more reliable and should be checked first.
Copy link
Contributor

@missytake missytake left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This basically means acme_account_url is set to "" on first deployment, and dkim_entry to None, which is fine because it isn't actually useful during first cmdeploy run, only for cmdeploy dns which calls the same function?

@link2xt link2xt merged commit a2f2e04 into main Oct 15, 2024
6 checks passed
@link2xt link2xt deleted the link2xt/acmetool-first branch October 15, 2024 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants