amplify init --providers $AMPLIFYPROVIDERS: profileName not taken into consideration

[dr-dolittle]

How did you install the Amplify CLI?

yarn

If applicable, what version of Node.js are you using?

v18.17.1

Amplify CLI Version

12.4.0

What operating system are you using?

Ubuntu 22.04.3 LTS

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No

Describe the bug

I set up the provider config via

export AWSCLOUDFORMATIONCONFIG="{\
\"useProfile\":true,\
\"profileName\":\"${AWS_PROFILE_NAME}\"\
}"

export AMPLIFYPROVIDERS="{\
\"awscloudformation\":$AWSCLOUDFORMATIONCONFIG\
}"

When I run amplify init --providers $AMPLIFYPROVIDERS --yes it does not consider the profile specified but deploys to default.

Using SSO

Expected behavior

Deploy to the profile specified

Reproduction steps

Obvious

Project Identifier

No response

Log output

``` # Put your logs below this line ```

Additional information

No response

Before submitting, please confirm:

• [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• [X] I have removed any sensitive information from my code snippets and submission.

[ykethan]

Hey @dr-dolittle, thank you for reaching out. I was unable to reproduce the issue in my local environment when utilizing the following

export AWS_PROFILE_NAME = "test"

export AWSCLOUDFORMATIONCONFIG="{\
\"useProfile\":true,\
\"profileName\":\"${AWS_PROFILE_NAME}\"\
}"

export AMPLIFYPROVIDERS="{\
\"awscloudformation\":$AWSCLOUDFORMATIONCONFIG\
}"

then ran amplify init --providers $AMPLIFYPROVIDERS --yes and observed the local-aws-config.json with the profileName.

could you provide us some additional information on how the profile is currently setup locally?

[josefaidt]

Hey @dr-dolittle I wanted to follow up here and see if you're still experiencing this?

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.