ionos-cloud/terraform-provider-ionoscloud

primary_ip not computed anymore

arteonprifti opened this issue · 1 comments

Description

The primary_ip field is not computed anymore when creating an ionoscloud_server

Expected behavior

primary_ip not empty

Environment

Terraform version:

Terraform v1.5.3
on linux_amd64

Provider version:

6.4.7

OS:

ubuntu:22_04

Configuration Files

terraform {
  required_providers {
    ionoscloud = {
      source = "ionos-cloud/ionoscloud"
      version = "6.4.7"
    }
    random = {
      source = "hashicorp/random"
      version = "3.5.1"
    }
  }
}


resource "ionoscloud_datacenter" "example" {
    name                  = "Datacenter Example"
    location              = "de/txl"
    description           = "Datacenter Description"
    sec_auth_protection   = false
}

resource "ionoscloud_lan" "example" {
    datacenter_id         = ionoscloud_datacenter.example.id
    public                = true
    name                  = "Lan Example"
}

resource "ionoscloud_server" "example" {
    name                  = "Server Example"
    datacenter_id         = ionoscloud_datacenter.example.id
    cores                 = 1
    ram                   = 1024
    availability_zone     = "ZONE_1"
    cpu_family            = "INTEL_SKYLAKE"
    image_name            = "ubuntu:22.04"
    image_password        = random_password.server_image_password.result
    type                  = "ENTERPRISE"
    volume {
        name              = "system"
        size              = 5
        disk_type         = "HDD"
        bus               = "VIRTIO"
        availability_zone = "ZONE_1"
    }
    nic {
        lan               = ionoscloud_lan.example.id
        name              = "system"
        dhcp              = true
    }

}
resource "random_password" "server_image_password" {
  length           = 16
  special          = false
}

output "the_ip" {
  value       = ionoscloud_server.example.primary_ip
}

How to Reproduce

  1. create server with the plan
  2. check state or output

Should be fixed in latest v6.4.8