-
-
Notifications
You must be signed in to change notification settings - Fork 601
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
Add a new remoteva binary #7437
Conversation
@pgporada, this PR appears to contain configuration and/or SQL schema changes. Please ensure that a corresponding deployment ticket has been filed with the new values. |
Config change ticket: IN-10231 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks really good! I have just a few comments right off the top, I'm going to dive into the mTLS bits now.
* Adds a new `remoteva` binary that takes a distinct configuration from the existing `boulder-va` * Removed the `boulder-remoteva` name registration from `boulder-va`. * Existing users of `boulder-remoteva` must either 1. laterally migrate to `boulder-va` which uses that same config, or 2. switch to using `remoteva` with a new config. Part of letsencrypt#5294
* Adds a new `remoteva` binary that takes a distinct configuration from the existing `boulder-va` * Removed the `boulder-remoteva` name registration from `boulder-va`. * Existing users of `boulder-remoteva` must either 1. laterally migrate to `boulder-va` which uses that same config, or 2. switch to using `remoteva` with a new config. Part of letsencrypt#5294
remoteva
binary that takes a distinct configuration from the existingboulder-va
boulder-remoteva
name registration fromboulder-va
.boulder-remoteva
must eitherboulder-va
which uses that same config, orremoteva
with a new config.Part of #5294