Use apps.json to power upgrade / rollback, add helper commands #135
Reference in New Issue
Block a user
No description provided.
Delete Branch "apps-json"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #130, #131 and #134
abra-apps.jsonas~/.abra/apps.json, update it as needed (i.e. when remote modified time is more recent than the local mtime)abra recipe lsto list all recipes available inapps.jsonabra recipe <recipe> versionsto show all a recipe's versionsabra recipe <recipe> release, replacingbin/app-version.sh, to sync git tags and Docker deploy labels with image versions, using metadata from Skopeo -- this also handles bumping recipe versions according to the logic in coop-cloud/organising#51require_yqinto a genericvendor_binaryfunction, and use it for bothjqandyqabra app <app> deploycommand to accept an optional<version>argument, and makeabra app <app> rollbackwork the same asabra app <app> deploy <last-version>(i.e. no longer usingdocker service rollback, which seems like it'll rarely be what people want)require_app_latestwithrequire_app_version, which accepts a recipe name and a version (tag), and only pull from git if we're trying to use a tag that's not available locally.checkout_main_or_masterto make a generic version of the diabolical logic we're using to handle different primary branch names.This PR also continues a gradual wafting towards lowercase names for local variables (keeping e.g.
ABRA_DIRcapitalised, but making e.g.$versionlowercase)... recipe .. releasesubcommand da77b63b7crecipe .. release2772eba601recipe .. releaseaf6e0920f2recipe .. releasedocs 1ffec9aec77279b54f51toa26a0d27d7