Skip to content
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.

Sign up for GitHub

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

Jump to bottom

deploy: --invalidateCDN, --maxDelete needs be explicitly set #11127

Closed
bep opened this issue Jun 18, 2023 · 1 comment · Fixed by #11129
Closed

deploy: --invalidateCDN, --maxDelete needs be explicitly set #11127

bep opened this issue Jun 18, 2023 · 1 comment · Fixed by #11129
Assignees
@bep
Labels
Bug Outdated
Milestone
v0.114.1

Comments

@bep
Copy link
Member

bep commented Jun 18, 2023 •
edited

See https://discourse.gohugo.io/t/hugo-appears-to-have-stopped-invalidating-my-cloudfront-cache/44841/2
@bep bep added this to the v0.114.0 milestone Jun 18, 2023
@bep bep self-assigned this Jun 18, 2023
@bep bep changed the title Check --invalidateCDN deploy: CDN not invalidated unless --invalidateCDN flag is used Jun 18, 2023
@bep 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
@bep
Fix deploy defaults for non-zero flag values (e.g. maxDeletes, invali…
559412a 
…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
@bep
deploy: Fix deploy defaults for non-zero flag values (e.g. maxDeletes…
3f95759 
…, 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
@bep
deploy: Fix deploy defaults for non-zero flag values (e.g. maxDeletes…
a577d4e 
…, 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 bep mentioned this issue Jun 18, 2023
Merged
bep added a commit to bep/hugo that referenced this issue Jun 18, 2023
@bep
deploy: Fix deploy defaults for non-zero flag values (e.g. maxDeletes…
4d5cced 
…, 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
@bep
deploy: Fix deploy defaults for non-zero flag values (e.g. maxDeletes…
3769fb6 
…, 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
@bep
deploy: Fix deploy defaults for non-zero flag values (e.g. maxDeletes…
12dc9a6 
…, 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
@bep bep modified the milestones: v0.114.0, v0.114.1 Jun 23, 2023
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bep bep

Labels
Bug Outdated
Projects
None yet
Milestone
v0.114.1
Development

Successfully merging a pull request may close this issue.

Fix deploy defaults for non-zero flag values (e.g. maxDeletes, invalidateCDN) bep/hugo
1 participant
@bep