Skip to content

Conversation

@djc
Copy link
Owner

@djc djc commented Mar 28, 2025

No description provided.

@djc djc requested a review from cpu March 28, 2025 10:30
Copy link
Collaborator

@cpu cpu left a comment

Choose a reason for hiding this comment

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

Looking good. I had a couple pieces of small feedback to consider.

Self {
identifiers,
replaces: None,
profile: None,
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think similar to ARI we should also gain a profile: Option<String> field on the OrderState.

That would let NewOrder's that don't specify a profile learn what "default" profile the server assigned their order:

If the server is advertizing profiles and receives a newOrder request which does not identify a specific profile, it is RECOMMENDED that the server select a profile and associate it with the new Order object.

Relatedly, the profiles spec doesn't say the server MUST reflect the matching profile for new order requests that do specify a profile. That's probably good feedback to give to the author. I think ideally we would enforce it matches like for ARI.

Copy link
Owner Author

Choose a reason for hiding this comment

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

The spec isn't specific at all about whether the order state will actually reflect back the selected profile, I think?

Copy link
Collaborator

@cpu cpu Mar 28, 2025

Choose a reason for hiding this comment

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

Yeah, I think there's language missing to make that crystal clear. I'm partly inferring it based on the registry update ("ACME Order Object Fields") and the accompanying Pebble logic:

Copy link
Collaborator

Choose a reason for hiding this comment

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

It's also similar in the Boulder order JSON

Copy link
Owner Author

Choose a reason for hiding this comment

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

Also, I couldn't think of a great way to test this.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yeah I think the Pebble test code makes it annoying to get at the order state while also using all the shared logic for completing the order. Seems fine to not test it explicitly for now. I think the spec should be updated to be clearer and then we can check it in the lib.rs code.

Copy link
Collaborator

Choose a reason for hiding this comment

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

The spec isn't specific at all about whether the order state will actually reflect back the selected profile, I think?

@djc It looks like this got addressed in -01 🎉

diff

@cpu
Copy link
Collaborator

cpu commented Mar 28, 2025

Also maybe worth a README mention as a supported feature? :-)

@djc djc merged commit 37566b0 into main Mar 28, 2025
9 checks passed
@djc djc deleted the profiles branch March 28, 2025 17:00
@djc djc mentioned this pull request Jul 9, 2025
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.

3 participants