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

Refactor advisory conflict management #3642

Open
dralley opened this issue Jun 26, 2024 · 1 comment
Open

Refactor advisory conflict management #3642

dralley opened this issue Jun 26, 2024 · 1 comment
Labels

Comments

@dralley
Copy link
Contributor

dralley commented Jun 26, 2024

Pulp should, probably, try to stop merging Errata and do away with as many special cases as possible. Hopefully without rediscovering all the reasons why it was done this way originally. If we can get rid of it entirely, that would be ideal.

At minimum, testing various combinations of bad data needs to be much easier.

One possibility, if we can't completely avoid errata merge, is to make each errata being independent documents, modeled more simply (possibly with one jsonfield), theoretically that could satisfy making the logic simpler while also making it easier to test. (there's some disagreement over whether that it would be simpler FWIW)

@ggainey
Copy link
Contributor

ggainey commented Jun 27, 2024

Current state is just All Edge Cases, because advisories in The Real World are always more complicated/uglier than we expect. We def need to refactor to make this more sane - but a lot of discussion/design will be needed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants