Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ip/route: dst_address should not be mandatory #184

Closed
n0rad opened this issue Apr 22, 2023 · 5 comments · Fixed by #185
Closed

ip/route: dst_address should not be mandatory #184

n0rad opened this issue Apr 22, 2023 · 5 comments · Fixed by #185
Assignees
Labels
bug Something isn't working released

Comments

@n0rad
Copy link

n0rad commented Apr 22, 2023

Currently routeros_ip_route requires dst_address to be set, but in some cases, routes must be set without it like for example in multi ISP failover scenario.

It should not be a mandatory field.

╷
│ Error: Missing required argument
│
│   on ip_route.tf line 135, in resource "routeros_ip_route" "d2_rmark_isp22":
│  135: resource "routeros_ip_route" "d2_rmark_isp22" {
│
│ The argument "dst_address" is required, but no definition was found.
╵
@n0rad n0rad added the bug Something isn't working label Apr 22, 2023
@vaerh
Copy link
Collaborator

vaerh commented Apr 22, 2023

Please publish the configuration of your resource.

@n0rad
Copy link
Author

n0rad commented Apr 22, 2023

resource "routeros_ip_route" "d2_rmark_isp22" {
  distance    = 2
  gateway     = "10.10.10.1"
  routing_table = "to_isp22"
  target_scope = 12
}

following mikrotik documentation at: https://help.mikrotik.com/docs/pages/viewpage.action?pageId=26476608

@vaerh
Copy link
Collaborator

vaerh commented Apr 22, 2023

The problem is fixed, but I want to warn you: the "dst_address" field will still be set to "0.0.0.0/0".

@gfenn-newbury
Copy link
Collaborator

🎉 This issue has been resolved in version 1.3.6 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@n0rad
Copy link
Author

n0rad commented Apr 23, 2023

Thx, you are awesome, I see that mikrotik keep it blank when not set through UI, but I suppose it's equal to 0.0.0.0/0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants