Cloud Function source changes fail to trigger Terraform updates
Developers deploying Google Cloud Functions with Terraform report that editing files inside an uploaded archive at the same path may not trigger a redeployment. They work around this by changing the archive path, but also want change detection to cover imported files and dependency versions—not just the entrypoint. One related signal describes friction switching between functions in a Docker-based development workflow; the reports are from 2018–2019, so the current state of the underlying issue needs validation.
For google Cloud developers using Terraform. Mentioned from Aug 2018 to Apr 2019 on GitHub.
4 different people described this problem in 2 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 5.6/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
The problem is it seems impossible to update a cloud functions source code after its initial deployment via terraform
I can change the blob path dynamically by appending the content hash to it's path, but that's imho just an ugly workaround :)
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks