Add required capabilities to delivery service structure#7224
Add required capabilities to delivery service structure#7224ocket8888 merged 12 commits intoapache:masterfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## master #7224 +/- ##
============================================
- Coverage 28.37% 28.29% -0.09%
Complexity 98 98
============================================
Files 617 617
Lines 69202 69360 +158
Branches 90 90
============================================
- Hits 19639 19626 -13
- Misses 47754 47922 +168
- Partials 1809 1812 +3
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
ocket8888
left a comment
There was a problem hiding this comment.
I think this should have removed deliveryservices_required_capabilities from API v5 but it doesn't appear to have done that.
ocket8888
left a comment
There was a problem hiding this comment.
This now removes deliveryservices_required_capabilities, but doesn't update the documentation to reflect that.
The new field of a Delivery Service should also be represented in the Delivery Service Overview section.
|
needs conflict resolution to run GHA |
|
@srijeet0406 Also, the API tests still try to create and delete DS required capabilities. See #7801 |
This PR adds the
required capabilitiesinto thedeliveryservicestructure.Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Make
CRUDcalls to the delivery service API and make sure that you can add, remove, modify and get required permissions as part of the DS structure.Make sure all the tests pass.
If this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist