fix: make warehouseId optional in ServiceContext when no plugin requires it #91
+54
−11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR makes
warehouseIdoptional inServiceContextwhen no registered plugin declares it as a required resource. Previously,ServiceContext.createContext()unconditionally calledgetWarehouseId(client), which in production throws ifDATABRICKS_WAREHOUSE_IDis unset, and in dev mode fires an unnecessary API call.This change introduces a plugin resource declaration system where plugins can specify which shared resources they need (e.g.,
warehouseId). OnlyAnalyticsPluginuses the warehouse ID, so apps using onlyserver()should not require it.FEATURES
static requiredResources: ServiceContextResource[]ServiceContext.initialize()accepts a list of required resources and only resolves them when neededAppKit._createApp()collects required resources from all registered plugins before initializing contextFIXES
createApp({ plugins: [server()] })no longer fails whenDATABRICKS_WAREHOUSE_IDis missingBREAKING CHANGES
requiredResourcesis optional on plugins)Test Plan
server()plugin work withoutDATABRICKS_WAREHOUSE_IDanalytics()plugin continue to requireDATABRICKS_WAREHOUSE_ID