Parent resource name missing in the name property of exported resources

Open

#738 opened on Jan 13, 2023 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 42/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: azure, powershell
Domain: cloud, devops, infrastructure

Research direction

Start by reproducing the AzOps pull and template-validation flow described in the issue, focusing on the four listed nested resource types. Trace the export path that builds each resource's name and verify that the parent name is included; done means the generated JSON matches the corrected example and validation succeeds.

Written by the indexing model from the issue text.

Description

bug resource-provider

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

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

Screenshots

Dominant language: PowerShell
Stars: 420
Forks: 174
Avg merge: 16d 18h
Merged PRs (30d): 1

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[AVM Module Issue]: Module Validation rules does not allow cache rules unless Premium SKU, yet cache rules are supported with non-Premium SKUs Open

Language: Terraform :globe_with_meridians: Needs: Triage :mag: Type: Bug :bug:

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

Azure/terraform-azurerm-avm-res-containerregistry-registry#230 · 1 comment · Opened Sep 22, 2026
[BUG] GkeTpuCluster queries metadata.google.internal for MEGASCALE_SLICE_ID even when TPU_SKIP_MDS_QUERY is set Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

jax-ml/jax#40854 · Opened Sep 22, 2026
fix(mcp): `permanently_delete_cloud_{source,destination,connection}` lack `workspace_id` param, unusable without a default workspace Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

airbytehq/PyAirbyte#1201 · Opened Sep 21, 2026
[BUG] Route53Resolver: CreateResolverEndpoint requires IpAddressRequests, but the AWS member is IpAddresses, so no SDK client can call it Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

floci-io/floci#4108 · Opened Sep 21, 2026
wm_gcp_parse_output underflows its heap buffer by one byte Open

level/task module/gcp type/bug

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

wazuh/wazuh#39525 · Opened Sep 21, 2026

More Cloud issues