<@UB89GSWCF> I saw there was a new release but I s...
# atmos
m
@Andriy Knysh (Cloud Posse) I saw there was a new release but I still see the same issue
a
you are seeing exactly the same issue described in https://github.com/cloudposse/atmos/issues/2071 ?
m
Yeah but I just notice that is bc atmos is using
AWS_PROFILE
to set/check a profile and since I have aws cli setup I have this ENV set. Once I unset this atmos actually works
maybe is a new issue but it sounds like it's close enough that maybe is the same?
so I think atmos is using
AWS_PROFILE
and
ATMOS_PROFILE
to set the profile? is this intencional? if so maybe I have to change my config
but I prefer this to be separate
a
yes, please open a new issue and describe the problem, we'll fix it ASAP
m
Thanks will do
a
atmos is using
AWS_PROFILE
and
ATMOS_PROFILE
,
ATMOS_PROFILE
takes precedence
m
is this intencional? if so this is not and issue then?
a
yes, it's intentional but please confirm if you are seeing anything wrong, we'll review and fix
e
@Andriy Knysh (Cloud Posse) AWS_PROFILE should have zero to do with atmos profiles
Atmos profiles should absolutely be unaware of that environment variable; there is no relationship
m
Yeah I feel like having
AWS_PROFILE
is confusing and makes it less flexible
e
Yes, its flat out wrong if atmos is confusing Aws profiles with atmos profiles. Similar concept but for 2 entirely different tools/SDK
An Atmos Profile should be able to set an AWS profile, but and AWS profile should never influence Atmos profiles.
a
yea, sorry, I misunderstood
m
no worries, I will create the issue then
a
@Miguel Zablah i don't understand what issue are you seeing, please provide more info
m
@Andriy Knysh (Cloud Posse) if you set
AWS_PROFILE
then atmos will error with:
Error: profile not found
when running anything. So for example if you run this:
export AWS_PROFILE=org-admin
and then run:
atmos
it will give you this error:
Copy code
atmos

   Error 

   Error: profile not found
  
  ## Explanation

   Profile  org-admin  does not exist in any configured location
   Available profiles are:  ci, developer 
  
  ## Hints

   💡 Check the spelling of the profile name

   💡 Run  atmos profile list  for detailed information about each profile

   💡 Verify the profile directory exists if you expect to see it
this is fix by just
unset AWS_PROFILE
actually this an issue bc atmos set this ENV when use
atmos auth
e
Ok, we should fix that asap
m
thanks I will create the issue
e
@Andriy Knysh (Cloud Posse) can you take a look at this one?
👍 1
a
@Miguel Zablah @david please test this release https://github.com/cloudposse/atmos/releases/tag/v1.206.2 let us know if you see any other issues
👀 2
🚀 1
party parrot 1
m
@Andriy Knysh (Cloud Posse) I have tested it and it now works without issues!! Thanks!! BTW I have also tested the
!terraform.state
fix with the
::
and it's awesome!! great job!!
✅ 1
❤️ 1