You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Service Used
Network
API Versions Used
2022-09-01
Description
I'm looking to migrate azurerm_private_endpoint_application_security_group_association. In this resource, we are doing a Get call from the application security group client and appending that to the private endpoint model.
Though the application security group models are the same from privateendpoints and applicationsecuritygroups, go doesn't like it as they are two separate packages.
I believe we need a way to copy the model from applicationsecuritygroups into the one from privateendpoints
References
No response
The text was updated successfully, but these errors were encountered:
@mbfrahry this only actually needs the ID to map across, so whilst these are two distinct object types in two different packages, it should be sufficient to specify:
Is there an existing issue for this?
Community Note
Service Used
Network
API Versions Used
2022-09-01
Description
I'm looking to migrate
azurerm_private_endpoint_application_security_group_association
. In this resource, we are doing a Get call from the application security group client and appending that to the private endpoint model.Though the application security group models are the same from privateendpoints and applicationsecuritygroups, go doesn't like it as they are two separate packages.
I believe we need a way to copy the model from
applicationsecuritygroups
into the one fromprivateendpoints
References
No response
The text was updated successfully, but these errors were encountered: