-
Notifications
You must be signed in to change notification settings - Fork 61
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
Migrating from vaerh provider, issue with bridge #104
Comments
Can you test this solution? |
The same issue. The other resources managed in this project has no problems. |
Okay, I think I know what the problem might be, but I need to get to my workbench to describe the solution. |
Yep, I think #103 created a breaking change, but was tagged as a patch version rather than major 🤦 Sorry, that's my mistake. @durandguru for the time being, can you test with v1.0.2 instead of v1.0.3, and see if that works? @vaerh I'll leave my pull requests open in the future until we've both reviewed them. I really should have spotted this |
1.0.2 works |
Describe the bug
I used the @vaerh provider before and want to switch to this one after the merge. If I only replace the provider and run a plan. It wants to create a new bridge.
To Reproduce
Current setup in vaerh provider:
resource "routeros_bridge" "bridge" {
name = "bridge"
ingress_filtering = true
priority = "0x3000"
vlan_filtering = true
}
Switch providers and run plan
routeros_bridge.bridge will be created
}
Expected behavior
Just migrate
Additional context
The text was updated successfully, but these errors were encountered: