Details
-
Fix
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
Desired Behavior
- improve performance of /inventory/dependencies API
- enhance the stability of provided related objects from deeper levels of dependence
- provide information for related objects of deeper levels that keep the relation to its parent intact
- provide information about which objects have to be enforced for the subsequent deploy and release operation
- the enforcement depends on
- previous operations that changed the object - store, rename
- exisitence of previous released/deployed versions of the references
- the enforcement depends on
Changes
- new Response
- the new response should contain all related objects
- requested items
- all their direct references
- and all related references from deeper levels
- the objects in the response are
- unique - no duplicates
- identified by their ID - to be able to resolve references by their IDs and to prevent duplicated objects
- objects are unique, referenced IDs can be present multiple times
- each holding its own direct references only and information about their enforcement from the POV of the parent object
- the new response should contain all related objects
- Performance
- improve the recursive determination of dependencies
- improve the storage of determined relations
- reduce client sided enforcement processing
- the determination of enforcement will be processed by the API and provides the information to the client
- the client does not need to determine the enforcement on its own anymore
- the client only needs to process the provided information
Attachments
Issue Links
- affects
-
JOC-2161 Release of any releaseable Object should work without errors
-
- Released
-