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

Aws provider 5.0.0 deprecated the classiclink parameter #958

Closed
djacquensf9 opened this issue Jun 26, 2023 · 6 comments
Closed

Aws provider 5.0.0 deprecated the classiclink parameter #958

djacquensf9 opened this issue Jun 26, 2023 · 6 comments

Comments

@djacquensf9
Copy link

Description

AWS provider 5.0.0 deprecated the classiclink parameter, therefore from now on if we use this VPC Module, we get the "Unsupported argument" error for :

  • enable_classiclink
  • enable_classiclink_dns_support

Thanks ;)

Versions

  • Module version: 5.0.0
  • Terraform version: 1.5.1
  • Provider version(s): AWS 5.0.0

Steps to reproduce the behavior:

Use this module with AWS provider 5.0.0

Terminal Output Screenshot(s)

image

@djacquensf9
Copy link
Author

My bad !!
The rm -fr .terraform did not work correctly. ;)

@OliverTetzTT
Copy link

Hello together,

we still encounter this error. We updated our terraform modules, tried removing and redownloading and still have this issue.

The only way to resolve this for our deployment is to comment the enable_classiclink out. But that feels like a very dirty hack.

Thanks in advance

@djacquensf9
Copy link
Author

djacquensf9 commented Jul 11, 2023

You deleted the .terraform folder in your root terraform folder and you are still having this issue, right?
Which versions of the AWS module and this VPC module are you using? Thanks

@OliverTetzTT
Copy link

To reiterate the statement from the previos issue reporter: Our bad!

We had our version defined with a ~> 3.0.0 instead of >3.0.0. Which lead to not properly updating this module.

Sorry for the hassle!

@djacquensf9
Copy link
Author

Since I am the previous reporter.
It was normal I helped on this case 😄

Have a great day 😉

@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 Aug 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants