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

Error on network_type after migration to 7.5.0 #323

Closed
gonrial opened this issue Sep 12, 2022 · 3 comments · Fixed by #324
Closed

Error on network_type after migration to 7.5.0 #323

gonrial opened this issue Sep 12, 2022 · 3 comments · Fixed by #324

Comments

@gonrial
Copy link

gonrial commented Sep 12, 2022

Description

After migration to 7.5.0 I got this error: An argument named "network_type" is not expected here.

According to the hashicorp/aws Changelog it seems that the network_type was introduced by this ticket and released in the 4.30.0 release, so it's not supported in the 4.28.0 which is the minimum version of this module.

Versions

  • Module version [Required]: 7.5.0

  • Terraform version: Terraform v1.1.8 on linux_amd64

  • Provider version(s):

    • provider registry.terraform.io/hashicorp/aws v4.29.0
    • provider registry.terraform.io/hashicorp/random v3.4.1

Reproduction Code [Required]

Steps to reproduce the behavior:

tf plan

Terminal Output Screenshot(s)

│ Error: Unsupported argument
│ 
│   on .terraform/modules/db/main.tf line 92, in resource "aws_rds_cluster" "this":
│   92:   network_type                  = var.network_type
│ 
│ An argument named "network_type" is not expected here.
@bryantbiggs
Copy link
Member

my apologies - looking again at the changelog it looks like the RDS instance resources was updated for this and the RDS cluster was not added till 4.30.0 as you've stated.

@antonbabenko
Copy link
Member

This issue has been resolved in version 7.5.1 🎉

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants