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.
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
filterby 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.