Skip to content

[ARM] Fix Deployment stacks What-If not rendering the properties body on resource creates and deletes - #34156

Merged
JaysonTaiMicrosoft merged 5 commits into
Azure:devfrom
kalbert312:kylea/stacks-whatif-create-delete-rendering-fix
Oct 8, 2026
Merged

JaysonTaiMicrosoft merged 5 commits into
Azure:devfrom
kalbert312:kylea/stacks-whatif-create-delete-rendering-fix

Conversation

@kalbert312

Copy link
Copy Markdown
Member

Related command
az stack-whatif

Description
Fixes Azure/deployment-stacks#259

Testing Guide
See unit test updates.

History Notes

[ARM] az stack-whatif: Fix resource properties not rendering for resource creates and deletes


This checklist is used to make sure that common guidelines for a pull request are followed.

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

@a0x1ab

Copy link
Copy Markdown
Member

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 3 pipeline(s).

@kalbert312
Kyle Albert (kalbert312) marked this pull request as ready for review October 1, 2026 14:47
@kalbert312
Kyle Albert (kalbert312) requested a review from a team as a code owner October 1, 2026 14:47
Copilot AI balanced review requested due to automatic review settings October 1, 2026 14:47

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

Top-level configuration such as SKU, identity, and tags remains omitted, leaving the linked issue only partially resolved.

Review effort: Balanced
Findings: 1 Medium severity

Open (1)
What changed in this PR

Updates Deployment Stacks What-If formatting to display nested resource properties for creates and deletes.

Changes:

  • Renders properties from create/delete configurations.
  • Extracts reusable inline JSON formatting.
  • Updates formatter test expectations.
File Description
_stacks_formatters.py Adds create/delete property rendering.
test_stack_formatters.py Updates expected formatted output.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread src/azure-cli/azure/cli/command_modules/resource/_stacks_formatters.py Outdated
@a0x1ab

Copy link
Copy Markdown
Member

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 3 pipeline(s).

@a0x1ab

Copy link
Copy Markdown
Member

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 3 pipeline(s).

@kalbert312

Copy link
Copy Markdown
Member Author

The PR check failures at this time look unrelated to these changes.

@a0x1ab

Copy link
Copy Markdown
Member

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 3 pipeline(s).

@kalbert312

Copy link
Copy Markdown
Member Author

@Azure/act-identity-squad Ready for review

@JaysonTaiMicrosoft
JaysonTaiMicrosoft merged commit ef09fd9 into Azure:dev Oct 8, 2026
50 checks passed
@kalbert312
Kyle Albert (kalbert312) deleted the kylea/stacks-whatif-create-delete-rendering-fix branch October 8, 2026 15:41
Anthony Martin (anthony-c-martin) added a commit to Azure/bicep-deploy that referenced this pull request Oct 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stack what-if: Create entries show only management/deny status, with no property-level detail (parity with deployment what-if)

6 participants