spotinst_elastigroup_aws is failing since v1.212 when using subnet_ids

[AlexeyMinasyan]

Terraform Version

Terraform v1.5.5
spotinst/spotinst v1.212.0 (self-signed, key ID D356E7D693D0F6BA)

Affected Resource(s)

spotinst_elastigroup_aws

Terraform Configuration Files

Debug Output

Panic Output

Expected Behavior

No changes expected in infrastructure

Actual Behavior

Since the recent update (v1.212.0) plan is constantly trying to remove availability_zones blocks, but these are not defined and not mentioned as required. We are using subnet_ids parameter instead

      - availability_zones {
          - availability_zones_name = "eu-central-1a" -> null
          - subnet_ids              = [
              - "subnet-123456",
            ] -> null
        }
      - availability_zones {
          - availability_zones_name = "eu-central-1c" -> null
          - subnet_ids              = [
              - "subnet-213456",
            ] -> null
        }
      - availability_zones {
          - availability_zones_name = "eu-central-1b" -> null
          - subnet_ids              = [
              - "subnet-432561",
            ] -> null
        }

And apply fails with bad request (400) error.

Steps to Reproduce

Trigger terraform plan on existing infrastructure

Important Factoids

References

Community Note

• Please vote on this issue by adding a 👍 reaction to help the community and maintainers prioritize this request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.