Skip to content

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

Closed

Description

Describe the solution you'd like
When running the pull pipeline it sometimes fails on exporting a resource. The pull will try the export three times before finishing the initialize step although there are a lot more resources to export. I would like to propose a change to this behaviour.

  1. Skip the resource that can't be exported, and continue with the intialize process.
  2. Output all information about the failing resource to the logs. It is quite hard to figure out which resource is causing the issue as it is working now.
Image

Activity

  1. changed the title [-]Pull - Failed to get resource - Skip failing resource or add additional logging[/-] [+][Feature Request] Pull - Failure to get resources - Skip failing resource or add additional logging[/+] on Aug 27, 2025
  2. Jefajers commented on Sep 1, 2025

    @Jefajers
    Member

    Hi Stefan Ivemo (@StefanIvemo), thanks for reporting this.

    We have attempted to reproduce and can confirm similar outcomes. It seems that we end up with:

    Cannot validate argument on parameter 'ResourceGroupName'

    In this context of Export-AzResourceGroup when the module simply does not declare any value for the ResourceGroupName parameter (missing/empty from graph discovery). This entire state is undesired and should be mitigated regardless of retry and message verbosity.

    Action:

    • Add logic to avoid further resource processing in this part of the module of resources with no ResourceGroupName
    • Add more detailed information for the child resource catch step for easier troubleshooting.

    Let me know if anything has been misunderstood or you believe we have discrepancy with reproducibility 👂

  3. StefanIvemo commented on Sep 1, 2025

    @StefanIvemo
    CollaboratorAuthor

    Jesper Fajers (@Jefajers) Just to confirm. With the suggested action, during Pull it will just skip any resources with a missing value for ResourceGroupName and continue with the next resource?

  4. Jefajers commented on Sep 1, 2025

    @Jefajers
    Member

    @Jefajers Just to confirm. With the suggested action, during Pull it will just skip any resources with a missing value for ResourceGroupName and continue with the next resource?

    Yes exactly, when the module performs discovery of resources and child resources at RG scope 👍 this would apply.

    Any such find (a resource at rg with no rg) would not be expected and should not be processed by this particular part of the export.

  5. moved this from In progress to Pending release in AzOps on Sep 15, 2025
  6. changed the title [-][Feature Request] Pull - Failure to get resources - Skip failing resource or add additional logging[/-] [+]Pull - Failure to get resources - Skip failing resource or add additional logging[/+] on Sep 16, 2025
  7. moved this from Pending release to Done in AzOps on Sep 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugSomething isn't working

Type

Projects

  • Status
    Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions