mist_org_networktemplate remote_syslog file archive not optional

[Walter-Smet-at-delen]

Describe the bug

the archive attribute is optional, however a tf apply fails when leaving it out.

To Reproduce

see data from json below

Data imported into terraform configuration

  "remote_syslog": {
    "enabled": true,
    "time_format": "year millisecond",
    "archive": {
      "files": 5,
      "size": "4m"
    },
    "files": [
      {
        "file": "messages",
        "match": "",
        "explicit_priority": false,
        "structured_data": false,
        "contents": [
          {
            "facility": "any",
            "severity": "notice"
          },
          {
            "facility": "authorization",
            "severity": "any"
          }
        ]
      },
      {
        "file": "interactive-commands",
        "match": "",
        "archive": {},  //empty object fixes tf apply
        "explicit_priority": false,
        "structured_data": false,
        "contents": [
          {
            "facility": "interactive-commands",
            "severity": "any"
          }
        ]
      }
    ],

Expected behavior

file messages should not fail when archive is missing, while adding an empty object renders file interactive-commands fine...

Error Message

mist_org_networktemplate.RemoteSite_TF_v002: Modifying... [id=a50ff425-95a7-46a7-8b97-a8994ea30a4a]
╷
│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to mist_org_networktemplate.RemoteSite_TF_v002, provider "provider[\"registry.terraform.io/juniper/mist\"]" produced an unexpected new value:
│ .remote_syslog.files[0].archive: was null, but now cty.ObjectVal(map[string]cty.Value{"files":cty.NullVal(cty.Number), "size":cty.NullVal(cty.String)}).
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

[tmunzer]

Hi @Walter-Smet-at-delen,

Version v0.2.21 has been published. Can you test it and validate it is fixing your issue?

Thanks