Current package filters were only implemented to associate with products, but we need them to associate with repositories as well. The ui was written with this assumption.
We decided to do it months ago, but we can push to post v1 as long as we disable some of the UI bits that allow you to try to add repos.
Hey Bryan, do we know what we're going to do with this? We need either frontend or backend work no matter which path we take. -Justin
Actually the UI controller ignores the repository attributes coming from the browser (doesn't actually get sent to the model layer). The ui itself though allows selecting and removing repos and sends those updates to the controller. If the model layer supports it, it would be trivial to pass these values from the controller down. -Justin
thanks.. will get it on the backlog.
I switched the component to WebUI. The model layer is ready and we already have this functionality in API/CLI. Frontend seems to be there. The only thing that remains is to connect it in UI controller.
Shouldbe fixed as of 696125a9adecd4e6a9321b0531d50786f1b5f795