Actions
Feature #37930
openRequesting Incremental Content View Update with unavailable content should fail
Status:
New
Priority:
Normal
Assignee:
-
Category:
Content Views
Target version:
-
Description
Discussed in the Pulp/Katello Community Meeting: https://hackmd.io/U9Q0Js0bRPez7oCgxUawng?view#2024-09-18-1000-1030-GMT-5
Creation of an Incremental Update to a content view should fail if the requested content is not available.
At the moment it just creates a new content view version without added content.
The reason for not available content can be for example if the repository supplying the content had not been added in the content view version that should be updated. Maybe we need a good error-message for that since "requested content not available" might be confusing, if it is available in the library lifecycle.
Actions