Closed psycofdj closed 2 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/179732578
The labels on this github issue will be updated when the story is started.
Confirmed. This behavior change was introduced in v0.38.0 unintentionally as a side effect of removing vendored Go dependencies.
Unfortunately, as far as I am aware there is no way to plumb in proxy environment variables into the bosh compilation VMs or otherwise provide "deploy time" configuration to the compilation environment.
To support this use case, I think go vendoring will need to be added back to the relevant components and support added back to the packaging scripts to consume that vendoring.
This has been fixed in the v0.39.0 release. This should be available on bosh.io shortly.
We have adjusted our CI testing pipeline to avoid this sort of regression in the future by always compiling pxc-release in a BOSH environment whose compilation VMs do not have public internet access.
v0.39.0
compiles fines, thank you for your work !
Bug Report Info
Currently:
The
v0.38.0
release cannot compile on air-gaped environment as many go packages fetch their dependencies on internet. Example for packagemigrate-to-pxc
provided in reference section.I believe this new behaviour was introduced by commit 1c6ff903fa458b197e5ceb6905238924704ba00f (between releases
v0.37.0
andv0.38.0
).Expected:
We expect the release to somehow compile on air-gaped environments.
Is it possible to configure proxy environment variables on bosh compilation VMs ?
Reference:
Package
migrate-to-pxc
compilation error: