Support tagging transit gateway attachements in centralised network account

[zakbatinica-reply]

Is your feature request related to a problem? Please describe.

Currently when you tag a transit gateway attachment with LZA it tags the attachment in the account where the attachment is created. If you are operating with a centralised network account where the transit gateway lives, this means that any transit gateway attachments that are created outside of the centralised network account will not be tagged in the network account making it difficult to identify attachments when looking in the console.

Describe the feature you'd like

A toggle similair to the applyTags option that exists for the transit gateway peering configuration that would enable the transit gateway attachment to be tagged in both the centralised network account and the account in which the attachment was created.

[awsclemj]

Hello @zakbatinica-reply, and thank you for filing a feature request with the LZA team! I have placed an internal feature request on your behalf that the team will evaluate for a future release.

We highly appreciate your interest and support of the solution!