1. Homepage
  2. Release Notes

  3. MuleSoft Terraform Provider Release Notes

MuleSoft Terraform Provider Release Notes

MuleSoft Terraform Provider release notes include information about changes, new features, improvements, and resolved issues in releases of the MuleSoft Terraform Provider.

1.0.7

June 01, 2026

Fixed Issues

Issue Resolution ID

Importing API policies using terraform import no longer fails.

W-22687456

1.0.5

May 29, 2026

What’s New

  • You can now import existing anypoint_private_space_association resources using terraform plan -generate-config-out to auto-generate Terraform configuration. The associations attribute is now optional, removing the error that occurred when the attribute was not known during import.

  • You can now import anypoint_api_instance resources for root-level organizations using the <env_id>/<instance_id> format.

  • You can now import anypoint_managed_omni_gateway resources for root-level organizations using the <env_id>/<gateway_id> format.

  • You can now import anypoint_private_space_upgrade resources using the <org_id>:<space_id>:<date>:<opt_in> format.

  • You can now import anypoint_tls_context (CloudHub 2.0) resources using the <org_id>:<space_id>:<tls_id> format.

  • You can now import anypoint_vpn_connection resources using the <org_id>/<space_id>/<connection_id> format.

  • You can now import anypoint_private_space_association resources using the <org_id>/<space_id> format.

Fixed Issues

Issue Resolution ID

Terraform state now correctly reflects both associations and created_associations after importing an anypoint_private_space_association resource.

W-22734343

1.0.3

May 27, 2026

Fixed Issues

Issue Resolution ID

Terraform no longer plans unnecessary changes after importing an existing anypoint_api_instance resource. The tls_context_id and gateway_id fields are now correctly restored during import.

W-22678732

Importing anypoint_private_space_config and anypoint_privatespace_advanced_config resources for private spaces in Business Groups no longer fails with "Cannot import non-existent remote object". The provider now correctly uses the sub-org context during import.

W-22678732

1.0.2

May 25, 2026

Fixed Issues

Issue Resolution ID

Creating and updating anypoint_team resources no longer produces errors or leaves the resource in an inconsistent state.

W-22677256

1.0.1

May 22, 2026

What’s New

  • You can now import existing anypoint_api_instance and related API management resources using terraform import.

  • All major resource documentation pages now include import block examples to help you bring existing Anypoint Platform resources under Terraform management without recreating them.

Fixed Issues

Issue Resolution ID

A2A policy configurations are now applied correctly to ensure policies are created with the intended settings.

W-22574468

1.0.0

May 11, 2026

What’s New

  • MuleSoft Terraform Provider is now available, enabling you to manage MuleSoft resources declaratively using Terraform.
    The provider supports resources across CloudHub 2.0, API Manager, Access Management, Secrets Manager, MCP servers, and A2A instances.

  • You can now provision and manage CloudHub 2.0 resources, including private spaces, network configuration, ingress and egress rules, VPN connections, and TLS contexts.
    For more information, see CloudHub 2.0 Resources.

  • You can now create and manage managed Omni Gateway resources in CloudHub 2.0.
    For more information, see Managed Omni Gateway Resources.

  • You can now manage Access Management resources, including business groups and teams.
    For more information, see Access Management Resources.

  • You can now configure Secrets Manager resources, including secret groups, certificates, keystores, truststores, and shared secrets.
    For more information, see Secrets Manager Resources.

  • You can now create and manage API Manager resources, including API instances and SLA tiers.
    For more information, see API Manager Resources.

  • You can now create and manage MCP servers and A2A instances.
    For more information, see MCP and AI Agent Resources and API, MCP, and A2A Policy Resources.

  • You can now apply API, MCP, and A2A policies declaratively.
    For more information, see Resources.