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
A change in the /etc/profile.d/aws.sh script in Geodesic 3 causes it to skip creation of the /conf/.aws symlink to /localhost/.aws if the latter directory already exists.
Steps to Reproduce
Run docker run --rm cloudposse/geodesic:3.3.0-debian init | bash
Run installed geodesic script
Run assume-role to select a profile from the host system's ~/.aws/config
Symlink to /localhost/.aws is missing, causing tofu commands to fail with the following message:
| Error: failed to refresh cached credentials, the SSO session has expired or
│ is invalid: failed to read cached SSO token file, open
│ /conf/.aws/sso/cache/<guid>.json: no such
│ file or directory
Expected Behavior
Running tofu commands should load the aws sso cache properly from /conf/.aws
justinbwood
changed the title
/conf/.aws symlink does not exist in Geodesic >=3.x
/conf/.aws symlink is not properly created in Geodesic >=3.x
Oct 11, 2024
Describe the Bug
A change in the
/etc/profile.d/aws.sh
script in Geodesic 3 causes it to skip creation of the/conf/.aws
symlink to/localhost/.aws
if the latter directory already exists.Steps to Reproduce
docker run --rm cloudposse/geodesic:3.3.0-debian init | bash
geodesic
scriptassume-role
to select a profile from the host system's~/.aws/config
Symlink to
/localhost/.aws
is missing, causing tofu commands to fail with the following message:Expected Behavior
Running tofu commands should load the aws sso cache properly from
/conf/.aws
Additional Context
This appears to be related to PR #945, specifically the changes to
aws.sh
on L11 here:https://github.com/cloudposse/geodesic/pull/945/files#diff-abfb531b678543f55ff5e43c165a1820748fa0a95ad1a7b1ef0aecb30feafde1R11
When the profile is sourced,
${GEODESIC_AWS_HOME}
is equal to/localhost/.aws
, which exists, so it skips creation of the symlink.The text was updated successfully, but these errors were encountered: