I'd like to see some way of ignoring certain requirements results, without having to turn off requirements checking entirely. E.g. right now I've got a site where I'm running the core Aggregator module, which is deprecated. This means that that site always shows up in at least a warning state, because requirements reports a warning on a deprecated module being used (and while it's supposed to have been moved to contrib, the contrib version isn't ready for prime time yet). Day to day, I'm not really interested in that. Turning off requirements checking, however, also turns off module updates being available, which I am interested in, day to day. It's one of the reasons I have my site being monitored by Nagios in the first place. So a way of being able to say "on this site, don't consider this part of requirements checking in reporting back to Nagios" would be handy. Similarly, I've got sites still on 8.9 that of course, report an unsupported Drupal release in the status page and to Nagios. Being able to turn that off for reporting to Nagios would make monitoring that site (until it is updated) for other day to day problems easier, as it wouldn't be constantly in a critical state just from the old version of Drupal.

Note that for the first scenario, ignoring the Aggregator module does not cause the Deprecated Module Used warning to turn off. So the current module ignoring facilities does not produce the results I'm looking for.

Issue fork nagios-3295094

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

Ben Coleman created an issue. See original summary.

ben coleman’s picture

Issue summary: View changes
gogowitsch’s picture

There is an option for ignoring modules. I hope that it will help you.

I‘ll try your use case myself once I have more time.

ben coleman’s picture

Yes, I tried using the Module ignore option. Ignoring the Aggregator module does not turn off the Deprecated Modules used warning, even though Aggregator is the only deprecated module I'm using.

I haven't yet had time to look at the code myself to figure out if this will be difficult or not.

sleitner made their first commit to this issue’s fork.

sleitner’s picture

Status: Active » Needs review

Please review code for deprecated modules and themes.

sleitner’s picture

Please review code for deprecated modules and themes & experimental modules.

ben coleman’s picture

I've checked deprecated modules and experimental modules, and it looks like it works.

  • Gogowitsch committed 7ec98e4 on 8.x-1.x authored by sleitner
    Issue #3295094 by Ben Coleman,sleitner: Way to ignore certain...

gogowitsch’s picture

Status: Needs review » Fixed

Thank you, Ben and sleitner, for your inspiration, code, testing and patience.

I have merged this feature into the dev branch, to be released soon.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.