I had that thought, as well as there are more recent versions like https://github.com/mattes/migrate. The question becomes if we ever get around to rewriting TrafficOps APIs in golang, will the Perl version then become obsolete?
On Fri, Apr 28, 2017 at 11:58 AM, Dave Neuman <neu...@apache.org> wrote: > Maybe it's time we take a look at what goose really buys us and consider > writing our own database migration tool. We already have admin.pl, it > could probably fit in with that? > > On Fri, Apr 28, 2017 at 11:45 AM, Eric Friedrich (efriedri) < > efrie...@cisco.com> wrote: > > > Hey Dew- > > What calls this script? > > > > If its called from the Traffic Ops Spec file, then this will cause some > > pain for those of us that need to install without internet access. > > > > —Eric > > > > > On Apr 28, 2017, at 12:41 PM, Dewayne Richardson <dewr...@gmail.com> > > wrote: > > > > > > I'm working toward a more streamlined installation process for Traffic > > Ops > > > (internally) and publicly. Of course, the same hiccups that everyone > else > > > runs into I am as well. Installation of Golang (proper version) and > > > installation of Goose. Goose has been the most challenging for several > > > reasons. The maintainer hasn't made any real changes since 2015, and > has > > > not "branched" his code to allow for explicit version download. Per > his > > > installation instructions "go get bitbucket.org/liamstask/goose/ > > cmd/goose" > > > > > > So I'm I'm proposing to write an installer script in bash to help > > automate > > > the Golang install as well as the Goose install. My only concern (as > > well > > > as most of yours) is "go get" will grab the latest, but since no real > > > changes have happened I'm left with no other option. > > > > > > Proposed: > > > > > > /opt/traffic_ops/install/bin/install_goose.sh > > > > > > - Install Golang (version 1.8.x) > > > - go get bitbucket.org/liamstask/goose/cmd/goose > > > > > > Thoughts? > > > > > > -Dew > > > > >
