abra app move does not support commit id from branch as version #803

New Issue

stevensting · 2026-03-24T10:18:24Z

stevensting commented

2026-03-24 10:18:24 +00:00

when trying to move an app using a commit id as a version, move aborts with the following error message:

FATA <recipe/git.go:166> unable to resolve 'dc28ebd3496dca63890d8d363f8c170a02066ae8': reference not found

minimum solution: improve error message.

But currently unclear if it only is relevant for commits from a branch or for all recipe versions referenced by commit id.
Also not clear if it shall be supported by move. From my point of view this is a relevant use case.

when trying to move an app using a commit id as a version, move aborts with the following error message: ``` FATA <recipe/git.go:166> unable to resolve 'dc28ebd3496dca63890d8d363f8c170a02066ae8': reference not found ``` minimum solution: improve error message. But currently unclear if it only is relevant for commits from a branch or for all recipe versions referenced by commit id. Also not clear if it shall be supported by move. From my point of view this is a relevant use case.

decentral1se added the

bug

label 2026-03-24 11:48:04 +00:00

decentral1se commented

2026-03-24 11:51:43 +00:00

@stevensting to be clear, what happened:

you deploy --chaos
you want to app move afterwards

However, that commit does not exist anymore (?) or app move just doesn't seem to support it? The error message looks like it tried to resolve the commit, so I'm wondering if the commit exists on your system after all?

In the case of app move'ing a deploy --chaos'd app (🙃), would you expect then to app move --chaos? If you're in a chaotic state then I am not sure you want to be moving? It's already quite a brittle operation... however, such is life? 🤷‍♀️

As far as I can tell, the implementation does guard against unstaged changes.

		cli/app/move.go
		Lines 84 to 86 in e04a1e15c4
	
						if err := app.Recipe.Ensure(internal.GetEnsureContext()); err != nil {

							log.Fatal(err)

						}

@stevensting to be clear, what happened: 1. you `deploy --chaos` 2. you want to `app move` afterwards However, that commit does not exist anymore (?) or `app move` just doesn't seem to support it? The error message looks like it tried to resolve the commit, so I'm wondering if the commit exists on your system after all? In the case of `app move`'ing a `deploy --chaos`'d app (🙃), would you expect then to `app move --chaos`? If you're in a chaotic state then I am not sure you want to be moving? It's already quite a brittle operation... however, such is life? 🤷‍♀️ As far as I can tell, the implementation does guard against unstaged changes. https://git.coopcloud.tech/toolshed/abra/src/commit/e04a1e15c4459cc7be5e91f0761c6edff33eb2c8/cli/app/move.go#L84-L86

stevensting commented

2026-03-24 12:09:22 +00:00

you deploy --chaos

you want to app move afterwards

it was more:

deploy with TYPE=nextcloud:dc28ebd3496dca63890d8d363f8c170a02066ae8
afterwards app move

However, that commit does not exist anymore (?) or app move just doesn't seem to support it? The error message looks like it tried to resolve the commit, so I'm wondering if the commit exists on your system after all?

Ok, now I checked again, and the commit probably does not exist anymore. Seems it was taken from a branch (the high performance backend one) which was deleted on merge. So no surprise it did not work.

In the case of app move'ing a deploy --chaos'd app (🙃), would you expect then to app move --chaos? If you're in a chaotic state then I am not sure you want to be moving? It's already quite a brittle operation... however, such is life? 🤷‍♀️

TBH, I would never try to move a chaos deployment. Maybe we should even state in the help for abra app move that it is not supported.

What remains is, maybe make the error message a little bit clearer.

> 1. you `deploy --chaos` > 2. you want to `app move` afterwards it was more: 1. `deploy` with `TYPE=nextcloud:dc28ebd3496dca63890d8d363f8c170a02066ae8` 2. afterwards `app move` > However, that commit does not exist anymore (?) or `app move` just doesn't seem to support it? The error message looks like it tried to resolve the commit, so I'm wondering if the commit exists on your system after all? Ok, now I checked again, and the commit probably does not exist anymore. Seems it was taken from a branch (the high performance backend one) which was deleted on merge. So no surprise it did not work. > > In the case of `app move`'ing a `deploy --chaos`'d app (🙃), would you expect then to `app move --chaos`? If you're in a chaotic state then I am not sure you want to be moving? It's already quite a brittle operation... however, such is life? 🤷‍♀️ TBH, I would never try to move a chaos deployment. Maybe we should even state in the help for `abra app move` that it is not supported. What remains is, maybe make the error message a little bit clearer.

👍 1

decentral1se added this to the Abra "next" project 2026-03-29 16:04:39 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/abra#803

	if err := app.Recipe.Ensure(internal.GetEnsureContext()); err != nil {
	log.Fatal(err)
	}

abra app move does not support commit id from branch as version #803

`abra app move` does not support commit id from branch as version #803