Properly Rename Extra CA Certificates (PROJQUAY-1306) #372
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.
Issue: https://issues.redhat.com/browse/PROJQUAY-1306
Changelog: Only add
extra_ca_cert_
prefix to actual extra CA certificates when creating newconfigBundleSecret
.Docs: N/a
Testing: N/a
Details: We were previously adding the
extra_ca_cert_
prefix to all certificates received by thecerts
payload to the/reconfigure
endpoint. This is incorrect, as some files are used for other purposes (likecloudfront-signing-key.pem
) and are referenced by filename inconfig.yaml
. Changing the name of this file breaks Quay when it tries to open the file.