Add a way for JobExecution storage to be setup before used #107
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some JobExecution storage might require to be setup before used
For instance storing JobExecution in an SQL table, require the table to exists
That storage was using it's own
createSchema
method for that purposeBut other storages might want to do the same, so I introduced an interface
This allows to have a common way to setup storages, and allows the existence of a symfony command to trigger the setup if required