Releases: lalalilo/aws-spa
v3.0.3
v3.0.2
v3.0.1
3.0.0
The behavior is unchanged on CI environments where the CI
env variable is set (this is the case of most CI services such as Travis and CircleCI).
If you deploy from an environment where CI
env variable is not set, you'll be prompt a confirmation message before deploying. You can remove this message thanks to the option --noPrompt
2.0.0
Add options to specify cache behavior: cacheInvalidation
and cacheBustedPrefix
.
There is a change in the behavior when not specifying these options:
cacheInvalidation
: was implicitly set toindex.html
. Now its default value is*
cacheBustedPrefix
: was implicitly set tostatic/
. Now its default value isundefined
(no cache busted folder)
To get the exact same behavior you must change:
- aws-spa deploy app.example.com
+ aws-spa deploy app.example.com --cacheInvalidation "/index.html" --cacheBustedPrefix "static/"
Write the code change above only if you use create-react-app
.
1.6.0
✨ Introducing basic auth to avoid non-production apps to be indexed.
1.5.1
Fix error "The specified bucket does not exist" on first deploy while adding public read to the bucket.
it seems to be due to some aws s3 async task while creating a bucket because it seems that we are correctly waiting for each HTTP request to be done before launching the next one.
1.5.0
Fixes:
- ACM certificate creation now waits for certificate creation.
Improvements:
- ACM certificate creation is now fully automated thanks to DNS validation
- It is now possible to deploy on root domain