-
Spike
-
Resolution: Done
-
Undefined
-
None
-
None
-
1
-
False
-
-
False
-
-
-
No
Value Statement
This will be a spike story to investigate what will be needed for the api change.
This is a larger effort as there are backwards compatibility concerns.
We want the related resource query to group results by apigroup and kind.
Currently for related resource queries we allow the following fields:
related: { kind count items }
This proposal would allow the following:
related: { apigroup apiversion kind count items }
Definition of Done for Engineering Story Owner (Checklist)
- ...
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the [Customer
Portal_doc_issue template](
https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
and ensure doc acceptance criteria is met. Link the development issue to
the doc issue. - [ ] Provide input to the QE team, and ensure QE acceptance criteria
(established between story owner and QE focal) are met.
Support Readiness
- [ ] The must-gather script has been updated.