EREGCSC-2269 - New serverless invalidate package. #1110
Closed
Conversation
This file contains 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
|
✨ See the Django Site in action ✨ |
|
✨ See the Django Site in action ✨ |
thwalker6
requested review from
PhilR8,
cgodwin1 and
peggles2
as code owners
|
✨ See the Django Site in action ✨ |
|
✨ See the Django Site in action ✨ |
|
✨ See the Django Site in action ✨ |
thwalker6
changed the title
|
Created a follow up ticket. https://jiraent.cms.gov/browse/EREGCSC-2478. Closing this. |
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.
Resolves # EREGCSC-2269
Description-
Change serverless-cloudfront-invalidate to serverless-cf-invalidate-proxy
serverless-cf-invalidate-proxy is an npm package I created that is the same as invalidate but changes the proxy-agent from 5 to 6. 5 is what contained the package that was causing the issue. Cloud front invalidate has been sitting on the issue and multiple people report this on the github and no one answered. I merely took their package and made the change, and published it.
This pull request changes...
Steps to manually verify this change...