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.

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

Fix deploy defaults for non-zero flag values (e.g. maxDeletes, invalidateCDN) #11129

Merged
merged 1 commit into from
Jun 18, 2023

Conversation

bep
Copy link
Member

@bep bep commented Jun 18, 2023

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 force-pushed the fix/defaultdeployflagsdefaults-11127 branch 3 times, most recently from a577d4e to 4d5cced Compare June 18, 2023 17:00
…, 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 force-pushed the fix/defaultdeployflagsdefaults-11127 branch from 4d5cced to 3769fb6 Compare June 18, 2023 17:13
@bep bep merged commit 12dc9a6 into gohugoio:master Jun 18, 2023
Copy link

This pull request 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 Jun 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

deploy: --invalidateCDN, --maxDelete needs be explicitly set
1 participant