I'm not sure if this is an issue or just a question. I can see that a CloudFront invalidation is executed on the / and /indexDoc paths. Is the aim to invalidate just those two paths or all files in the CloudFront distribution? The reason I ask is that the AWS documentation says that the /* path is used to invalidate all files.
More context
When deploying an SPA to an AWS environment I've noticed that the changes are not always visible. E.g.
- First deploy. Everything works.
- Subsequent deploys. E.g. Add a
console.log("hello world"). The output of the log is not displayed in the console.
I've tried clearing the browser cache. That doesn't work. I can see the correct version of the file exists in the S3 bucket. The only way I've managed to fix the issue is to manually run a CloudFront invalidation using the path /*.
I'm not sure if this is an issue or just a question. I can see that a CloudFront invalidation is executed on the
/and/indexDocpaths. Is the aim to invalidate just those two paths or all files in the CloudFront distribution? The reason I ask is that the AWS documentation says that the/*path is used to invalidate all files.More context
When deploying an SPA to an AWS environment I've noticed that the changes are not always visible. E.g.
console.log("hello world"). The output of the log is not displayed in the console.I've tried clearing the browser cache. That doesn't work. I can see the correct version of the file exists in the S3 bucket. The only way I've managed to fix the issue is to manually run a CloudFront invalidation using the path
/*.