abra app undeploy fails to fetch recipe
#573
No Assignees
decentral1se
decentral1se
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/abra#573
Reference in New Issue
Block a user
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?
(Regression from the large refactor last release...)
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 undeploydoes need to access the check-out (and have it present on the local FS) because it needs to know theTIMEOUTvalue.@simon how do you feel about
--chaos/-Cbeing added toabra 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
abrabut passing-Cis so ingrained now, I hope it will be obvious how to proceed when people run into the issue?Hey, thanks for investigating!
I think adding the
-Cflag should be fine I guess. Do you have thoughts on this, @moritz?I was wondering whether I should be able to undeploy an app even if I don't have the recipe available, e.g. by having a fallback to the default
TIMEOUTwith a Warning or a--forceoption.But I guess thats also a generall discussion of what is or should be possible should I lose access to my recipe whysoever
Oh, wait a second! I can just ensure the recipe is present but not update it / check if there are changes 😌 We don't need to add a
-Cflag. It seems the timeouts are becoming a bit of a controversial aspect of our (un)deployment strategy 🙃 See #596. Moving on 🤸