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

Receiving alerts: plugins or glue-services? #44

Closed
hmpf opened this issue Jun 10, 2020 · 2 comments
Closed

Receiving alerts: plugins or glue-services? #44

hmpf opened this issue Jun 10, 2020 · 2 comments
Labels
discussion Requires developer feedback/discussion before implementation

Comments

@hmpf
Copy link
Contributor

hmpf commented Jun 10, 2020

Should the backend have a mapper (in plugins) from a sender to native format, or should the sender send native format, or should there be a glue service that translates from sender's format to the backend's native format?

@lunkwill42
Copy link
Member

As discussed yesterday, I think we should move as much of the service-specific logic into glue services. Most alert sources will need some glue service to dispatch their alerts into AAS, and it would be easier for third parties to maintain their own code in that way, rather than attempting to get more plugin code into the AAS codebase.

@hmpf hmpf added the discussion Requires developer feedback/discussion before implementation label Jun 17, 2020
@hmpf
Copy link
Contributor Author

hmpf commented Sep 15, 2020

Closing, glue-service for NAV nearing completion. Documenting how to make a glue-service is not in scope for this issue.

@hmpf hmpf closed this as completed Sep 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Requires developer feedback/discussion before implementation
Projects
None yet
Development

No branches or pull requests

2 participants