provision resources for Cloud Foundry alongside the BTP provider

[eshirke]

Could someone please provide examples of how to use the Cloud Foundry provider alongside the BTP provider in Terraform? Specifically, I'm looking for examples where:

We create a BTP Subaccount Environment Instance using the BTP provider.
We create spaces, org_users and service keys using the Cloud Foundry provider.

Examples of how to integrate both providers in a Terraform configuration would be greatly appreciated!

[lechnerc77]

In general this is always a two-step approach as the Terraform provider for Cloud Foundry requires the CF API URL endpoint as configuration:

1. Provision the Cloud Foundry environment via the Terraform Provider for SAP BTP
2. Provision the Cloud Foundry specific resources

You have different options how to achieve this:

• Option 1: Define the CF API URL as output of step 1 and transfer the information to step 2 as variable. One example using GitHub Actions to transfer the information is available here: https://github.com/btp-automation-scenarios/terraform-multistep-approval. The relevant code is starting here: https://github.com/btp-automation-scenarios/terraform-multistep-approval/blob/main/.github/workflows/project-provisioning.yml#L72
• Option 2: The configurations are in two different directories (one for SAP BTP, one for Cloud Foundry). Write the output values from the SAP BTP in a terraform.tfvars file in the Cloud Foundry directory. This will automatically be used when executing terraform apply in the CF directory. You find an example here: https://github.com/SAP-samples/btp-terraform-samples/tree/main/released/discovery_center/mission_3488. The relevant code is here: https://github.com/SAP-samples/btp-terraform-samples/blob/main/released/discovery_center/mission_3488/step1/main.tf#L131
• Option 3: This is a advanced option using a open source tool called terramate to orchestrate the execution. A sample setup is available here: https://github.com/btp-automation-scenarios/terramate-orchestrate and a blog post describing the setup is available here: https://dev.to/lechnerc77/experimenting-with-terramate-and-sap-btp-22m1

[eshirke]

@lechnerc77 thanks for the guidance, I have followed the two-step approach and able to create cloud foundry resources. however, when I want to delete the cloud foundry resources, I am getting below error. seems like when I comment out cloud foundry resources from drc.tf, the provider configuration also not getting recognized.

Error: Provider configuration not present
To work with module.gmi-global-nfe-drc-nonprod-cloudfoundry.cloudfoundry_org_users.org_user (orphan) its original provider configuration at module.gmi-global-nfe-drc-nonprod-cloudfoundry.provider["registry.terraform.io/cloudfoundry-community/cloudfoundry"] is required, but it has been removed. This occurs when a provider configuration is removed while objects created by that provider still exist in the state. Re-add the provider configuration to destroy module.gmi-global-nfe-drc-nonprod-cloudfoundry.cloudfoundry_org_users.org_user (orphan), after which you can remove the provider configuration again.

Terraform Code:

cloudfoundry module:

main.tf

provider "cloudfoundry" {
api_url = "https://api.cf.br10.hana.ondemand.com/"
}

resource "cloudfoundry_space" "cf_space" {
name = "my-space"
org = var.cloudfoundry_org_id
}

calling module

drc.tf
module "gmi-global-nfe-drc-nonprod" {
source = "./modules/subaccount"
environment = "nonprod"
business_unit = "global"
btp_service = "nfe-drc"
region = "br10"
cloudfoundry = true
subaccount_users = local.nfe-drc-subaccount-roles
entitlements = {
"nfe" = ["standard"],
"nfein-broker" = ["standard"],
}

}

module "gmi-global-nfe-drc-nonprod-cloudfoundry" {
source = "./modules/cloudfoundry"
cloudfoundry_org_id = module.gmi-global-nfe-drc-nonprod.cloudfoundry_org_id
}

[lechnerc77]

Hard to say from the code snippets what exactly goes sideways. According to the error message due to commenting some code the resource module.gmi-global-nfe-drc-nonprod-cloudfoundry.cloudfoundry_org_users.org_user that is part of the module is orphaned. In general, if you want to delete provisioned resources, you can comment the resources, but the provider configuration must be in place and be valid, as Terraform needs that to delete the resources. It seems like you want to remove the sapce and keep the org roles (if I understand the code snippets correctly) so the provider config must not be commented or the or user must also be removed from your configuration.