Operator Action Needed management system

[focusaurus]

The system should have a way of registering and tracking actions requiring an operator's attention. This would include things like:

• configuring key settings in the operator UI (storefront URLs, email settings, logo images, etc)
  • This is what prompted me to suggest this feature. Now that we are headless, storefront URLs are technically optional so I didn't think the system should error or warn when they are unset, but we should register they are unset if things like outgoing emails are using them but they are still unset.
  • There are other plugins that probably could use this pattern. Something needs to eventually be configured but maybe not a strict requirement to even bring up the system.
• System maintenance becoming required
  • I can't think of already-existing examples of this, but it would be something like a TLS certificate expiration approaching
  • This might be out of scope, at least for v1 of this feature

We need a mechanism to get attention on these, but often they are not immediately necessary and we want the system to function without them. That said, we want to guide the operators/admins to getting these done as appropriate.

I think we want to ensure

• Each issue is only represented once (not once each time the system noticed it was an issue)
• A way to permanently dismiss a particular alert
• System should automatically clear the alert when the underlying issue is resolved
• This should be available in the graphql API and probably also have a GUI somewhere in the operator UI
• Alerts should be rich enough to link to relevant documentation

CC: @rymorgan for input and design

[rymorgan]

💯 This is badly needed. It's something that @mikemurray and I have discussed recently. I don't think UI needs to be complicated and @cassytaylor and I have ideas of how we should handle it in the operator tools. I think this can be a stretch goal for out Catalyst UI pod.