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
Attributes that are implemented as metadata of any flow like disabled, namespace , labels should be directly available at the Terraform resource level instead of YAML, might even be good to have for inputs and variables.
When using Terraform it means you likely want to modularize and control config of each flow / module (modifié).
When creating TF module currently, you then need to template all these metadata in YAML (disabled, description, labels) where it should be native.
Putting everything in the YAML limits any logic proper to terraform where you can reuse inputs as outputs easily...
Currently the logic is kind of mixed : metadata (namespace, id) in resource and the rest in YAML.
The text was updated successfully, but these errors were encountered:
aballiet
changed the title
Allow user to specify all flow metadata with TF resource instead of YAML
Allow to specify all flow metadata with TF resource instead of YAML
Jul 5, 2024
Feature description
Attributes that are implemented as metadata of any flow like
disabled
,namespace
,labels
should be directly available at the Terraform resource level instead of YAML, might even be good to have forinputs
andvariables
.namespace
,id
) in resource and the rest in YAML.The text was updated successfully, but these errors were encountered: