r/aws_vpc_ipv4_cidr_block_association: Support optional import of the ipv4_ipam_pool_id and ipv4_netmask_length attributes

[ewbankkit]

Description

Relations

Closes #38873.

Output from Acceptance Testing

% make testacc TESTARGS='-run=TestAccVPCIPv4CIDRBlockAssociation_' PKG=ec2
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.23.7 test ./internal/service/ec2/... -v -count 1 -parallel 20  -run=TestAccVPCIPv4CIDRBlockAssociation_ -timeout 360m -vet=off
2025/03/11 16:08:31 Initializing Terraform AWS Provider...
=== RUN   TestAccVPCIPv4CIDRBlockAssociation_basic
=== PAUSE TestAccVPCIPv4CIDRBlockAssociation_basic
=== RUN   TestAccVPCIPv4CIDRBlockAssociation_disappears
=== PAUSE TestAccVPCIPv4CIDRBlockAssociation_disappears
=== RUN   TestAccVPCIPv4CIDRBlockAssociation_ipamBasic
=== PAUSE TestAccVPCIPv4CIDRBlockAssociation_ipamBasic
=== RUN   TestAccVPCIPv4CIDRBlockAssociation_ipamBasicExplicitCIDR
=== PAUSE TestAccVPCIPv4CIDRBlockAssociation_ipamBasicExplicitCIDR
=== CONT  TestAccVPCIPv4CIDRBlockAssociation_basic
=== CONT  TestAccVPCIPv4CIDRBlockAssociation_ipamBasic
=== CONT  TestAccVPCIPv4CIDRBlockAssociation_ipamBasicExplicitCIDR
=== CONT  TestAccVPCIPv4CIDRBlockAssociation_disappears
--- PASS: TestAccVPCIPv4CIDRBlockAssociation_basic (42.75s)
--- PASS: TestAccVPCIPv4CIDRBlockAssociation_disappears (47.47s)
--- PASS: TestAccVPCIPv4CIDRBlockAssociation_ipamBasicExplicitCIDR (1170.86s)
--- PASS: TestAccVPCIPv4CIDRBlockAssociation_ipamBasic (1174.71s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/ec2	1180.674s

[github-actions]

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.