Not sure quite why, but Hugo was invalidating the cache quite successfully but is no longer doing so. What have I done wrong?
The output of hugo deploy says this:
Deploying to target “pbj-s3” (s3://xxxxxxxxx?region=us-west-1)
Identified 77 file(s) to upload, totaling 21 MB, and 0 file(s) to delete.
Success!
…and there is no invalidation message any more, nor an invalidation job listed in the AWS invalidation list.
I do have a few separate [[deployment.matchers]] sections in my config.toml, which I gather seems to be an issue sometimes, but unsure what the issue might be. Here’s the deployment section, suitably edited.
Is there anything that I can do to help debug this issue?
[deployment]
[[deployment.targets]]
name = “pbj-s3”
URL = “s3://xxxxxxxxxxx?region=us-west-1”
cloudFrontDistributionID = “EU4xxxxxxxxx”
I can’t tell you, really (my Hugo upgrades are automatic). It was working fine on June 7, according to my invalidation logs, when I saw a Hugo-submitted invalidation call. It looks like Hugo’s upgrade to v0.113.0 was released on June 6, so may have happened on my system on June 8 or 9. I haven’t seen one since. So I would guess that it is related.
I have discovered that hugo deploy --invalidateCDN --verbose works fine. It looks perhaps like a regression of this bug perhaps?