Skip to content

Fix issues with child resource export error verbosity and processing of resource with null or empty resource group - #935

Merged
Jesper Fajers (Jefajers) merged 2 commits into
Azure:mainfrom
Jefajers:verbosity
Sep 15, 2025
Merged

Jesper Fajers (Jefajers) merged 2 commits into
Azure:mainfrom
Jefajers:verbosity

Conversation

@Jefajers

Copy link
Copy Markdown
Member

Overview/Summary

This PR addresses issue #932 by improving error messages during child resource export.

  • Added resource group export parameters to error messages to provide relevant troubleshooting insights.
  • Updated processing logic to prevent unintentional handling of resources that are not associated with a resource group during export.

This PR fixes/adds/changes/removes

  1. Changes Get-AzOpsResourceDefinition.ps1
  2. Changes Strings.psd1

Breaking Changes

  1. N/A

Testing Evidence

Utilize automated testing from GH action.

As part of this Pull Request I have

  • Checked for duplicate Pull Requests
  • Associated it with relevant issues, for tracking and closure.
  • Ensured my code/branch is up-to-date with the latest changes in the main branch
  • Performed testing and provided evidence.
  • Updated relevant and associated documentation.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@Jefajers
Jesper Fajers (Jefajers) merged commit b87cfc0 into Azure:main Sep 15, 2025
4 checks passed
@Jefajers
Jesper Fajers (Jefajers) deleted the verbosity branch September 15, 2025 08:19
@Jefajers Jesper Fajers (Jefajers) moved this from Needs review to Done in AzOps Sep 16, 2025

This branch was previously deployed

1 inactive deployment
test 02ff365e Deployed Sep 11, 2025 by Jefajers via Tests - Subscription Only #362
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Pull - Failure to get resources - Skip failing resource or add additional logging

2 participants