We are currently using the Cloud Foundation Fabric Apigee module to manage our Apigee organizations via Terraform. Our existing setup uses the billing type PAYG, and we plan to migrate to the SUBSCRIPTION model as per our new commercial agreement.
While reviewing the Terraform plan, we noticed that changing billing_type from PAYG to SUBSCRIPTION appears to trigger a force replacement of the Apigee organization (org_id) and environments (env_id).
Is this behavior expected because the subscription has not yet been assigned to the Apigee project.
Once the subscription is attached on the backend, will Terraform still plan a force replacement, or will it allow an in-place update without impacting org_id and env_id?