3 ms·

> We price Fix ;-) but, in seriousness > Currently, Fix Inventory can collect AWS, Google Cloud, DigitalOcean, VMWare Vsphere, OneLogin, and Slack resources

> We price Fix ;-) but, in seriousness > Currently, Fix Inventory can collect AWS, Google Cloud, DigitalOcean, VMWare Vsphere, OneLogin, and Slack resources That's kind of a weird mix of control planes, and it seems that Azure is actually present, just just not listed in the readme: https://github.com/someengineering/fixinventory/tree/4.0.1/plugins/azure#fix-plugin-azure https://github.com/someengineering/fixinventory/tree/4.0.1/p... (AGPLv3 for those interested in such things)

lloesche 3y ago
We're currently working on Azure, but it's not stable enough to be listed here. > > AWS, Google Cloud, DigitalOcean, VMWare Vsphere, OneLogin, and Slack > kind of a weird mix of control planes :D agreed. Two of these things are not like the others. There are also Github, Posthog and Scarf plugins. To explain, Fix Inventory doesn't care about Cloud resources per se. It can create an inventory of whatever kind of resources. fixcore maintains a large graph of resources and makes them searchable. fixworker runs collector plugins and ships their results to the core. In theory you could build a plugin that monitors the sensors of your farm's greenhouses and run automations and reporting on them. Slack for instance is there because when you want to notify a user on Slack it makes it convenient to lookup their internal Slack ID based on e.g. their Email address. So you might do lookups like: AWS resource tag -> OneLogin User -> Email -> Slack UID.