refactor: make the Launcher abstraction less opinionated #3273
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.
Description
After these changes the
Launcher
class will delegate more of how a test is run down to the actual implementation of the runtime platform (e.g. local, AWS Lambda, AWS ECS or something else).It will no longer manage workers directly via
createWorker()
,prepareWorker()
etc.The only concerns handled in Launcher now are to:
'stats'
or'phaseCompleted'
and aggregate metric reports from multiple workersThese changes make it easier to implement support for new platforms and to move the existing AWS ECS implementation over to use the
Launcher
abstraction.Pre-merge checklist
This is for use by the Artillery team. Please leave this in if you're contributing to Artillery.