Closed rschmied closed 4 months ago
tagging @netcicd and @tiagosil-cisco
I will see what I use when I am back next week. Have a good newyear
I extensively use elements as per your blog. Will it just be a replacement of the elements keyword with depends_on? If so I will try to test
yes... everywhere where you use an elements
list it should be possible to simply replace it with an depends_on
list. They do the same thing but depends_on
is built into TF.
Maybe I wasn't using "elements" correctly, but I thought that we could have different "cml2_lifecycle" resources to manage different nodes/links in the same lab. Let's say, we build a big topology with two datacenter but I want to control each one independently.
@tiagosil-cisco I guess you were. Are you saying that you had multiple lifecycle resources in the same TF? If so, then I think that there should be some code which would restrict the number of lifecycle resources to ONE or ZERO. Not even sure what the implications would be if there's multiple LC resources...!?
https://developer.hashicorp.com/terraform/plugin/framework/deprecations
need to implement this...
fixed by PR #130
Apparently, they are doing the same thing: creating state dependencies. At the time of creating the
elements
property, I was simply not aware ofdepends_on
which would have been the obvious choice as it does exactly the same thing, built-in.Need to investigate the ramification when declaring
elements
obsolete/deprecated and how this would impact users... I guess it would not but want to be clear upfront.