fix: Remove EC2-classic deprecation warnings by hardcoding classiclink values to null
#826
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
null
null
as unset value, resulting in deprecation warning hashicorp/terraform#31730 - defaulting tonull
does not resolve the warning and instead we have to hardcode the value asnull
to satisfy. Users cannot create new EC2-classic VPCs today, and users who are still using EC2-classic are required to upgrade (per AWS) - users who are using EC2-classic created under this module should pin their module version to v3.14.3 until they have migrated their VPC out of EC2-classicMotivation and Context
Breaking Changes
tl;dr - the breaking change is on the AWS side, not the module
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request