deploy/upgrade/rollback version arguments can be git hash #517

New Issue

moritz · 2023-10-19T12:30:02Z

moritz commented

2023-10-19 12:30:02 +00:00

It would be nice if it's possible to specify a commit hash as version parameter of the commands abra app deploy/upgrade/rollback <app_name> [version], instead of checking out the hash using git and than setting the -C flag.

It would be nice if it's possible to specify a commit hash as `version` parameter of the commands `abra app deploy/upgrade/rollback <app_name> [version]`, instead of checking out the hash using git and than setting the `-C` flag.

👍 2

moritz added the

enhancement

label 2023-10-19 12:30:02 +00:00

decentral1se commented

2023-10-19 13:33:18 +00:00

Oh nice yeh, I guess that we then warn to say "this implies --chaos, doing as instructed"?

I don't imagine we want to have to pass --chaos explicitly here as well?

Oh nice yeh, I guess that we then warn to say "this implies --chaos, doing as instructed"? I don't imagine we want to have to pass `--chaos` explicitly here as well?

moritz commented

2023-10-19 13:36:05 +00:00

I think passing a hash need to be enough to know that it won't deploy a stable release version. But printing an extra warning would be nice as well.

👍 1

decentral1se added the

abra

label 2023-10-20 09:10:32 +00:00

moritz referenced this issue

2023-11-30 15:51:10 +00:00

Specify a different git location for a recipe #533

~~decentral1se referenced this issue 2024-03-27 06:24:01 +00:00~~

New abra release planning #583