Yes, we are moving away from account map for all new engagements. For the next year, we need to straddle a world where both work, before we fully yank it out. We therefore use a providers.tf mixin that doesn't use account map.

@Erik Osterman (Cloud Posse) I see that mixins are only available in ComponentVendorConfig which is considered legacy, and not in AtmosVendorConfig which is considered as the recommended vendoring type. So how can I achieve this behavior with AtmosVendorConfig?

You can also try the

generate

block

I'll give it a go. Thank you 🙂