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

Namespace substitution variables #404

Closed
disrupted opened this issue Jan 9, 2024 · 0 comments · Fixed by #408
Closed

Namespace substitution variables #404

disrupted opened this issue Jan 9, 2024 · 0 comments · Fixed by #408
Assignees
Labels
breaking-change Indicates that this PR introduces a breaking change component/config Related to pipeline config
Milestone

Comments

@disrupted
Copy link
Member

The global configuration variables can be namespaced under the config key, such as ${config.kafka_brokers}, ${config.schema_registry.url}. Same thing could be considered for pipeline variables, e.g. ${pipeline_name}${pipeline.name}.
This would make it more uniform with the existing ${component.<key>} variables.

Furthermore, we might consider deprecating the hardcoded aliases ${output_topic_name} and ${error_topic_name} afterwards. (#383)

@disrupted disrupted added the component/config Related to pipeline config label Jan 9, 2024
@sujuka99 sujuka99 self-assigned this Jan 11, 2024
@sujuka99 sujuka99 added this to the v3.0 milestone Jan 11, 2024
@sujuka99 sujuka99 added the breaking-change Indicates that this PR introduces a breaking change label Jan 11, 2024
sujuka99 added a commit that referenced this issue Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change Indicates that this PR introduces a breaking change component/config Related to pipeline config
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants