Fixes #11262: Only update Candlepin content for library repositories #5390
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This prevents updating the Candlepin content for cloned repositories to prevent certain attributes from being reset. For example, since the cloned repositories may not have an associated gpg key url, a call to update would set this value to nil in Candlepin and thus break GPG key checks on signed packages for instances of the repository. This is because library repositories and their clones are linked to the same content object in Candlepin.
|
ACK |
ehelms
added a commit
that referenced
this pull request
Jul 31, 2015
Fixes #11262: Only update Candlepin content for library repositories
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This prevents updating the Candlepin content for cloned repositories
to prevent certain attributes from being reset. For example, since
the cloned repositories may not have an associated gpg key url, a call
to update would set this value to nil in Candlepin and thus break GPG
key checks on signed packages for instances of the repository. This is
because library repositories and their clones are linked to the same content
object in Candlepin.