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

ACMEv2: Implement "ready" state for order objects #3530

Closed
cpu opened this Issue Mar 6, 2018 · 3 comments

Comments

2 participants
@cpu
Copy link
Member

cpu commented Mar 6, 2018

Per https://tools.ietf.org/html/draft-ietf-acme-acme-10#section-7.1.6

Once all of the authorizations listed in the order object are in the "valid" state, the order transitions to the "ready" state.

@cpu cpu added this to Backlog in v2 API Mar 6, 2018

@jsha jsha closed this in #3614 Apr 11, 2018

tdelmas added a commit to tdelmas/boulder that referenced this issue May 18, 2018

@tdelmas

This comment has been minimized.

Copy link
Contributor

tdelmas commented May 18, 2018

Quoting @cpu #3725 (comment) :

It's likely to be some time (weeks) before we can enable the feature flag in prod or staging.

@cpu

This comment has been minimized.

Copy link
Member

cpu commented May 25, 2018

It's likely to be some time (weeks) before we can enable the feature flag in prod or staging.

@tdelmas I posted an API announcement with a concrete release schedule today: https://community.letsencrypt.org/t/acmev2-order-ready-status/62866

@cpu cpu moved this from Backlog to Done in v2 API Jun 5, 2018

tdelmas added a commit to tdelmas/boulder that referenced this issue Jul 5, 2018

@cpu

This comment has been minimized.

Copy link
Member

cpu commented Jul 5, 2018

For folks that land here from Google or otherwise this change is now live in production.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment