Azure Naming Tool - Release Notes v5.0.3
Overview
Version 5.0.3 is a patch release that addresses resource name generation, resource type editing, SQLite configuration updates, and .NET 10 test compatibility. It also updates the Resource Types and Resource Locations catalogs to align with current Azure naming rules and regions. This release maintains full compatibility with v5.0.0 and requires no additional migration steps.
What's New in v5.0.3
Bug Fixes
Issue #201 - Cannot generate a subscription name
- Added validation metadata for Azure subscriptions and management groups
- Added current length, character, and validation requirements so subscription and management group names can be generated successfully
Issue #204 - UI test project has not been upgraded to .NET 10
- Updated the AzureNamingTool.UiTests project to target .NET 10
- Restored compatibility between the UI test project and the main application project
Issue #205 - No Update button in the Resource Type editing window
- Fixed the Resource Type editing modal so its action buttons remain visible
- Replaced JavaScript checkbox polling with Blazor-managed state for Optional and Excluded component selections
- Preserved Optional and Excluded selections while editing resource types
Issue #208 - Global Exclude and Optional updates fail with SQLite
- Changed global Optional and Excluded component updates to save all modified resource types in a single batch
- Improved SQLite replacement transactions by persisting deletions before inserting records with retained IDs
- Prevented EF Core tracking and unique-key errors during global configuration updates
Issue #209 - Auto-Increment Resource Instance updates the wrong number
- Made Resource Instance auto-increment position-aware
- Ensured only the configured Resource Instance component is incremented when other components contain numeric values
Resource Catalog Updates
- Added 98 Azure resource types to the Resource Types catalog
- Corrected naming scopes, length limits, character rules, fixed-name values, and validation patterns using current Azure resource naming rules
- Added Denmark East, India South Central, and China East 3 to the Resource Locations catalog
Maintenance Updates
- Updated the application version to 5.0.3
- Updated Microsoft.OpenApi to version 3.9.0
- Added the SQLitePCLRaw.lib.e_sqlite3 dependency for SQLite runtime support
- Included current security and maintenance dependency updates
v5.0.0 Documentation
This patch release builds upon the major v5.0.0 release. For comprehensive documentation about the v5.0.0 features and migration guides, please refer to:
User Documentation
- v5.0.0 Release Notes - Complete feature list and breaking changes
- v5.0.0 Migration Guide - Upgrade instructions from v4.x
- v5.0.0 Azure Name Validation Guide - Azure tenant validation setup
- v5.0.0 Azure Name Validation Docker Guide - Docker deployment with validation
- Choose an Installation Option - Installation guides
Architecture Documentation
- ADR-001-application-architecture - Application design decisions
- ADR-002-hosting-architecture - Hosting platform guidance
- ADR-003-data-storage-architecture - Data storage strategy
Upgrading to v5.0.3
From v5.0.0, v5.0.1, or v5.0.2
Upgrading to v5.0.3 requires no breaking configuration changes or additional migration steps:
- Back up the existing configuration
- Stop the application
- Replace application files with v5.0.3 binaries
- Restart the application
Existing JSON and SQLite configurations will continue to work without modification. Updated default Resource Types and Resource Locations are applied only when using or restoring the repository defaults.
From v4.x
If you are upgrading from v4.x, please follow the v5.0.0 Migration Guide first, then upgrade to v5.0.3.
Known Issues
No new issues have been identified in v5.0.3. See the v5.0.0 Release Notes for existing known issues from the major release.
Support and Feedback
- Issues: Report bugs via GitHub Issues
- Discussions: Join the conversation in GitHub Discussions
- Wiki: Access documentation at GitHub Wiki
Contributors
Thank you to all contributors who helped identify, resolve, and validate these improvements!