Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Noticed this while trying to reproduce the situation described in issue #4808. Updating a cert file in place that is referenced in the ssl_multi_cert.config file was doing nothing. The Secret file was not being cleared during the reload before the server cert reloading would occur. I believe this problem was introduced by PR #6609. I am surprised we haven't been hit by this. We must either be running our cert update plugin or restarting the process on each server cert update.
I added a test to exercise config reload with an updated server certificate file. We already had such test for the client cert update.
While exercising this I noticed that you no longer need to touch the ssl_multi_cert.config file when only the referenced cert and key files are updated as described in issue #3931. I think that has been fixed for a while. The commit from @zizhong mentioned in the issue seems to be the logic that fixed it.