[WIP] New Resources: aws_dx_private_vif, aws_dx_private_vif_allocation and aws_dx_private_vif_confirmation

[spirius]

Implemented direct connect private virtual interface and confirmation resources. Supports private VIFs for own and foreign AWS accounts. Only virtual private gateway is supported atm. Confirmation resource can be used to attach VIF to foreign account's virtual gateway.

[spirius]

Any suggestions regarding how to write acceptance tests for this? In order to create virtual interfaces aws requires dx connection to be in "available" state and that might take up to 72 hours after creation.

[ewbankkit]

See also:

• New Resource: aws_dx_private_virtual_interface #3253
• Add 'aws_dx_hosted_private_virtual_interface'/'aws_dx_hosted_private_virtual_interface_accepter' resources #3255

[spirius]

@ewbankkit thanks. Closing this, since it's already covered by your PRs.

[ewbankkit]

@spirius If there's any functionality that I missed, please let me know. AFAIK the issue with acceptance is the fact that you need an active Direct Connect connection available for creating the virtual interfaces and the creation of the connection is not 100% programmatic.

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!