[Monitoring] Fix UI error when alerting is not available

[chrisronline]

Resolves #77130

We actually fixed part of this problem in #71846 but it didn't catch all locations. The scenario is on the cluster listing page, when SSL is not enabled or there is a missing encryption key in the config file. This is hard to simulate in dev because the encryption key is automatically set in dev mode.

To test, you need to either create a dist build, or change the above code to not default in dev mode:

diff --git a/x-pack/plugins/encrypted_saved_objects/server/config.ts b/x-pack/plugins/encrypted_saved_objects/server/config.ts
index 9c751a9c67f..5b33c6b80cb 100644
--- a/x-pack/plugins/encrypted_saved_objects/server/config.ts
+++ b/x-pack/plugins/encrypted_saved_objects/server/config.ts
@@ -11,12 +11,12 @@ import { PluginInitializerContext } from 'src/core/server';
 
 export const ConfigSchema = schema.object({
   enabled: schema.boolean({ defaultValue: true }),
-  encryptionKey: schema.conditional(
-    schema.contextRef('dist'),
-    true,
-    schema.maybe(schema.string({ minLength: 32 })),
-    schema.string({ minLength: 32, defaultValue: 'a'.repeat(32) })
-  ),
+  encryptionKey: schema.maybe(schema.string({ minLength: 32 })),
+  //   schema.contextRef('dist'),
+  //   true,
+  //   schema.maybe(schema.string({ minLength: 32 })),
+  //   schema.string({ minLength: 32, defaultValue: 'a'.repeat(32) })
+  // ),
 });

Unfortunately, I don't know of a way to add an automated test around this.

[elasticmachine]

Pinging @elastic/stack-monitoring (Team:Monitoring)

[igoristic]

Looks good 👍

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: e7b11f7

Build metrics

✅ unchanged

History

• 💔 Build #73798 failed fd0312f
• 💔 Build #73718 failed 6a415b2

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[chrisronline]

Backport

7.x: d0147b1
7.9: 0e12028