Lack of Rollback on Failures

[EmAchieng]

Description: If resource creation fails midway, the script does not roll back previously created resources, potentially leading to orphaned resources.

Possible Fix: Implement rollback functionality to delete resources if any part of the creation process fails.

[EmAchieng]

Recent update addresses the issue of orphaned resources by introducing a rollback mechanism. If resource creation fails at any stage, the script now attempts to delete previously created resources, ensuring no orphaned resources remain. This significantly improves the reliability of the resource creation process and avoids unnecessary costs associated with leftover resources.

Key Changes

• Rollback on Failure: Added logic to track and delete previously created resources when an error occurs during the creation process.
• Enhanced Logging: Error handling and detailed logging ensure visibility into which resources were cleaned up after failure.
• Modular Structure: Resources like VMs, VNets, and NSGs are each rolled back if creation fails, making the process flexible and easy to maintain.

The changes ensures that failures in the middle of resource creation no longer leave behind orphaned resources, improving overall robustness and cost management.