DLRS should be able to use a named credential instead of borrowing a session id and managing a Remote Site Setting #1565
Description
Is your feature request related to a problem? Please describe.
DLRS uses a Remote Site Setting and a VF session id to communicate with the Metadata API for trigger management and some metadata actions. This is good because it reduces the setup burden but has some security negativity as well as some org configurations prevent this from working.
Salesforce is actively securing things like this and making it harder for app's to use UI sessions to interact with the API.
Describe the solution you'd like
It would be nice if we could add an escape hatch that let the user configure DLRS to access the metadata api using a named credential instead. This would enable users with stronger security preferences to setup their org connections differently and if they have some of those heavier security controls then this app will be able to still function after the Named Credential is configured.
Describe alternatives you've considered
DLRS is actively working to make rollup management better and use the built-in APIs where possible (not delete). The new LWC wizard has implemented that and I think we're seeing success. I don't think this is going to work for code units like triggers and apex. Those require deployments and Salesforce hasn't and may not in the near future give us a way to do this using native APIs.