Parent resource name missing in the name property of exported resources

[Poekiee12]

Describe the bug
When exporting a resource through AzOps, the template validation fails because the name of the parent resource is not included in the name property.

This bug applies to the following types:

"type": "Microsoft.Network/privateDnsZones/virtualNetworkLinks",
"type": "Microsoft.Sql/servers/databases",
"type": "Microsoft.Cdn/profiles/endpoints",
"type": "Microsoft.Network/dnsResolvers/inboundEndpoints",

Wrong JSON

"type": "Microsoft.Sql/servers/databases",
"name": "databasename",

Correct JSON

"type": "Microsoft.Sql/servers/databases",
"name": "sqlservername/databasename",

Steps to reproduce

1. Pull Azure environment with AzOps
2. Validate pulled resource templates
3. Error appears in the name property of the JSON file

Screenshots

[Poekiee12]

Added multiple resource types we're facing issues with.

[daltondhcp]

Thank you for reporting this!
We are striving to support all resource providers in pull, but also rely on that the RPs return all the correct schema.
We are currently working on improving this to enable higher quality, but for now, it is best effort.

Out of curiosity, in this particular case, do you always run a validate after pull, or is this after changing the resource through a PR?

[Poekiee12]

We always run a validate after a pull! This particular case was a first pull of an environment at which the validate fails. We are currently excluding the resource types to make sure it works.

[Gizzaaa]

I got the same with 'Microsoft.Sql/managedInstances/databases'