CDR: provider trying to force replace orgs in update runs in case purge_delete is enabled about terraform-provider-hsdp HOT 5 OPEN

@akodhawan the plan suggests a change in the fhir_store URL in the data source, which in turn caused a change in the endpooint argument of the resources which forces a replacement, which is expected behaviour. Can you confirm no changes were made to the hsdp_cdr_fhir_store data source?

from terraform-provider-hsdp.

@loafoe yup & that is the part which is strange as fhir_store has not changed (same base url & same iam org id)

from terraform-provider-hsdp.

@akodhawan after our discussion it is clear where this diff is coming from. The ForceNew fields is not desired as it will almost never be the correct change. I'm adding a customDiff function which will error out as a start. There is one possible caveat in that the Terraform documentation states that known after apply values are not supported there which is exactly what is happening in your case. We may need to introduce actual resources for instances but I was reserving these for the days when we are actually able to provision such service via Terraform. This use case might force us to adopt full resources ahead of schedule.

from terraform-provider-hsdp.

@loafoe agree on adding fhir_store resource but that needs more detailing / investigation.
Proposal for now:
Short Term: advice based on doc to implement fhir_store based on pattern - base url / cdr org or chain it from resource (rather from data source)
Long Term: add fhir_store resource

from terraform-provider-hsdp.