toolshed/abra
4
2
Fork 18
Code Issues 37 Pull Requests 6 Packages Releases 40 Activity

abra app undeploy fails to fetch recipe #573

New Issue
Open
opened 2025-06-09 10:00:00 +00:00 by decentral1se · 1 comment
decentral1se commented 2025-06-09 10:00:00 +00:00
Owner
Copy Link

(Regression from the large refactor last release...)

$ abra app undeploy vault.foo.com
FATA stat /home/d/.abra/recipes/vaultwarden/compose.yml: no such file or directory
(Regression from the large refactor last release...) ``` $ abra app undeploy vault.foo.com FATA stat /home/d/.abra/recipes/vaultwarden/compose.yml: no such file or directory ```
decentral1se added the
bug
 label 2025-06-09 10:00:00 +00:00
decentral1se self-assigned this 2025-07-08 09:59:13 +00:00
decentral1se added the
red abya yala
 label 2025-07-08 10:02:24 +00:00
decentral1se added this to the Abra "next" project 2025-07-08 10:06:51 +00:00
decentral1se moved this to In Progress in Abra "next" on 2025-08-13 09:45:15 +00:00
decentral1se commented 2025-08-13 09:59:03 +00:00
Author
Owner
Copy Link

Oh dear, this one is also a bit of a rabbit hole!

This is a result of toolshed/organising#628. Contrary to what we thought then, yes, abra app undeploy does need to access the check-out (and have it present on the local FS) because it needs to know the TIMEOUT value.

@simon how do you feel about --chaos/-C being added to abra app undeploy? The proposed code change is here: #595 Would this disrupt your workflow?

I guess this might be a slight annoyance for those not expecting it in the next release of abra but passing -C is so ingrained now, I hope it will be obvious how to proceed when people run into the issue?

Oh dear, this one is also a bit of a rabbit hole! This is a result of https://git.coopcloud.tech/toolshed/organising/issues/628. Contrary to what we thought then, yes, `abra app undeploy` does need to access the check-out (and have it present on the local FS) because it needs to know the `TIMEOUT` value. @simon how do you feel about `--chaos/-C` being added to `abra app undeploy`? The proposed code change is here: https://git.coopcloud.tech/toolshed/abra/pulls/595 Would this disrupt your workflow? I guess this might be a slight annoyance for those not expecting it in the next release of `abra` but passing `-C` is so ingrained now, I hope it will be obvious how to proceed when people run into the issue?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
build
go build related issues
ci/cd
Building things with CI/CD
contributing
Dealing with contributing
critical fix
https://docs.coopcloud.tech/federation/resolutions/passed/010/
design
UI/UX
documentation
Documenting all the things
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
meta
relating to the project or repo itself
question
More information is needed
red abya yala
Work funded by Calyx institute for Red Abya Yala
release
Release management
release-candidate
Related to the new release candidate
security
Security related
test
Unit/integration testing
wontfix
This won't be fixed
No Label
bug
red abya yala
Milestone
No items
No Milestone
Projects
Clear projects
No project Abra "next"
Assignees
Clear assignees
3wordchant abra-bot ammaratef45 Apfelwurm carla cas coopcloud decentral1se fauno jmakdah2 kawaiipunk knoflook lambdabundesverband moritz p4u1 ripclap simon sixsmith trav val yksflip
No Assignees decentral1se
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/abra#573
No description provided.
Delete Branch "%!s()"

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?