fix: Parameter cidr_block set to null if use_ipam_pool set to true

[osaluden]

Description

cidr_block parameter is set to null when use_ipam_pool varaiable is set to true. Thus, only ipv4_netmask_length is available when you want to use IPAM. However, it is possible to chose the CIDR rather than the netmask length as the example shows at line 44.

Motivation and Context

Want to be able to use IPAM with CIDR selection, not only with netmask length selection.

Breaking Changes

No breaking changes.

How Has This Been Tested?

• Test with cidr provisioned as example shows at line 44
• Test with ipv4_netmask_length provisioned as example shows at line 24
• Test with use_ipam_pool set to false
• I have executed pre-commit run -a on my pull request

[osaluden]

Hi there

After several tests an deployment, I discovered that if the parameter use_ipam_pool is set to false, it is still possible to use the ipv4_ipam_pool_id parameter to register the VPC CIDR into the desired IPAM pool. This way, the cidr parameter can be used as well as ipv4_netmask_length if you want to ask IPAM to provided you with a CIDR range with the desired netmask length.

Let's close the pull request.

[github-actions]

I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.