Deploy process executing out of order

[jelder]

The CloudFront invalidation is issued before the new assets are uploaded.

jacob@jeldair:~/code/boundless/spar-examples/todos$ spar deploy production
Deploying /Users/jacob/code/boundless/spar-examples/todos to the production environment
Invalidation InProgress after 0.12 seconds
Invalidation InProgress after 0.25 seconds
Invalidation InProgress after 0.41 seconds
Invalidation InProgress after 0.62 seconds
Invalidation InProgress after 0.95 seconds
Invalidation InProgress after 1.47 seconds
Invalidation InProgress after 2.40 seconds
Invalidation InProgress after 4.10 seconds
Invalidation InProgress after 7.40 seconds
Invalidation InProgress after 13.91 seconds
Invalidation InProgress after 26.83 seconds
Invalidation InProgress after 52.54 seconds
Invalidation InProgress after 104.24 seconds
Invalidation InProgress after 206.80 seconds
Invalidation InProgress after 411.85 seconds
Invalidation Completed after 616.80 seconds
Deployed Asset: application.js
Deployed Asset: jquery.min.js
Deployed Asset: route.min.js
Deployed Asset: application.css
Deployed Asset: ui/bg.png
Deployed Asset: index.html

[mhodgson]

This is actually just the way its logged. Do you think we should say the asset is deployed before it is invalidated? Note it is 'deployed' not 'uploaded'.

[jelder]

As a user I assume that logs represent the order in which things happened.

[mhodgson]

Obviously, but do you really consider a file deployed before it is invalidated from the cache? It isn't accessible yet....

[jelder]

Then it would be more obvious if we reported uploads independently or instead of of "deployments" of each asset.