---
schema_version: "1"
id: 4fa868584e1b0da1d28466424d0f2b43c171b7f6dc5359f449c939ed459ed776
title: MuleSoft Terraform Provider Release Notes
collection: mulesoft
version: current
locale: ja-jp
portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/terraform/terraform-release-notes.md
canonical_url: https://docs.mulesoft.com/jp/release-notes/terraform/terraform-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: f6bae13ad2929ea03d10b3f6c7bbccd2755fdb5d971acc0b462f217c60c43b60
description: MuleSoft Documentation Site
latest: true
---
# 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.

## [](#v1-0-14)1.0.14

**June 22, 2026**

### What’s New

- 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`.

## [](#v1-0-13)1.0.13

**June 16, 2026**

### What’s New

- 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.

### Fixed Issues

<table class="tableblock frame-all grid-all stretch">
<colgroup>
<col style="width: 66.6666%;">
<col style="width: 33.3334%;">
</colgroup>
<thead>
<tr>
<th class="tableblock halign-left valign-top">Issue Resolution</th>
<th class="tableblock halign-left valign-top">ID</th>
</tr>
</thead>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Routes in <code>anypoint_api_instance</code> can now be added, inserted, and reordered correctly.</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>W-22924093</p>
</div></div></td>
</tr>
</tbody>
</table>

## [](#v1-0-12)1.0.12

**June 10, 2026**

### Fixed Issues

<table class="tableblock frame-all grid-all stretch">
<colgroup>
<col style="width: 66.6666%;">
<col style="width: 33.3334%;">
</colgroup>
<thead>
<tr>
<th class="tableblock halign-left valign-top">Issue Resolution</th>
<th class="tableblock halign-left valign-top">ID</th>
</tr>
</thead>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p><code>anypoint_privatespace_advanced_config</code> now sets the <code>id</code> and <code>organization_id attributes</code> correctly after an update, so Terraform no longer fails with a "Provider returned invalid result object after apply" error.</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>W-22363491</p>
</div></div></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>The <code>type</code> field in <code>anypoint_secret_group_tls_context</code> is now correctly read and written, resolving import and plan-diff issues for TLS contexts backed by PEM or JKS keystores.</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>W-22774371</p>
</div></div></td>
</tr>
</tbody>
</table>

## [](#v1-0-10)1.0.10

**June 08, 2026**

### Fixed Issues

<table class="tableblock frame-all grid-all stretch">
<colgroup>
<col style="width: 66.6666%;">
<col style="width: 33.3334%;">
</colgroup>
<thead>
<tr>
<th class="tableblock halign-left valign-top">Issue Resolution</th>
<th class="tableblock halign-left valign-top">ID</th>
</tr>
</thead>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Upstreams in <code>anypoint_api_instance</code> are now correctly updated when multiple upstreams are configured.</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>W-22774371</p>
</div></div></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Policy-bound pointcut configurations in <code>anypoint_api_instance</code> are now correctly applied and read back from state when using known policies.</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>W-22721413</p>
</div></div></td>
</tr>
</tbody>
</table>

## [](#v1-0-9)1.0.9

**June 05, 2026**

### What’s New

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

### Fixed Issues

<table class="tableblock frame-all grid-all stretch">
<colgroup>
<col style="width: 66.6666%;">
<col style="width: 33.3334%;">
</colgroup>
<thead>
<tr>
<th class="tableblock halign-left valign-top">Issue Resolution</th>
<th class="tableblock halign-left valign-top">ID</th>
</tr>
</thead>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p><code>anypoint_secret_group_tls_context</code> import and apply operations no longer fail due to an incorrect API endpoint.</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>W-22721411</p>
</div></div></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>The <code>associations</code> attribute in <code>anypoint_private_space_association</code> is now optional, preventing unnecessary plan diffs when the attribute is not specified.</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>W-22721405</p>
</div></div></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>The default version of the <code>message-logging-outbound</code> policy has been reverted to <code>2.0.2</code> to match the version available in Anypoint Exchange.</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>W-22721410</p>
</div></div></td>
</tr>
</tbody>
</table>

## [](#v1-0-7)1.0.7

**June 01, 2026**

### Fixed Issues

<table class="tableblock frame-all grid-all stretch">
<colgroup>
<col style="width: 66.6666%;">
<col style="width: 33.3334%;">
</colgroup>
<thead>
<tr>
<th class="tableblock halign-left valign-top">Issue Resolution</th>
<th class="tableblock halign-left valign-top">ID</th>
</tr>
</thead>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Importing API policies using <code>terraform import</code> no longer fails.</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>W-22687456</p>
</div></div></td>
</tr>
</tbody>
</table>

## [](#v1-0-5)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

<table class="tableblock frame-all grid-all stretch">
<colgroup>
<col style="width: 66.6666%;">
<col style="width: 33.3334%;">
</colgroup>
<thead>
<tr>
<th class="tableblock halign-left valign-top">Issue Resolution</th>
<th class="tableblock halign-left valign-top">ID</th>
</tr>
</thead>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Terraform state now correctly reflects both <code>associations</code> and <code>created_associations</code> after importing an <code>anypoint_private_space_association</code> resource.</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>W-22734343</p>
</div></div></td>
</tr>
</tbody>
</table>

## [](#v1-0-3)1.0.3

**May 27, 2026**

### Fixed Issues

<table class="tableblock frame-all grid-all stretch">
<colgroup>
<col style="width: 66.6666%;">
<col style="width: 33.3334%;">
</colgroup>
<thead>
<tr>
<th class="tableblock halign-left valign-top">Issue Resolution</th>
<th class="tableblock halign-left valign-top">ID</th>
</tr>
</thead>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Terraform no longer plans unnecessary changes after importing an existing <code>anypoint_api_instance</code> resource. The <code>tls_context_id</code> and <code>gateway_id</code> fields are now correctly restored during import.</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>W-22678732</p>
</div></div></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Importing <code>anypoint_private_space_config</code> and <code>anypoint_privatespace_advanced_config</code> 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.</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>W-22678732</p>
</div></div></td>
</tr>
</tbody>
</table>

## [](#v1-0-2)1.0.2

**May 25, 2026**

### Fixed Issues

<table class="tableblock frame-all grid-all stretch">
<colgroup>
<col style="width: 66.6666%;">
<col style="width: 33.3334%;">
</colgroup>
<thead>
<tr>
<th class="tableblock halign-left valign-top">Issue Resolution</th>
<th class="tableblock halign-left valign-top">ID</th>
</tr>
</thead>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Creating and updating <code>anypoint_team</code> resources no longer produces errors or leaves the resource in an inconsistent state.</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>W-22677256</p>
</div></div></td>
</tr>
</tbody>
</table>

## [](#v1-0-1)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

<table class="tableblock frame-all grid-all stretch">
<colgroup>
<col style="width: 66.6666%;">
<col style="width: 33.3334%;">
</colgroup>
<thead>
<tr>
<th class="tableblock halign-left valign-top">Issue Resolution</th>
<th class="tableblock halign-left valign-top">ID</th>
</tr>
</thead>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>A2A policy configurations are now applied correctly to ensure policies are created with the intended settings.</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>W-22574468</p>
</div></div></td>
</tr>
</tbody>
</table>

## [](#1-0-0)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](https://docs.mulesoft.com/mulesoft-terraform-provider/cloudhub2-resources).
- You can now create and manage managed Omni Gateway resources in CloudHub 2.0.  
    For more information, see [Managed Omni Gateway Resources](https://docs.mulesoft.com/mulesoft-terraform-provider/managed-gateway-resources).
- You can now manage Access Management resources, including business groups and teams.  
    For more information, see [Access Management Resources](https://docs.mulesoft.com/mulesoft-terraform-provider/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](https://docs.mulesoft.com/mulesoft-terraform-provider/secret-manager-resources).
- You can now create and manage API Manager resources, including API instances and SLA tiers.  
    For more information, see [API Manager Resources](https://docs.mulesoft.com/mulesoft-terraform-provider/api-manager-resources).
- You can now create and manage MCP servers and A2A instances.  
    For more information, see [MCP and AI Agent Resources](https://docs.mulesoft.com/mulesoft-terraform-provider/mcp-resources) and [API, MCP, and A2A Policy Resources](https://docs.mulesoft.com/mulesoft-terraform-provider/a2a-resources).
- You can now apply API, MCP, and A2A policies declaratively.  
    For more information, see [Resources](https://docs.mulesoft.com/mulesoft-terraform-provider/resources).

## [](#see-also)See Also

- [Known Issues](https://help.salesforce.com/s/issues)