MuleSoft Terraform Provider Release Notes

You can now create and manage Anypoint Connected Applications using the new anypoint_connected_app resource, including inline scope assignments.
The anypoint_connected_app_scopes resource is deprecated; migrate to the inline scopes attribute on anypoint_connected_app instead.

You can now manage role groups with inline permission and member assignments using the new anypoint_role resource.
For more information, see Access Management Resources.

The anypoint_team resource now supports inline permissions and members management. The team_name attribute is renamed to name.

New read-only data sources are now available for Access Management: anypoint_connected_app, anypoint_connected_apps, anypoint_role, anypoint_roles, anypoint_team, anypoint_teams, anypoint_users, anypoint_available_permissions, and anypoint_available_scopes.

You can now link a CloudHub 2.0 private space to an AWS Transit Gateway using the new anypoint_transit_gateway_connection resource.
New anypoint_transit_gateway_connection, anypoint_transit_gateway_connections, and anypoint_private_spaces data sources are also available.

New read-only data sources are now available for Managed Omni Gateway: anypoint_managed_omni_gateway and anypoint_managed_omni_gateways.

You can now register and manage Self-Managed Flex Gateway instances using the new anypoint_self_managed_gateway resource.
New anypoint_self_managed_gateway and anypoint_self_managed_gateways data sources are also available.
For more information, see Self-Managed Gateway Resources.

You can now publish and manage Anypoint Exchange asset versions using the new anypoint_exchange_asset resource.
New anypoint_exchange_asset and anypoint_exchange_assets data sources are also available.
Use type = "extension" and classifier = "mule-plugin" for policy and connector assets — Exchange normalizes these asset types to extension on publish.
For more information, see Exchange Resources.

You can now create and manage MCP bridges using the new anypoint_mcp_bridge resource, with new anypoint_mcp_bridge, anypoint_mcp_bridges, and anypoint_mcp_tools data sources.
The anypoint_mcp_tools data source reads a source REST API’s Exchange spec and generates the tool list automatically, so you don’t have to hand-write each tool entry.
Each source API entry supports an optional tls_context_id for HTTPS backends, and each tool supports input_schema (overrides the derived JSON Schema, advancing asset_version on update) and http_mapping (overrides how tool inputs map to the upstream request, without bumping asset_version).
The bridge also supports instance_label, approval_method, consumer_endpoint, and provider_id to align with other API Manager instance types.

You can now read anypoint_api_instance, anypoint_agent_instance, and anypoint_mcp_server by composite ID using the new by-id data sources, without filtering the full list.

New read-only data sources are now available for anypoint_connected_app_scopes, anypoint_api_policy, anypoint_api_policies, per-known-policy anypoint_api_policy_<type> variants, anypoint_api_instance_sla_tier, anypoint_api_instance_sla_tiers, anypoint_private_space_config, anypoint_privatespace_advanced_config, and anypoint_vpn_connection.
Each data source accepts the same composite ID as the corresponding resource’s import format.

The provider version constraint in all bundled examples is updated to ~> 1.0.0.

The upstream_uri shorthand attribute on anypoint_api_instance is now deprecated. Existing configurations continue to work, but the attribute will be removed in a future major version. Migrate to a routing block with a single upstream entry instead.

You can now associate a TLS context with individual upstreams in anypoint_api_instance using the new upstream_tls_context_id field.

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.

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.

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.

Known Issues