ssh-host-fingerprints
causes unexpected diff when specifying user data for instance
#2800
Labels
bug
instance
Instance issues, bugs and feature requests
priority:highest
Bugs filled by customers, security issues
Community Note
Terraform Version
Affected Resource(s)
scaleway_instance_server
Terraform Configuration Files
Expected Behavior
terraform apply
:Apply complete! Resources: 2 added, 0 changed, 0 destroyed.
terraform apply
:No changes. Your infrastructure matches the configuration.
Actual Behavior
terraform apply
:Apply complete! Resources: 2 added, 0 changed, 0 destroyed.
terraform apply
:Terraform will perform the following actions: # scaleway_instance_server.example will be updated in-place ~ resource "scaleway_instance_server" "example" { id = "fr-par-1/8ddc7dda-5900-4888-88e7-45954858df23" name = "example" ~ user_data = { - "ssh-host-fingerprints" = <<-EOT 256 SHA256:Ar8UZbObn5a50JNVFRv9a3+UTaikTsuDRhhcwmhYGiU root@example (ED25519) 256 SHA256:2wt5gLFSgsfaBVPPjPa4oJKjeC08xXEDt3Dg1Gg3IxY root@example (ECDSA) 3072 SHA256:Aczmai9uDBZtZAISLOL1pKjCi+Uduf++18dqoriHEHg root@example (RSA) EOT -> null # (1 unchanged element hidden) } # (17 unchanged attributes hidden) # (2 unchanged blocks hidden) } Plan: 0 to add, 1 to change, 0 to destroy.
Steps to Reproduce
terraform apply
terraform apply
Important Factoids
Not exactly sure what it takes to reproduce. The diff doesn't always happen and it seems that having a public IP and waiting a few minutes for the instance to boot between 1st and 2nd apply is required.
The text was updated successfully, but these errors were encountered: