Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement callback support #46

Open
mwvaughn opened this issue Nov 16, 2018 · 1 comment
Open

Implement callback support #46

mwvaughn opened this issue Nov 16, 2018 · 1 comment
Assignees
Labels
priority.verylow Don't even think about starting work on this proposal

Comments

@mwvaughn
Copy link

Though Abaco allows us to build event-driven systems, we can't learn information about its state without polling. This puts load on the system and introduces latency to downstream consumers in the form of minimum polling intervals (especially if they implement exponential backoff and the desired event occurs right after the last poll).

It would be advantageous if Abaco could post to callbacks when events such as the following occur.

  • actor created
  • actor updated
  • actor scaled
  • actor shared
  • actor deleted
  • execution start
  • execution end
  • execution failed
  • nonce created
  • nonce deleted

At minimum, https POST with a non-customizable payload should be supported. Support for one or more authn/authz HTTP headers would be useful. URL parameters should be allowed in callbackURLs and any user-specified ordering should be respected.

@mwvaughn mwvaughn added proposal priority.verylow Don't even think about starting work on this labels Nov 16, 2018
@mwvaughn
Copy link
Author

This is implemented for status changes but not for some of the other events.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority.verylow Don't even think about starting work on this proposal
Projects
None yet
Development

No branches or pull requests

2 participants