Test compliance fix
All Submissions:
- [YES] I have added an explanation of what changes in this merge do and why we should include it?
- [N/A] I have updated the documentation accordingly.
- [YES] I have added tests to cover my changes.
- [YES] All new and existing tests passed.
- [YES] My code follows the code style of this project.
- [YES] I ran lint checks locally prior to submission.
What is the current behavior?
The bug and related investigation is explained in the issue linked. Issue: #70 (closed)
What is the new behavior?
- The compliance API now uses the data-partition-id from within the for loop instead of using the one coming in from the compliance-trigger request
Does this introduce a breaking change?
- [No]
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)