invalid plan warning

[pnodet]

trafficstars

2024-08-05T12:00:53.321+0200 [WARN] Provider "registry.terraform.io/scaleway/scaleway" produced an invalid plan for scaleway_iam_ssh_key.public_key, but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .disabled: planned value cty.False for a non-computed attribute
2024-08-05T12:00:53.323+0200 [WARN]  Provider "registry.terraform.io/scaleway/scaleway" produced an invalid plan for scaleway_domain_record.backend_domain_record[0], but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .keep_empty_zone: planned value cty.False for a non-computed attribute
2024-08-05T12:00:53.325+0200 [WARN]  Provider "registry.terraform.io/scaleway/scaleway" produced an invalid plan for scaleway_instance_server.server, but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .enable_dynamic_ip: planned value cty.False for a non-computed attribute
      - .boot_type: planned value cty.StringVal("local") for a non-computed attribute
      - .replace_on_type_change: planned value cty.False for a non-computed attribute
      - .state: planned value cty.StringVal("started") for a non-computed attribute
      - .public_ips: attribute representing nested block must not be unknown itself; set nested attribute values to unknown instead
      - .root_volume[0].delete_on_termination: planned value cty.True for a non-computed attribute
      - .root_volume[0].boot: planned value cty.False for a non-computed attribute

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment