azapi Output Values (Feature 106)
azapi_resource and azapi_update_resource now render a dedicated Output Values section
in Terraform plan reports, surfacing the Azure REST API response (output attribute) alongside
the body (input) attributes you configure. This makes it easier to review what values Azure
will return — resource IDs, connection strings, computed SKUs — without having to cross-reference
the Terraform state.
✨ Features
-
Dedicated Output Values section: Both
azapi_resourceandazapi_update_resource
now render an#### Output Valuessection after the#### Body/#### Body Changessection,
containing all values returned by the Azure REST API (outputattribute). All change actions
are covered: create, update, delete, and replace. -
Section suppression on create: When all output values will be unknown after apply (the
common case for a freshazapi_resourcecreate), the Output Values section is suppressed
entirely — no empty placeholder or notice is shown, keeping the report clean. -
Feature 034 grouping: Complex
outputsub-objects (e.g., askuobject with multiple
fields) are rendered as grouped###### \sku`` sub-sections with their own Property table,
consistent with how body attributes with sub-objects are rendered. -
Sensitivity masking: Sensitive output fields are shown as
(sensitive)— no actual values
are exposed in the report. -
Display name mapping: Azure resource IDs in output values are resolved to human-readable
names via the--principalsmapping file (e.g., a workspace ID becomes
Log Analytics Workspace 🆔 log-workspace-new in resource group 📁 rg-logs). -
Large-value folding: Output values exceeding the 200-character threshold are collapsed
into<details>blocks, consistent with body attribute handling.

