Make the provider declarative like the ACI provider

[alxgarder]

When working with the Cisco ACI provider it doesn't matter that the object is already there when running Terraform. The object will simply be added to the state file as-is. This, in my opinion, makes the ACI provider truly declarative – you define the desired state, and Terraform figures out how to reach that state.

Would it be possible to do the same for the FMC provider? Currently. it fails the entire terraform apply when running into an object that is already created.

Alternative it could be flag on the object, that allows Terraform to grab the current object instead of insisting on the user manually deleting and re-creating the object (or doing manual imports).

[rchrabas]

The ACI Terraform Provider's behavior closely follows the ACI API, which updates existing objects instead of throwing an error when duplicates are encountered.

On the other hand, the FMC Terraform Provider reflects the behavior of the FMC API, where trying to create an object with a duplicate name results in an error.

More likely approach to this, would be a provider-level switch to toggle between modes of operation. However, there are currently no plans to implement this feature anytime soon.