Danny Kulchinsky

The general behavior in Terraform is that existing resource (created outside of Terraform) should be imported into the state, the error here is actually coming from F5 itself as the...

It would be easier to understand if you can share your terraform configuration for the relevant bigip resources. in general, this shouldn't happen - the nodes resource should be created...

Hi @swightkin! We are using Route Domainss in all our deployments and the current code works just fine for us (in fact I did a fix around this a while...

mmm, ok... so you should remove all the `%20` from your configuration since F5 will add these automatically. also, your node attribute in the attachment resource looks a bit strange....

Assuming that you have separate partitions for the workloads, each partition should be assigned a default Route Domain and it is used by F5 on the relevant resources based on...

Unfortunately, I don't see how that would be possible with the current code.

I suppose it would be possible to add a new resource attribute (route domain) and store it there, but that would require some testing.

RD are supported when there's one RD per partition, assigning multiple RDs in the same partition is not supported. I added the above since we needed this for our use...

Yes, that would be needed as well, but it's not enough. We need to add support for the route domain semantics in all the resources that implement it: node, virtual...

we have a similar configuration, but configuration changes can be apllied on either the active or passive node since they sync each other, it's what we do and we don't...