routeros_system_logging_action and default settings

[durandguru]

Describe the bug
Setting 1 of the 4 predefined logging actions will give an error about that that action already exists.

To Reproduce
resource "routeros_system_logging_action" "syslog" {
name = "remote"
target = "remote"
bsd_syslog = true
remote = var.shared_settings.syslog_server
remote_port = "514"
src_address = var.device_settings.ip
syslog_facility = "daemon"
}

Error: PUT 'https://1.1.1.1:443/rest/system/logging/action' returned response code: 400, message: 'Bad Request', details: 'failure: action already exists with such a name'
│
│ with module.terraform-module-mikrotik.routeros_system_logging_action.syslog,
│ on .terraform\modules\terraform-module-mikrotik\routeros-system-logging-action.tf line 1, in resource "routeros_system_logging_action" "syslog":
│ 1: resource "routeros_system_logging_action" "syslog" {

Expected behavior
Import works. So that is no problem. But normally in this provider you can just set settings on predefined resources. This resource can be an exception, documentation must be changed then. Or it becomes possible to set the 4 predefined resoures.

**Predefined resources:
Flags: * - default
*0 * name="memory" target=memory memory-lines=1000 memory-stop-on-full=no

*1 * name="disk" target=disk disk-file-name="log" disk-lines-per-file=1000 disk-file-count=2
disk-stop-on-full=no

*2 * name="echo" target=echo remember=yes

*3 * name="remote" target=remote remote=1.1.1.1 remote-port=514 src-address=0.0.0.0 bsd-syslog=yes
syslog-time-format=bsd-syslog syslog-facility=local0 syslog-severity=auto

[vaerh]

Yes, it turns out to be a mix of normal and system resources. It is necessary to fix the logic of interaction, but it is not quick.

[durandguru]

Take your time. Import works for me now. Especially because the id is always the same (on my devices).

[vaerh]

🎉 This issue has been resolved in version 1.58.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀