I hope I'm not asking for too much, but, I'm curious on thoughts - I'm seeing loads of different people asking for support with "x", and whilst I think a lot of these are neat and would love to see them, only very few integrations are actually really complex and need more work than defining authentication, an endpoint of objects and then mapping - I can't help but feel there is an opportunity to make integrations a lot more generic in nature.
What I'm thinking is basically under integrations, simply having a generic "Rest API" or similar option that allows you to create a new integration definition.
Once created, have the ability to configure authentication (User/Pass, Oauth, etc.) and then the ability to "Define asset to endpoint link" or similar.
The best part is that there should be some sort of parser/transformation definitions.
So, in the case of the Unifi suggestion on another thread, you could target the endpoint that lists devices, run some sort of parser on the result for "If type=AP" create asset under AP (linking MAC as the key), "if type=router" create asset under router… and so on.
It would be great if we can then map either to a section (like how O365/CWM info goes to an asset) or the ability to update fields on an asset directly.
As I think I covered in another idea, I would also love for the ability for integrations to basically be able to set revision checkpoints upon changes so that the old values are logged and you can go back to points in time.
And most importantly, the ability to share these integrations with other users.
Whilst there are so many features that will always need to be built and made by the Hudu team, if there are certain integrations or features that can be community supported, that surely can only be a good thing!