You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2023. It is now read-only.
Instead of having to include a valid invalidation batch, why not build the invalidation batch from a much simpler configuration?
Please see sspinc/grunt-cloudfront@30db42bd0290040392ea24ddd16da8adc82172d4 in our fork. This is the only difference and we would love to contribute this back in a backwards-compatible manner by checking the configuration whether it already includes Paths and CallerReference or it expects grunt-cloudfront to assemble it).
It would make it much easier to invalidate paths, especially if they are determined dynamically.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Instead of having to include a valid invalidation batch, why not build the invalidation batch from a much simpler configuration?
Please see sspinc/grunt-cloudfront@30db42bd0290040392ea24ddd16da8adc82172d4 in our fork. This is the only difference and we would love to contribute this back in a backwards-compatible manner by checking the configuration whether it already includes
Paths
andCallerReference
or it expectsgrunt-cloudfront
to assemble it).It would make it much easier to invalidate paths, especially if they are determined dynamically.
The text was updated successfully, but these errors were encountered: