Reconsidering domain polling for now #169
Labels
No Label
breaking-change
bug
CI/CD
design
documentation
duplicate
enhancement
help wanted
invalid
plugin
question
secrets
shell-completion
versioning
wontfix
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/abra#169
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?
I don't think it should be on by default now. But also, I don't think I'd even use it then because it is so flaky. Then I started to wonder if we should even have this in now at all.
Without the solid base of #165 I don't think we can do domain polling in any reliable way. For example, if we can't tell the deployment definitely succeeded then we could be polling without reason when all the containers fell down. Also, if the containers come up but they're not healthy then traefik won't route them and we're polling for no reason. And if the containers come up successfully but keep erroring out in the logs then we're polling for no reason.
Maybe domain polling should be ripped out for now or made non-default (
--no-domain-poll
becomes--domain-poll
) until we have #165 done well.I guess having a reliable domain polling setup is beta level polish.
Thoughts?
decentral1se referenced this issue from coop-cloud/organising2021-06-04 14:27:42 +00:00
Actually, was thinking, maybe just
--fast
is good enough! We could drop all the--no-*
options and then it is just a simpler CLI experience overall. I will get a PR out.