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

Bridge resource creating 400 errors #102

Closed
gfenn-newbury opened this issue Feb 15, 2023 · 1 comment
Closed

Bridge resource creating 400 errors #102

gfenn-newbury opened this issue Feb 15, 2023 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@gfenn-newbury
Copy link
Collaborator

Describe the bug
After creating a bridge interface, subsequent plans will fail due to the bridge resource creating a 400 error

To Reproduce
Create a bridge interface, then run a plan afterwards

Expected behavior
Subsequent plan completes successfully

Stack Trace

╷
│ Error: unknown error, status code: 400
│ 
│   with routeros_interface_bridge.main_bridge,
│   on main.tf line 39, in resource "routeros_interface_bridge" "main_bridge":
│   39: resource "routeros_interface_bridge" "main_bridge" {
│ 
╵
@gfenn-newbury
Copy link
Collaborator Author

Further testing suggests it's an issue with the ID of the routeros_interface_bridge resource having a space in the name. So, this works happily:

resource "routeros_interface_bridge" "main_bridge" {
  name           = "Mainbridge"
  pvid           = 1
  vlan_filtering = true
}

but this does not (creates, but throws a 400 in subsequent plans):

resource "routeros_interface_bridge" "main_bridge" {
  name           = "Main bridge"
  pvid           = 1
  vlan_filtering = true
}

gfenn-newbury added a commit that referenced this issue Feb 16, 2023
fix(#102): Change property ID for bridge
gfenn-newbury added a commit that referenced this issue Feb 16, 2023
fix(#104): Revert "fix(#102): Change property ID for bridge"
vaerh added a commit that referenced this issue Feb 16, 2023
gfenn-newbury added a commit that referenced this issue Feb 17, 2023
fix: Spaces in resource names (#102 - #104).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant