Slack log forwarder duplicate messages by replica count #7
Reference in New Issue
Block a user
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?
Each replica listens for doorlog changes in database and forwards changes to Slack. This is IMO the most sensible way, vs duplicating each statement, and calling out to Slack in multiple codebases (leading to 'where exactly did this originate from / is broken at?).
Reduced replicas to 1 for time being. Locking via built-in kube primitives seems sensible (as the service already talks to kube api).