Azure service bus emulator destroys secret.json file when adding its own configuration

[pwrreset]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When adding the service bus emulator in an aspire project and running the project, it will add its password to the secret.json file. While doing so, it will reformat, reorder and destroy some values.

I can't really paste an example since my projects contains a lot of things I don't want to share publicly.

Expected Behavior

Adds the value at the end of the file without messing with it.

Steps To Reproduce

1-Have an aspire project that uses secret file.

2-Add these lines to the project (with the necessary references):
var serviceBus = builder.AddAzureServiceBus("messaging");
serviceBus.AddServiceBusQueue("queue");
serviceBus.AddServiceBusTopic("topic");

3-Add your own configuration to the secret.json file.

4-Run the project, the secret.json file will be rewritten, reordered and values will be changed as if it was done by some AI hallucinating.

Exceptions (if any)

No response

.NET Version info

No response

Anything else?

No response

[davidfowl]

destroy some values.

Reformat is unfortunate and inconvenient but destroy is a bug. Do you have an example?

[pwrreset]

Actually, I've lost all my commented configuration.

[pwrreset]

And it altered all the boolean config into strings and capitalized it.

[sebastienros]

I think it's not limited to service bus emulator, but any azure resource that is provisioned:

https://github.com/dotnet/aspire/blob/main/src/Aspire.Hosting.Azure/Provisioning/Provisioners/AzureProvisioner.cs#L198-L202