Actions
Bug #31616
closedRemove content_types requirement in katello.yaml and use of it
Description
Instead work purely off the smart proxy capabilities.
May need to move 'fix_pulp3_capabilities' to anytime the supported content types are looked up.
Need to investigate how this impacts navigation loading
Probably want to remove :use_pulp_2_for_content_type: at the same time?
Updated by Ian Ballou almost 4 years ago
- Target version changed from Katello 4.0.0 to Katello 4.1.0
Updated by Justin Sherrill over 3 years ago
- Target version changed from Katello 4.1.0 to Katello 4.2.0
Updated by The Foreman Bot over 3 years ago
- Status changed from New to Ready For Testing
- Assignee set to Ian Ballou
- Pull request https://github.com/Katello/katello/pull/9394 added
Updated by The Foreman Bot over 3 years ago
- Fixed in Releases Katello 4.2.0 added
Updated by Anonymous over 3 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|304de977b189990164968a7d1a482137012bc9d7.
Updated by Ewoud Kohl van Wijngaarden about 3 years ago
- Related to Refactor #33830: Drop content type settings from katello module added
Actions