Feature Request P2
Status Update
Comments
ar...@google.com <ar...@google.com>
is...@google.com <is...@google.com>
br...@gmail.com <br...@gmail.com> #3
Hi, this error only affects Cloud SDK version 186. It was previously reported in Issue 72407295 and a fix for it should be released in Cloud SDK version 187.
In the mean time, you can downgrade to Cloud SDK version 185 as a workaround by running the following command:
gcloud components update --version 185.0.0
In the mean time, you can downgrade to Cloud SDK version 185 as a workaround by running the following command:
gcloud components update --version 185.0.0
br...@gmail.com <br...@gmail.com> #4
Oh, but while go112 seems to use the standard go tooling, it seems I still can't pass a ldflags. Cloud Build does the build on my behalf, and I can't pass it ldflags. My goal is the same, but I think a different bug is needed? Thanks
Description
This version is described in a few places:
* What is the desired behaviour of the feature? (Be specific!)
$ goapp deploy -application myapp-1234 -version 1234 -ldflags "-X main.Date=2017-02-16" app.yaml
This would build the binary with the variable main.Date set to '2017-02-16'.
* If relevant, why are current approaches or workarounds insufficient?
Currently I work around this by using a Makefile, sed and a versions.go file. This is doable, but means I have to do something different for my Appengine builds.
* If relevant, what new use cases will this feature will enable?
This will enable embedding better build time information into the application, such as version and date.
thanks.