-
Notifications
You must be signed in to change notification settings - Fork 43
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
Update TLS certificates in tests #169
Conversation
8228833
to
66c31d7
Compare
Some TLS certificates used in tests expired, this commit fixes it by generating the certificates and, if needed, calculating the fingerprint on each test. This will prevent future CI failures and reduce the maintenance burden.
66c31d7
to
2edaf34
Compare
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.
Looks good. Thanks for fixing it where it won't need to be updated again.
} | ||
|
||
// If for any reason there is a need to debug |
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.
If for some reason this fails in CI, we are going to want the cert/key pair to see what happened. How about always dumping out the keys & certs, then deleting the dir if the test succeeds?
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.
Yeah, I first thought about it, but while writing this PR what helped me was to have a fixed set of certs that I could use over multiple test runs. So I ended up generating them once and re-using until I found out where the mismatch between cert, CA and fingerprint were.
Anyway, I see no issue in persisting them on failure.
All suggestions implemented on 9d031ae |
9d031ae
to
793de7e
Compare
💚 Build Succeeded
History
cc @belimawr |
What does this PR do?
Some TLS certificates used in tests expired, this commit fixes it by generating the certificates and, if needed, calculating the fingerprint on each test.
This will prevent future CI failures and reduce the maintenance burden.
Why is it important?
It fixes the broken tests
Checklist
- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.md
## Author's Checklist## Related issues