Id drift detected after resource creation #547
Description
What happened?
We recently switched our provider to using the no-fork implementation for plugin framework based resources.
The resources get created just fine but in the next reconcile loop a drift is detected for the "id" field which is calling an update in the terraform provider (found while debugging here)
I reproduced the behaviour with a simple resource, that does not use async behaviour and regular config.IdentifierFromProvider configuration.
Is there any additional requirement for implementing this I am missing here? E.g. some requirement of how the schema must be structured? You can find our no-fork migration for a couple of resources in this PR.
What would you expect to happen?
Having the id field populated after creation is what I would expect, however calling a Update() in the terraform provider because of this doesn't make any sense. I would expect the drift detection to ignore this change gracefully.