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

Revisit way that tasks are triggered #107

Closed
helrond opened this issue Feb 9, 2020 · 0 comments · Fixed by #125
Closed

Revisit way that tasks are triggered #107

helrond opened this issue Feb 9, 2020 · 0 comments · Fixed by #125
Labels
Milestone

Comments

@helrond
Copy link
Member

helrond commented Feb 9, 2020

Is your feature request related to a problem? Please describe.

In our current implementation, tasks can be triggered by configuring a callback request or by passing a post_service_url parameter. This is confusing for implementers and also artificially limits the number of services that can be triggered.

Describe the solution you'd like

  • Exclusively use callbacks as a way to trigger services. This will require some refactoring of existing services to rework those that use the POST request method.
  • Change model relationships to allow the designation of more than one callback service.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant