search

mspnp / AzureNamingTool

The Azure Naming Tool is a .NET 8 Blazor application, with a RESTful API. The UI consists of several pages to allow the configuration and generation of Azure Resource names. The API provides a programmatic interface for the functionality.
https://aka.ms/azurenamingtool
MIT License
308 stars 604 forks source link

Config Import Screen working indefinitely #28

Closed ArlanNugara closed 7 months ago

ArlanNugara commented 9 months ago

Describe the bug When we import a config a pop up shows (Global) Global Config Update Succeeded whereas the screen shows Working indefinitely and does not go back to Configuration page or Home page.

To Reproduce Steps to reproduce the behavior:

  1. Go to Configuration
  2. Click on Global Configuration under General Configuration
  3. Scroll down to Import Global Configuaration
  4. Paste the backed up json of global config
  5. Click on Import button
  6. Click on OK button on Attention pop up
  7. Click on OK button on Attention pop up again

Expected behavior A pop up showing Success / Failure in loading the global config and go back to Configuration page or home page.

Screenshots image

Installation Method As per official document here.

BryanSoltis commented 9 months ago

Hi @ArlanNugara,

Thank you for feedback! We will research this issue and include a fix in the next release.

BryanSoltis commented 8 months ago

Hi @ArlanNugara,

I have continued to research this and remembered we had a fix for this in the last update. Can you confirm what version of the tool you are running? If you go to the Admin page, it will show the current version at the top.

Thank you!

-Bryan

BryanSoltis commented 8 months ago

Closed due to inactivity

ArlanNugara commented 8 months ago

@BryanSoltis Sorry for late response. The version we are using is 3.1.0 and the issue is still persisting. Do you think upgrading to 3.1.1 will fix the issue ?

ArlanNugara commented 8 months ago

@BryanSoltis The issue persists in 3.1.0. And I have upgraded the version to 3.1.1 and the issue is still there.

image

BryanSoltis commented 8 months ago

When v3.1.0 was released I had updated the Global Configuration to handle this, so I'm a little curious as to what is causing it. I may have to see your configuration and step through the code to test it. I will create a private repo and invite you shortly for collaboration.

-Bryan

BryanSoltis commented 7 months ago

Closed due to inactivity.

ArlanNugara commented 7 months ago

@BryanSoltis Sorry, we can not share our configurations with you. However, the issue persists with / without specific configuration. And we are getting used to the issue..