Skip to content
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

Added ALLOW_UNSAFE_ADVISORY_CONFLICT_RESOLUTION. Default is False. #1950

Merged
merged 1 commit into from
Mar 25, 2021

Conversation

ggainey
Copy link
Contributor

@ggainey ggainey commented Mar 10, 2021

closes #8250

@pulpbot
Copy link
Member

pulpbot commented Mar 10, 2021

Attached issue: https://pulp.plan.io/issues/8250

@ggainey
Copy link
Contributor Author

ggainey commented Mar 11, 2021

Pending discussion on whether we even continue to do the complicated-choice-logic for errata-conflicts or just go with a mirror strategy.

@dralley dralley marked this pull request as draft March 11, 2021 19:44
CHANGES/8250.feature Outdated Show resolved Hide resolved
@ggainey ggainey force-pushed the 8250_unsafe_advisory_merge branch 3 times, most recently from 23abf77 to 7359800 Compare March 24, 2021 22:35
@ggainey ggainey marked this pull request as ready for review March 24, 2021 22:36
Comment on lines +44 to +45
This approach to conflict-resolution is done **AT YOUR OWN RISK**.
Pulp cannot guarantee the usability/usefulness of the resulting advisory.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Member

@goosemania goosemania left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great job!

@ggainey ggainey merged commit 651ee79 into pulp:master Mar 25, 2021
@ggainey ggainey deleted the 8250_unsafe_advisory_merge branch March 31, 2023 20:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants