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

cloudconnexa_network default_route does not Validate #67

Open
bcdady opened this issue Jan 19, 2025 · 2 comments · May be fixed by #68
Open

cloudconnexa_network default_route does not Validate #67

bcdady opened this issue Jan 19, 2025 · 2 comments · May be fixed by #68

Comments

@bcdady
Copy link

bcdady commented Jan 19, 2025

The documentation for the default_route of the cloudconnexa_network resource lists that it should have a value (required) and a type (optional) attrib

I provided a cloudconnexa_network resource block that includes such a default_network block, but then running terraform validate returns the following error:

tf validate
╷
│ Error: Missing required argument
│ 
│   on networks.tf line 13, in resource "cloudconnexa_network" "awsusw2":
│   13:   default_route {
│ 
│ The argument "subnet" is required, but no definition was found.
╵
╷
│ Error: Unsupported argument
│ 
│   on networks.tf line 14, in resource "cloudconnexa_network" "awsusw2":
│   14:     value = "100.96.1.26/28"
│ 
│ An argument named "value" is not expected here.

My terraform resource:

resource "cloudconnexa_network" "awsusw2" {
  egress          = false
  internet_access = "LOCAL"
  name            = "AWS US West 2"

  default_connector {
      name = cloudconnexa_connector.default.name
      vpn_region_id = cloudconnexa_connector.default.vpn_region_id
  }

  default_route {
    value = "100.96.1.26/28"
    type  = "IP_V4"
  }
}
@bcdady
Copy link
Author

bcdady commented Jan 20, 2025

I got my module to validate by replacing value with subnet within the default_route block.

@bcdady bcdady linked a pull request Jan 20, 2025 that will close this issue
@sahaqaa
Copy link
Contributor

sahaqaa commented Jan 20, 2025

Created internal ticket CAPI-403 to review and fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants