Azure / Azure/deployment-stacks

Better results dispaly for new DeploymentStackWhatIfResult cmdlets

Open
#244 1 comment 1 reaction 1 assignee Claimed by @anamikapan11 View on GitHub
Dominant language
Bicep
Stars
101
Forks
13
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
I am not fan of how the results coming from DeploymentStackWhatIfResult cmdlets are displayed. Now everything is displayed one line after another line without empty lines before the different resources. this makes it hard to read. Additionally now the full resource ID is displayed. This also makes it hard to read in CI/CD consoles like in Azure DevOps as you have to scroll horizontally to see the full value. The implementation for the regular WhatIfResult cmdlets was better from that perspective.

Image

**Describe the solution you'd like**
Either go back to implementation of WhatIfResult cmdlets or do something like:

```
= Scope: /subscriptions/{subscription id}/resourceGroups/{resource group name}
= Resource: Microsoft.Storage/storageAccounts/{account name} [2025-06-01]
= Management Status: "managed"
= Deny Status: "none"

= Scope: /subscriptions/{subscription id}/resourceGroups/{resource group name}
= Resource: Microsoft.Storage/storageAccounts/{account name}/blobServices/default/providers/Microsoft.Insights/diagnosticSettings/LogsAndMetricsToLogAnalytics [2021-05-01-preview]
= Management Status: "managed"
= Deny Status: "none"

```

- two empty lines between different resources. Better to scroll vertically than horizontally.
- Scope and resource as separate entries. Reduces scrolling for long names.

**Describe alternatives you've considered**
No alternatives currently.

**Additional context**
Add any other context or screenshots about the feature request here.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.