-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Open
Milestone
Description
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.
Description
I recently start playing around using Terraform to deploy App Engine apps.
One unexpected thing I encountered is that I thought google_app_engine_standard_app_version will take the hash of the source_url into consideration when doing terraform plan and figure out the diff between the intent and the actual version. But looks like this is not how it was implemented.
For example: if I have the TF config below, when I upload a new version of MY_CODE.zip to GCS, terraform should use the hash of the GCS bucket to do diff and start a new push, without me to use a different filename on GCS.
New or Affected Resource(s)
- google_app_engine_standard_app_version
Potential Terraform Configuration
resource "google_app_engine_standard_app_version" "app-version" {
project = "my-project"
service = "default"
runtime = "go113"
version_id = "v1"
deployment {
zip {
source_url = "https://storage.googleapis.com/MY_BUCKET/MY_CODE.zip"
}
}
}References
- #0000
b/374162602