hmm so account-settings module has been upgraded to v2. looks like the provider config has changed from

dynamic assume_role

(which pulled the role from account-map) to an empty provider. does that mean in order to upgrade...we'll need to setup atmos profiles for our CI?

@Bruce Xu we are working on upgrading all our components to not use

account-map

and instead use Atmos Auth. Profiles are a different concept (a profile can define different auth providers/identities, but also other Atmos configurations). If you are using Atmos Auth, you can upgrade to v2. Otherwise, stay at v1 (we are actively working on this)

So generally, we try keep this channel for atmos, not our commercial reference architecture. This is to reduce the confusion between atmos and our comercial offerings. We ask questions pertaining to this be opened in https://github.com/orgs/cloudposse/discussions