`azurerm_site_recovery_replicated_vm`: exported resource format mismatch
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- azure, go, terraform
- Domain
- devops, infrastructure, tooling
Research direction
Start with the linked terraform-provider-azurerm issue and the azurerm_site_recovery_replicated_vm export entry point. Compare the exported managed_disk collection with the two Terraform formats shown; done means the generated configuration uses block syntax and azurerm plan succeeds.
Written by the indexing model from the issue text.
Description
link: https://github.com/hashicorp/terraform-provider-azurerm/issues/23159
managed_disk is exported in this format:
managed_disk = [{
# details removed
}]
which caused azurerm failed on plan
it works with this format:
managed_disk {
# details removed
}
- Dominant language
- Go
- Stars
- 1.9k
- Forks
- 220
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 5
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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.
More from Azure/aztfexport
-
question
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Azure/aztfexport#676 · 1 comment ·
-
question
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/aztfexport#663 · 3 comments ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Azure/aztfexport#652 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Azure/aztfexport#649 · 1 reaction ·
-
upstream-provider
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Azure/aztfexport#637 · 1 comment · 1 reaction ·
All issues in Azure/aztfexport
Similar issues
-
bug go
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
genkit-ai/genkit#6761 · 1 comment ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 2 days
-
ready
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
kubeflow/pipelines#14784 · 1 comment ·
Maintainers usually reply within 2 days
-
bug frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
trust: update-propagation-directive requires developer mode while add and remove do notPossibly taken @bhuvan-somisetty claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days