rad run shows incorrect environment name during deployment

[loekd]

Steps to reproduce

• use this application definition
• it has an explicit environment definition
• run the app using this command rad run ./app_v1.bicep --group test --application demo01

Observed behavior

This is the generated commandline output:

PS C:\Temp\radius\01-Bicep> rad run ./app_v1.bicep --group test --application demo01
Building ./app_v1.bicep...
WARNING: The following experimental Bicep features have been enabled: Extensibility, Dynamic type loading, Extension registry, Asserts. Experimental features should be enabled for testing purposes only, as there are no guarantees about the quality or stability of these features. Do not enable these settings for any production usage, or your production environment may be subject to breaking.
Deploying template './app_v1.bicep' for application 'demo01' and environment 'default' from workspace 'local'...

Deployment In Progress...

Completed            test            Applications.Core/environments
Completed            redis01         Applications.Datastores/redisCaches
Completed            demo01          Applications.Core/applications
...                  container01     Applications.Core/containers

Deployment Complete

Notice how the environment name is 'default' in the text and 'test' in the list below the text.
The app name and workspace are correct.

Desired behavior

When creating an explicit environment, its name should be displayed properly.

Workaround

It's not a blocking issue, just a cosmetic thing.

rad Version

rad version
RELEASE   VERSION   BICEP     COMMIT
0.37.0    v0.37.0   0.29.47   b1a78222b715a29fd5d76858403bec8f686b732e

Operating system

Windows 11

Additional context

No response

Would you like to support us?

• Yes, I would like to support you

AB#13047

[radius-triage-bot]

👋 @loekd Thanks for filing this bug report.

A project maintainer will review this report and get back to you soon. If you'd like immediate help troubleshooting, please visit our Discord server.

For more information on our triage process please visit our triage overview

[radius-triage-bot]

👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

[radius-triage-bot]

This issue is a great one to pickup for new contributors. It should only require small changes and not assume a deep knowledge of the Radius architecture.

We always welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview