[ResponseOps][Connectors] prevent or allow connectors with pre/post save/delete hooks from being used as pre-configured connectors?

[pmuellr]

based on PR comments:

• https://github.com/elastic/kibana/pull/189027#discussion_r1793120532
• https://github.com/elastic/kibana/pull/189027#issuecomment-2406133287

Originally this was titled "prevent connectors" without the "or allow", but I guess we're still figuring it out, and it looks like we will likely need to allow them.

If we wanted to prevent themwe should be able to - at startup - mark pre-configured connectors as disabled (or unusable, somehow), if their connectorType has pre-save/post-save/post-delete hooks. Since the hooks will never be called since the connector is never "created" or "deleted" via API.

If we want to allow them, we need to figure out:

• how the inference the connector normally creates in it's pre-save hook, actually gets created, since the create code is not called
• I could see some ways of getting the inference created, but no idea how we'd go about deleting it. I guess in theory, it would never need to be deleted, since the pre-configured can't really be deleted (unless the pre-configured connector is removed from config and then Kibana restarted.

Once we figure out which way to go, we can aim this issue down that track, or leave this as discussion and create a new one ...

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[pmuellr]

Note this was a little premature - actually an inference connector DOES need to be pre-configured - some conversation here:

https://github.com/elastic/kibana/pull/189027#issuecomment-2406133287

We can use this issue to discuss how this can happen, I'll swizzle the title and top comment ...