-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deploy: --invalidateCDN, --maxDelete needs be explicitly set #11127
Comments
bep
changed the title
Check --invalidateCDN
deploy: CDN not invalidated unless --invalidateCDN flag is used
Jun 18, 2023
bep
changed the title
deploy: CDN not invalidated unless --invalidateCDN flag is used
deploy: --invalidateCDN, --maxDelete needs be explicitly set
Jun 18, 2023
bep
added a commit
to bep/hugo
that referenced
this issue
Jun 18, 2023
…dateCDN) This was broken in the config rewrite in Hugo 0.112.0. The workaround is to be explicit about setting these flag values (even if just using the defaults), e.g.: --- hugo deploy --invalidateCDN --maxDeletes 256 ``` Fixes gohugoio#11127
bep
added a commit
to bep/hugo
that referenced
this issue
Jun 18, 2023
…, invalidateCDN) This was broken in the config rewrite in Hugo 0.112.0. The workaround is to be explicit about setting these flag values (even if just using the defaults), e.g.: --- hugo deploy --invalidateCDN --maxDeletes 256 ``` Fixes gohugoio#11127
bep
added a commit
to bep/hugo
that referenced
this issue
Jun 18, 2023
…, invalidateCDN) This was broken in the config rewrite in Hugo 0.112.0. The workaround is to be explicit about setting these flag values (even if just using the defaults), e.g.: ´`` hugo deploy --invalidateCDN --maxDeletes 256 ``` Fixes gohugoio#11127
bep
added a commit
to bep/hugo
that referenced
this issue
Jun 18, 2023
…, invalidateCDN) This was broken in the config rewrite in Hugo 0.112.0. The workaround is to be explicit about setting these flag values (even if just using the defaults), e.g.: ``` hugo deploy --invalidateCDN --maxDeletes 256 ``` Fixes gohugoio#11127
bep
added a commit
to bep/hugo
that referenced
this issue
Jun 18, 2023
…, invalidateCDN) This was broken in the config rewrite in Hugo 0.112.0. The workaround is to be explicit about setting these flag values (even if just using the defaults), e.g.: ``` hugo deploy --invalidateCDN --maxDeletes 256 ``` Fixes gohugoio#11127
bep
added a commit
that referenced
this issue
Jun 18, 2023
…, invalidateCDN) This was broken in the config rewrite in Hugo 0.112.0. The workaround is to be explicit about setting these flag values (even if just using the defaults), e.g.: ``` hugo deploy --invalidateCDN --maxDeletes 256 ``` Fixes #11127
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
See https://discourse.gohugo.io/t/hugo-appears-to-have-stopped-invalidating-my-cloudfront-cache/44841/2
The text was updated successfully, but these errors were encountered: