-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
ACME: add support for IP identifiers #53660
Conversation
This comment has been minimized.
This comment has been minimized.
6d096cf
to
64f09f7
Compare
The test
|
@mattclay I want to preserve the trailing whitespaces in the OpenSSL outputs which are part of the unit tests. I've tried to skip the pep8 tests for this unit tests (df7e282d87f5cdf0d01cbe65492e2412ea7ca470), but this apparently didn't work. Do you know what went wrong? I could also do this by adding |
@felixfontein Definitely don't skip the pep8 checks. For large static content like that, I'd put it in a separate file and load it during the test instead of trying to embed it in the code. |
df7e282
to
a27afa7
Compare
@felixfontein Yes, the folder structure is correct. The unit tests to run will be determined based on import analysis, so there's no issue there. It's actually more important that the fixtures are in the correct location so changes to them will run the tests. Those are OK as well. You can check with the following commands:
Those will show what tests will run based on files changing. |
@mattclay great, thanks a lot! |
ready_for_review |
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.
don't see anything to block this from getting in. Good job.
shipit
SUMMARY
According to https://tools.ietf.org/html/draft-ietf-acme-ip-05. First interoperability tests with letsencrypt/pebble#221 are looking good. This is essentially the
acme_certificate
part of #53228.ISSUE TYPE
COMPONENT NAME
acme_certificate