-
Story
-
Resolution: Unresolved
-
Critical
-
Global Hub 1.5.0
-
Product / Portfolio Work
-
2
-
False
-
-
False
-
-
-
-
Critical
-
None
Value Statement
Ensure the issue title clearly reflects the value of this user story to the
intended persona. (Explain the "WHY")
Definition of Done for Engineering Story Owner (Checklist)
Based on the bundle sync consolidate solution provided by the spike story: https://issues.redhat.com/browse/ACM-21905.
The current user story should contains the following cases:
- Define the compliance bundle support both full and delta updates between global hub and managed hub
- Change the global hub agent with related syncer adopt the stream compliance bundle sync
The agent sync the delta bundle when:1. the bundle size is up to 1 MiB;2. There are some new update in the bundle during the last 5 seconds
The agent sync the full bundle(resync) when:1. the manager request resync the bundle(manager start);2. the agent is starting3. resync interval, current with 5 hours
- Manager updates
-
- Modify the manager handler can process the new bundle for policy compliance
- Add the logic in the manager conflation to support the new bundle deliver, avoid the race condition in bundle handler
Development Complete
- The code is complete.
- The compliance is synced into the database
- 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 template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.