As we’re moving to TC2.1, we’ve found that the goose migration requires not just the goose binary to be installed, but also the go compiler and a fairly large set of dependencies. Most of these are a result of the migration of the MSO parent_retry parameters from the DS table into the profile_parameters table.
We have a very hard requirement that our product CANNOT require Internet access for installation. We’d like to avoid vendoring (in one form or another) all of the goose dependencies, the same way we’ve had to do with web-deps and CPAN. We are considering two solutions: 1) Replace the .go migration with a PL/SQL file that does not require all of the go dependencies. In this case we would compile goose and ship it as a binary in our RPM to eliminate the ‘go get goose' 2) Switch to a different fork of goose (https://github.com/pressly/goose) that can execute binary migrations. Here we would compile the .go migration into a binary and ship both the new goose binary and the migration binary in our RPM. —Eric
