feat(marketing): invalidate cache after deployment#65707
Conversation
ebfbb64 to
f876dd5
Compare
|
|
||
| - name: "[Test] Invalidate CloudFront Cache" | ||
| env: | ||
| CLOUDFRONT_DISTRIBUTION_ID: ${{ vars.CLOUDFRONT_DISTRIBIUTION_ID }} |
There was a problem hiding this comment.
| CLOUDFRONT_DISTRIBUTION_ID: ${{ vars.CLOUDFRONT_DISTRIBIUTION_ID }} | |
| CLOUDFRONT_DISTRIBUTION_ID: ${{ vars.CLOUDFRONT_DISTRIBUTION_ID }} |
There was a problem hiding this comment.
Just wanted to confirm - I only see the addition of a space here which wouldn't be valid. Did you have a different review comment?
There was a problem hiding this comment.
oops. sorry about that. fixed the missing space.
There was a problem hiding this comment.
The spelling of distribution is incorrect
|
During the transition period, will we also need to invalidate the cache on the Pegasus CloudFront Distribution? |
No, I don't think so. The invalidation makes changes visible instantly but we still have a SWR flag which will cause the pages to be refreshed after ~1-2 hours. We'll have to test it some more once we have the full stack integration in place to ensure the caching mechanism works as expected, though. |
f876dd5 to
47a8c6c
Compare
After deploying the marketing app, invalidate the cache to ensure the live content reflects the deployed application.