Skip to content
Discussion options

You must be logged in to vote

Hi @naoki85

Thank you for the report. This was actually a bug we just fixed yesterday. Our 0.1.3 release should address this issue. AWS_API_MCP_PROFILE_NAME is now used appropriately for both low level commands and high level commands (what we call CLI customizations).

Do give it a try and let us know if you still encounter the issue.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@naoki85
Comment options

Answer selected by PCManticore
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants