Getting Error: failed to start plugin manager: timeout while waiting for plugin to start

[nmische]

Describe the bug
This appears to be due to a large number of kubernetes connections that have custom resources.

Steampipe version (steampipe -v)
Steampipe v0.21.3
AWS Plugin v0.126.0
Kubernetes Plugin v0.26.0

To reproduce
Configure several (~50) kubernetes connections with custom resources.

Expected behavior
Steampipe lazily loads connections and does not time out.

Additional context
This issue started after adding additional clusters to my steampipe config. If I comment out some connections, the issue goes away.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[nmische]

I see there is a TODO to make plugin startup timeout configurable: https://github.com/turbot/steampipe/blob/main/pkg/pluginmanager_service/plugin_manager.go#L684-L685

I can maybe find time to take a stab at this. Would that be general option: https://steampipe.io/docs/reference/config-files/options#general-options?

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.