You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Good day! I use your module to automate the configuration of my Mikrotik. There was a need to configure the following paths in the configuration:
/system logging; /system logging action
ISSUE TYPE
Feature Idea
COMPONENT NAME
community.routeros.api_modify module – Modify data at paths with API
ADDITIONAL INFORMATION
Here is an example of the command I need to execute on my Mikrotik:
/system logging action add email-start-tls=yes email-to={{ smtp_mail_to_addr }} name={{ smtp_logging_action_name }} target=email
/system logging add action={{ smtp_logging_action_name }} topics=critical
/system logging add action={{ smtp_logging_action_name }} topics=error
/system logging add action={{ smtp_logging_action_name }} topics=warning
I'm sorry if there are errors in the text!
The text was updated successfully, but these errors were encountered:
@izzzhoga all the new changes are in the latest release (2.4.0) from yesterday, so you can try them out without having to install this collection from source or something like that.
SUMMARY
Good day! I use your module to automate the configuration of my Mikrotik. There was a need to configure the following paths in the configuration:
/system logging; /system logging action
ISSUE TYPE
COMPONENT NAME
community.routeros.api_modify module – Modify data at paths with API
ADDITIONAL INFORMATION
Here is an example of the command I need to execute on my Mikrotik:
/system logging action add email-start-tls=yes email-to={{ smtp_mail_to_addr }} name={{ smtp_logging_action_name }} target=email
/system logging add action={{ smtp_logging_action_name }} topics=critical
/system logging add action={{ smtp_logging_action_name }} topics=error
/system logging add action={{ smtp_logging_action_name }} topics=warning
I'm sorry if there are errors in the text!
The text was updated successfully, but these errors were encountered: