I had this PR in an almost finished state for many months … Now it is.
Thanks. Appreciate this change because I was trying to figure out how to do it by mining the git log for changes and feeding it to
aws cloudfront create-invalidation .....
Let me know if my “cache logic” makes sense in real life scenarios.
My first try at adding the distribution id in the s3deploy command at circleci worked just fine. Prior to this, if I deploy, then check the page forgetting to invalidate, the page is unchanged. Now, "it just works"™. Thanks!
This test was just a single page update (https://esolia.com/japan-apps/) in two languages, so I’ll let you know if I observe anything else.