Add CloudFront invalidation to SFA S3 upload workflow #5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The automated workflow for SFA forecasting results in files being updated on S3, but the associated CloudFront distribution was not being udpated. This adds the required CloudFront invalidation as the final step in the workflow.
davereinhart
force-pushed
the
main
branch
2 times, most recently
from
f88a889 to
e1174ad
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The automated workflow for SFA forecasting results in files being updated on S3, but the associated CloudFront distribution was not being updated. This adds the required CloudFront invalition as the final step in the workflow.