Recursive and conservative recursive copy
With the fix for the Issue #4152, the default behaviour of recursive copy changes back to the state before 2.17, rendering the test case CopyRecursiveUnitsTestCase broken.
The behaviour specified in the pulp smash issue 1090, as requested in the Issue #2478, is now optional and can be triggered by providing the
"recursive_conservative": true config override instead of the default
With that setting, the test case CopyRecursiveUnitsTestCase should agin pass as is.
Proposed solution¶Split the test case CopyRecursiveUnitsTestCase such that it asserts:
- a failure in the terms described in pulp smash issue 1090 with the default
"recursive": trueconfig override setting
- a success once the non-default
"recursive_conservative": trueconfig override setting is provided
Please register to edit this issue