- Issue created by @kreynen
I understand that this is still an alpha so I'm really just trying to figure out if it's possible to extend the fields of the client POSTs or the UI is just a placeholder for future features.
I'm looking into what it would take to recreate the functionality we used to have a Python devops solution for collecting data from ~1000 D7 sites. In https://github.com/CuBoulder/express_mono/blob/dev/modules/custom/atlas/..., we would generate information about sites we could use in reports like number of nodes or specific content types, list of user emails, last login, etc. The Drupal side of this was fairly straight forward. Use a query to get a number or list and add that list to JSON response. The python service would periodically pole the sites for updates to their statistics.
We would then use that stats to do things like try to sunset inactive sites.
I understand that the Site Manager/Site/Site Audit integration uses the Site module to push values to the Site Manager instance and while I see `List of fields that client site POSTs are allowed to overwrite in this site.` in the Site Manager UI, I can't track where allowed_remote_fields is implemented or how someone would alter what's being POSTed by a site with the Site Module installed to include custom values.
I really like that the site object is customizable with just core Field functionality and maybe I'm just looking at this too soon, but if there is any documentation about this or an example, it would help me understand it this might eventually meet our needs.
Active
1.0
Documentation