Right now the plugin is processing its configuration and it adds each file to the queue handled by serverless AWS provider.
This gives no control over the order of uploaded files
My use case:
I have a project that consists of source code of a single page app. The code is bundled into several css js and font files and one html file.
It is important for the deployment to be consistent to have a way to upload everything but the html file first and only if it succeeded then upload html file.
I see no way to do that just by using configuration of the plugin
I analysed the code and I see that the promise returned by the awsProvider@request is discarded:
|
this.provider.request('S3', 'putObject', details, this.options.stage, this.options.region); |
File uploads could possibly be sequentialised on 2 levels:
- assets
- files in each asset
with current syntax. Right now everything runs in parallel (or: as parallel as awsProvider allows it to be)
I'd like to open a discussion about:
-
whether the plugin should allow sequences
-
should it
- process assets and files in sequence
- process assets in parallel but files should be uploaded sequentially
- process assets sequentially but files should be uploaded in parallel
- introduce new syntax to express sequences and keep current syntax for maximum parallelisation
Right now the plugin is processing its configuration and it adds each file to the queue handled by serverless AWS provider.
This gives no control over the order of uploaded files
My use case:
I have a project that consists of source code of a single page app. The code is bundled into several css js and font files and one html file.
It is important for the deployment to be consistent to have a way to upload everything but the html file first and only if it succeeded then upload html file.
I see no way to do that just by using configuration of the plugin
I analysed the code and I see that the promise returned by the awsProvider@request is discarded:
serverless-s3-deploy/index.js
Line 103 in 1107710
File uploads could possibly be sequentialised on 2 levels:
with current syntax. Right now everything runs in parallel (or: as parallel as awsProvider allows it to be)
I'd like to open a discussion about:
whether the plugin should allow sequences
should it