Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need better data provider for source/destination meta #126

Open
terence1988 opened this issue Jun 25, 2024 · 0 comments
Open

Need better data provider for source/destination meta #126

terence1988 opened this issue Jun 25, 2024 · 0 comments

Comments

@terence1988
Copy link

Is your feature request related to a problem? Please describe.
As of now, both source meta and destination meta requires Segment's internal id, because these data providers are supposed to provide those Segment's internal ids, as well as other related metadata. As a workaround, I have to user other tools to call Segment Public API to list the needed data, then hard-code them in my script.

Describe the solution you'd like
It seems filter by name could potentially be a better approach for these data providers, then the other parts of my script can reference the value it returns.

Describe alternatives you've considered
These data providers can also list all possible values, then the other parts of my script can always reference to part of the value it returns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant