md5_authentication_key not managable net-vlan-attachments

[mhutzsch]

In the google provider a new attribute for the md5_authentication_key was implemented in the google_compute_router_peer. The net-vlan-attachment could implement this on the resource, see: GoogleCloudPlatform/magic-modules#9666

Why does the module only deploy the router_peer for dedicated interconnect and not for partner_interconnect? It is still possible to set the md5 key in the console when a partner interconnect is deployed. My guess is, that the interfaces deployed in a partner interconnect are not managed via terraform but the ids are a mandatory key for the router_peer resource. Is my assumption right? Any ideas how to get a md5_authentiction_key into the terraform code for partner interconnect?

[sruffilli]

Hey @mhutzsch,
#2142 introduces support for BFD and MD5 Auth in the supported setups.

[...] interfaces deployed in a partner interconnect are not managed via terraform [...]
Any ideas how to get a md5_authentiction_key into the terraform code for partner interconnect?

Given interfaces are created automatically when partner interconnect is activated, I believe the only viable way to manage the md5_auth via terraform is to import google_compute_router_peer after it's created.

Unfortunately I suspect managing this process wouldn't really be practical within the net-vlan-attachment module.