-
-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After import command or block, unprivileged forces replacement #1406
Comments
It looks like the
But I'm not sure why the import block behaves differently:
Regardless, the import is incomplete. For example, the Import is not something that I use often, so this functionality might be half-baked. |
Thanks for your attention here, appreciate it. My current use case is to migrate most/all of my infra to TF/Tofu, previously all created manually. I was hoping for a quicker/smoother/easier transition than basically bit-by-bit building tf files. |
Describe the bug
I'm attempting to import an existing container, and no matter what is chosen for
unprivileged
, terraform insists on forcing replacement.To Reproduce
Steps to reproduce the behavior:
plan
, with-generate-config-out=
plan
runs insist thatunprivileged
forces replacement:It doesn't matter which
unprivileged
setting is made in thetf
file, I get the same result.The same thing would happen with
vm_id
until I upgraded to0.60.0
. No issues when using the provider to create a container from scratch.Container config:
Expected behavior
No container replacement.
Additional context
Add any other context about the problem here.
TF_LOG=DEBUG terraform apply
): As this outputs a lot of info (including a complete dump of inventory), would rather not post.The text was updated successfully, but these errors were encountered: