Incorrect configuration for `tap-fastly` validates with successful pipeline run once saved
When "Connect"ing to tap-fastly
with knowingly inaccurate configuration (API Token):
- Clicking "Test Connection" results in error response (expected)
- Clicking "Save" -> Auto run pipeline results in valid pipeline run (unexpected)
My hunch is that since tap-fastly
doesn't have transforms
, the backend validation somehow misses this. If this is the case, any extractor without transforms
would also communicate a false positive in the UI. The actual issue may have nothing to do with my hunch.
Edited by Derek Knox