Terraform Anypoint Provider Fails to Import Upstream Configuration for Flex Gateway API Instances

CAUSE

This behavior is caused by a defect in versions of the Terraform Anypoint Provider prior to 1.0.3. These earlier versions contained a bug that prevented the correct processing and application of the upstream URL configuration when creating or updating Flex Gateway API instances. As a result, the upstream details specified in your Terraform configuration were not properly translated and applied to the Flex Gateway.

SOLUTION

To resolve this issue, upgrade your Terraform Anypoint Provider to version 1.0.3 or later. This version includes the necessary fix to correctly handle upstream configurations for Flex Gateway API instances.

1.  **Update your Terraform provider configuration**:
    Modify your `versions.tf` or provider block to specify version `1.0.3` or a later compatible version for the Anypoint Provider.

    ```terraform
    terraform {
      required_providers {
        anypoint = {
          source  = "mulesoft/anypoint"
          version = "~> 1.0.3" # Or a later compatible version
        }
      }
    }
    ```

2.  **Initialize and upgrade Terraform providers**:
    Navigate to your Terraform project directory in your terminal and run the following command to re-initialize your working directory and upgrade the provider:

    ```bash
    terraform init -upgrade
    ```

3.  **Apply your Terraform configuration**:
    After the provider has been upgraded, apply your Terraform configuration to ensure the upstream details are correctly provisioned:

    ```bash
    terraform apply
    ```

    Confirm the changes when prompted.

After these steps, the Flex Gateway API instance should correctly reflect the upstream URL as defined in your Terraform configuration.

APPLIES TO

*   Terraform Anypoint Provider versions prior to 1.0.3
*   Flex Gateway API instances