feat: Mock capability for taps #2874
ReubenFrankel
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
Hey @ReubenFrankel 👋
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Feature scope
Taps (catalog, state, tests, etc.)
Description
Do you see value in adding a mock data capability to SDK taps? In the spirit of #1009 and MeltanoLabs/Singer-Most-Wanted#90 (comment), the idea would be to generate mock records for each stream based on their schemas (JSON Schema property
type
,format
,enum
, etc) using Faker - possibly reusing/refactoring the current stream maps implementation. This is obviously already possible with stream maps today, but would require stubbing out each stream property individually - the aim is to streamline this process; reduce the amount of necessary config and assume sensible mock values. Another benefit would be for taps with statically defined schemas that would be able to run without any config or connection to the source as a result, allowing for quick onboarding/prototyping. This would also work for taps that perform dynamic discovery, although config would still be required (in most cases).Spec
MOCK
(or similar) capability, which exposes some SDK-native settingsseed
andlocale
configurable withfaker_config
(as with stream maps)Considerations
type
/format
is fairly straightforward - it may be possible to resolve a more accurate provider in a more granular context when taking the property name into account (this would be more of a "best guess", however)meltano config <tap> test
withmock_enabled: true
, as this may otherwise indicate a false-positiveBeta Was this translation helpful? Give feedback.
All reactions