Pilot built without version information
Closed this issue · 6 comments
The gobuild script istio uses captures build information
Here's the invocation
https://github.com/istio/istio/blob/99d9f3fda4bd7ae1a851306a0140d67ca3c324cd/bin/gobuild.sh#L56
The script sets these properties when building the go application
https://github.com/istio/istio/blob/99d9f3fda4bd7ae1a851306a0140d67ca3c324cd/bin/get_workspace_status.sh#L49
This is exposed when running the version
command for the binary
I don't see these settings set in pilot's packaging's script
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/161561530
The labels on this github issue will be updated when the story is started.
So I was thinking about this @dprotaso and wanted to know what most people do for external dependencies they are building themselves. Do we just make it a SHA of the repo we used? Do we try to mirror some version number? Do we make up our own (hate this idea but good to document that we shouldn't do it).
Feels like SHA is the best idea but I am sure we are open to other suggestions.
Istio integration with CF is now happening in https://github.com/cloudfoundry/cf-for-k8s via https://github.com/cloudfoundry/cf-k8s-networking