Changing user_account in initialization always trigger a replacement

[fuse]

Not 100% if this is a bug or a feature not yet implemented but modifying a user_account in a initialization block alway trigger a VM replacement. That’s not something I expected from the documentation.

That seems a bit weird because doing the same thing trough the UI does not trigger this replacement.

Other cloud init options doesn’t seem to be affected. I only tested DNS servers.

I’m currently using version 0.66.2. I can reproduce it for every attributes of the user_account block (ssh keys, username, password).

For instance while changing password :

      ~ initialization {
          ~ upgrade              = false -> (known after apply)
            # (7 unchanged attributes hidden)

          ~ user_account {
              + password = (sensitive value) # forces replacement
                # (2 unchanged attributes hidden)
            }

            # (2 unchanged blocks hidden)
        }

For now my only option has been to ignore changes on initialization[0].user_account.