1.6 KiB
title
| title |
|---|
| Upgrade |
Release channels
Stable
abra upgrade
Release candidate
abra upgrade --rc
Migration guides
v0.3.x -> v0.4.x
Make sure to back up your ~/.abra/servers configurations first for safety.
-
Please run
mv ~/.abra/apps ~/.abra/recipes. -
"app name" as a concept went away,
abranow uses the domain name of an app as the identifier. However, we don't expect to see breaking behaviour if you have.envfiles like~/.abra/servers/foo.com/mycoolapp.envand you still want to runabra app ps mycoolapp.abrastill reads the filename to figure out the identifier. When runningabra app new <recipe>,abrawill now take the domain name as the name of the.envfile. -
abrahas a new SSH implementation which enforces SSH host key checking. You may run into connection issues as a result of this code churn, please see this entry for help navigating a fix. -
CLI flag/args handling has been made more flexible. We're workign within the constraints of an upstream library issue but have hopefully made it easier to mange passing flags to commands with
abra. See this troubleshooting entry for the full review. -
A number of short style flags have been re-mapped and/or added. This is again related to an issue with the upstream CLI library which sometimes understands short style flags as long style flags. E.g.
--chinstead of-chfor--chaos. As a concrete example,--chis now-Conabra app deploy.