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

[dev.icinga.com #13211] REST API over HTTPs as data source #603

Closed
icinga-migration opened this issue Nov 16, 2016 · 3 comments
Closed

[dev.icinga.com #13211] REST API over HTTPs as data source #603

icinga-migration opened this issue Nov 16, 2016 · 3 comments

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/13211

Created by dzalewski on 2016-11-16 12:48:25 +00:00

Assignee: dzalewski
Status: Feedback
Target Version: (none)
Last Update: 2016-12-06 12:38:07 +00:00 (in Redmine)


It would be nice if data could be fetched from a source via REST API over HTTPS. Most REST APIs return back JSON so ability to parse it would be a useful.

@icinga-migration
Copy link
Author

Updated by tobiasvdk on 2016-12-01 07:42:33 +00:00

Duplicates #11565 "Add general REST API as import source".

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-12-06 12:38:07 +00:00

  • Status changed from New to Feedback
  • Assigned to set to dzalewski

@dzalewski: could you please have a look at the issue linked by Tobias and let me know your thoughts? I rejected this once as YES, REST is easy, but NO, implementing it in a generic way is not as everybody does it different. This starts with authentication, goes to data wrapping, pagination... nothing is really standardized, and everybody does it different.

I fear those zillions of bug reports once I add something similar ;-)

@Thomas-Gelf
Copy link
Contributor

No feedback, closing this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants