Abra fails to deploy recipes with no published versions #476
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#476
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
(EDIT: asking fedi friends if this can be moved to the critical fixes budget)
I managed to track this down to
e76ed771df
@moritz which I then later tried to tweak with0582147874
due to the number of issues people were running into re: #432. However, I realise that < 0.7.xabra
used to do this for deploying a new recipe with no released versions:But now it errors out when there are missing tags even when the version is the latest hash (fresh recipe). It used to be a
Warn
but now it is anError
... I could change this back to a warning but then I perhaps breakkadabra
😬 Do you know if you need this to definitely be an error?I have a diff that preserves the current erroring functionality and allows deploying a fresh recipe. Let me know if this works? I'm hesitant to make the change (risk of more regressions...) but we can try to do more manual testing? (automated test suite One Day ™️)
coop-cloud/abra#335
Please re-open if stuff is broke!