-
Notifications
You must be signed in to change notification settings - Fork 50
[AVM Module Issue]: 409 Conflict on migrated VM import #240
Copy link
Copy link
Open
Labels
Language: Terraform 🌐This is related to the Terraform IaC languageThis is related to the Terraform IaC languageNeeds: Immediate Attention ‼️Immediate attention of module owner / AVM team is neededImmediate attention of module owner / AVM team is neededNeeds: Triage 🔍Maintainers need to triage stillMaintainers need to triage stillStatus: Response Overdue 🚩When an issue/PR has not been responded to for X amount of daysWhen an issue/PR has not been responded to for X amount of daysType: Bug 🐛Something isn't workingSomething isn't working
Metadata
Metadata
Assignees
Labels
Language: Terraform 🌐This is related to the Terraform IaC languageThis is related to the Terraform IaC languageNeeds: Immediate Attention ‼️Immediate attention of module owner / AVM team is neededImmediate attention of module owner / AVM team is neededNeeds: Triage 🔍Maintainers need to triage stillMaintainers need to triage stillStatus: Response Overdue 🚩When an issue/PR has not been responded to for X amount of daysWhen an issue/PR has not been responded to for X amount of daysType: Bug 🐛Something isn't workingSomething isn't working
Type
Fields
Give feedbackNo fields configured for issues without a type.
Check for previous/existing GitHub issues
Issue Type?
Bug
(Optional) Module Version
0.20.0
(Optional) Correlation Id
No response
Description
I have some VMs that were migrated to Azure from on-prem VMware. I originally had issues with importing these similar to the issue described in #230, which were resolved when I pinned the commit in #234. After that, however, I got a new error:
That was related to two items in the plan (the only changes/additions):
This only occurs one time on apply, subsequent plan/apply operations seem fine with no drift detected.
I believe the issue is that these attributes are immutable and cannot be set post-creation.