You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently user is allowed to distribute pipeline configuration bodies across multiple YAML files and Data Prepper will merge them together before converting into internal PipelineDataflowModel. This will require any shared pipeline configuration to be applied to all pipeline config files even if it is only defined in one of those files. Thus blurring the usage of pipeline config file versus data prepper config file which is supposed to include global settings.
Describe the solution you'd like
Instead of merging the pipeline config body from files together, we should first parse each file into its own PipelineDataflowModel and then merge them into a single PipelineDataflowModel.
Describe alternatives you've considered (Optional)
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently user is allowed to distribute pipeline configuration bodies across multiple YAML files and Data Prepper will merge them together before converting into internal PipelineDataflowModel. This will require any shared pipeline configuration to be applied to all pipeline config files even if it is only defined in one of those files. Thus blurring the usage of pipeline config file versus data prepper config file which is supposed to include global settings.
Describe the solution you'd like
Instead of merging the pipeline config body from files together, we should first parse each file into its own PipelineDataflowModel and then merge them into a single PipelineDataflowModel.
Describe alternatives you've considered (Optional)
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: