Sorry, something went wrong.
|
Please expand on the How was this tested
Manually
What were the commands and their output and how it was verified. I always discourage saying "manually" without explanation in testing done. It's good idea to verify it works well with a few commands . E.g vdk list, vdk create, vdk depoy, vdk version |
Sorry, something went wrong.
Why?
Configuring the logs in the vdk_initialize hook causes commands like vdk server and vdk info to have the same verbose logging format as data job logs.
What?
Put the log configuration for vdk_initialize behind a config option and disable it by default for local runs and enable it by default for cloud runs. Configuring the logging format in vdk_initialize might still be useful for cloud runs and we don't care about other vdk commands output in cloud environments
Move config classes and functions into separate file
How was this tested
CI/CD
What kind of change is this?
Bugfix