-
Story
-
Resolution: Done
-
Undefined
-
None
-
3
-
False
-
None
-
False
-
-
ACM-2047 - ACM Store Compliance History
-
-
-
GRC Sprint 2024-02, GRC Sprint 2024-03
-
No
Value Statement
As a policy user, I need a way to generate a spreadsheet of compliance events within a date range for an audit.
Definition of Done for Engineering Story Owner (Checklist)
- Generating a report as described in the design.
- If using the GET request approach in the design, the API endpoint must return within 30 seconds for a simulation of 3000 managed clusters with 30 policies with each policy having 4 compliance events. This would be done by adding mock data to the database. Speed is important because OpenShift routes timeout after 60 seconds.
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.
- depends on
-
ACM-6857 Write the API endpoint to get compliance events
- Closed
1.
|
[QE] ACM-6884: Add an API endpoint to generate a CSV compliance report | Closed | Unassigned | ||
2.
|
[QE Automation] ACM-6884: Add an API endpoint to generate a CSV compliance report | Closed | Unassigned |