This interface allows us to represent only the actions required for us. And this will help us disassociate container run time specific implementation from main code.
How
Currently an iterable logs and a method to make sure container cleanup happens are our requirements. So we have created an interface for this. We will create implementation of this depending up on container run time along with it's client interface implementation.
Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
It shouldn't since we are only doing refactoring
Database Migrations
None
Env Config
None
Relevant Docs
None
Related Issues or PRs
None
Dependencies Versions
None
Notes on Testing
Tested locally running a workflow.
Screenshots
Checklist
I have read and understood the [Contribution Guidelines]().
What
Why
How
Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
Database Migrations
Env Config
Relevant Docs
Related Issues or PRs
Dependencies Versions
Notes on Testing
Screenshots
Checklist
I have read and understood the [Contribution Guidelines]().