Revert "Do not use cached entities in code generation (#403)"#409
Conversation
This reverts commit 0af0ffc.
|
@andrewnester Put up the PR because without this change, fields incorrectly persist across multiple methods. The proper fix should therefore be different. Is there some kind of mutation of these objects happening out of band? |
|
well, that "fix" breaks the SDKs :) there's TODO still https://github.com/databricks/databricks-sdk-go/blob/main/openapi/code/service.go#L170-L173 |
pietern
left a comment
pietern
left a comment
There was a problem hiding this comment.
Note that we need this patch in order to generate the CLI commands.
|
@nfx could you point to where do we modify cached object which is required for correct generation of IntegrationId? The fact that we have different behaviour for cached and non-cached object is a bit worrisome |
3 participants
This reverts commit 0af0ffc, otherwise, we miss the path parameters in the requests and break all SDKs
