Install Config Override Warn?

[nigelgbanks]

See the conversation here for more info.

Islandora-Devops/isle-site-template#12

[adam-vessey]

Another potential candiate: Config Override Inspector

I know config_override_warn in particular indicates:

This is not intended to be used on production environments.

From bit of looking, COI may require some additional hook implementations, if we have some odd forms setup for config entities, to help it target the appropriate fields; though, with this targeting, it can actually go and disable the relevant fields/elements, to prevent users from trying to change the values.

[rosiel]

The UI from COI is much nicer.

Here's what Config Override Warn looks like: Fields aren't disabled, and you have to mentally translate the field's machine name into the field in the form.

Using COI, (after adding the important info to islandora.settings):

I'm leaning to COI, so will make a set of PRs that enable COI on all the currently overridden values.

[rosiel]

PRs created for Islandora and IIIF, and for Openseadragon.

The rest of our overrides are for matomo and search_api, which are not COI compatible.

We could create a form alter for these, but where would it be good to put it? Will a form override cause complaints if the form is not found? (My guess is no but just want to make sure).