Details
-
Improvement
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
-
None
Description
Scenario:
Consider a pipeline targeting multiple environments. In Hop, this could be achieved by configuring Project environments specific to each of the environments and defining environment specific properties (connection strings, host names etc.) in them.
If this pipeline is to be submitted to a Flink cluster to target a specific environment, then the variable values for that environment need to be explicitly set in the Pipeline Run Configuration -> Variables section
Setting them in flink.conf.yaml won't work if the same Flink cluster is used for different environments.
Improvement:
Perhaps, the metadata export step could be extended to have an option to export the variables for a specific environment.
Attachments
Issue Links
- links to