Right now, there's no good story for testing custom pipelines locally when they access secrets via DecodableSecret. It requires knowledge of where and how to create secret assets in the file system, is prone to leaving them behind after a test has completed, etc. There should be a way for setting up secrets on a per-test basis, automatically cleaning up all resources after completion.
Right now, there's no good story for testing custom pipelines locally when they access secrets via
DecodableSecret. It requires knowledge of where and how to create secret assets in the file system, is prone to leaving them behind after a test has completed, etc. There should be a way for setting up secrets on a per-test basis, automatically cleaning up all resources after completion.