Upgrade process using "Migration Tool"
I read this in the release notes:
"The preferred (and safest) way to upgrade is now to launch a new copy of Matillion ETL running the latest version, use the Migration Tool to move and validate the new version...In-place upgrade may be removed in future versions."
There are aspects of this that I like, and I want to try it out. But I also have a couple of questions/concerns about it...
First, I am wondering about things that are not "migratable resources." The two things I can think of are that my EC2 instance has (a) additional Python packages I've installed, and (b) certificate files that are needed to authenticate with some APIs.
I suppose it is just a few minutes of effort for me to re-add things like these, to a new instance. Is that indeed what you'd recommend?
Second, how does it work with licensing and costs? If I have an annual license for a single instance, then what happens when I launch a new, second instance? Do I incur hourly Matillion charges for the second instance, while I have two instances running at the same time? And then, do I need to do anything to "map" my annual license to the new instance? Or once I finish the migration and validation, and delete the old instance, does the annual license automatically get "mapped" to the new instance?