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

feat: DNS propagation wait worker #305

Merged
4 commits merged into from Mar 9, 2023
Merged

feat: DNS propagation wait worker #305

4 commits merged into from Mar 9, 2023

Conversation

ghost
Copy link

@ghost ghost commented Mar 8, 2023

  • Alters Let's encrypt class to handle DNS error
  • Alters DNS worker, enhances error logging
  • Adds request to DNS worker to inject appropriate records
  • Implements DNS propagation waiter worker
  • Simplifies Cert order worker, simplifies response (no need for additional data)

Closes #169

@ghost ghost added this to the Milestone 0.5 milestone Mar 8, 2023
@ghost ghost requested review from humphd, SerpentBytes and Genne23v March 8, 2023 17:40
@ghost ghost self-assigned this Mar 8, 2023
app/lib/dns.server.ts Show resolved Hide resolved
app/utils.ts Show resolved Hide resolved
@ghost ghost requested a review from Genne23v March 9, 2023 00:08
@ghost ghost requested a review from SerpentBytes March 9, 2023 16:52
app/lib/dns.server.ts Outdated Show resolved Hide resolved
@SerpentBytes SerpentBytes self-requested a review March 9, 2023 17:26
SerpentBytes
SerpentBytes previously approved these changes Mar 9, 2023
*/
await addDnsRequest({
username,
Copy link
Contributor

Choose a reason for hiding this comment

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

@dadolhay I'm going to break down this function into 1. Add a record to DB with pending status 2. Route53 update and update DB status once Route53 work is complete. Let me know if you see any concern with this.

Copy link
Author

Choose a reason for hiding this comment

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

@Genne23v
It's still going to be a flow, right? so I create a job to handle this, and the job flow adds the db entry, handles the route53 api, then updates the status to complete

Am I understanding you correctly?

Copy link
Contributor

Choose a reason for hiding this comment

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

Initial DB record creation won't be a part of flow as it completes the work immediately. Then the rest of jobs will be run as flow.

Copy link
Contributor

@humphd humphd left a comment

Choose a reason for hiding this comment

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

Looks good. A few small things and questions.

app/lib/dns.server.ts Outdated Show resolved Hide resolved
app/queues/certificate/dns-waiter-worker.server.ts Outdated Show resolved Hide resolved
app/queues/certificate/order-creator-worker.server.ts Outdated Show resolved Hide resolved
app/routes/dev.tsx Outdated Show resolved Hide resolved
@ghost ghost requested review from Genne23v, humphd and SerpentBytes March 9, 2023 20:09
@ghost ghost merged commit 6719cee into DevelopingSpace:main Mar 9, 2023
This pull request was closed.
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.

Create queue and worker for ACME DNS propagation await
4 participants