-
-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Source_role does not work #333
Comments
When the profile "dhitagger" is set, "devops-infra-tagger" is recognized as the base account. Therefore, the role "CDDOTagging" is not a switch target, but a condition of the role immediately after signing. |
Using this exact configuration in ~/aws/config works perfectly. I do not
understand your response, and it also follows your documentation.
…On Sat, Nov 11, 2023, 8:38 PM Toshimitsu Takahashi ***@***.***> wrote:
When the profile "dhitagger" is set, "devops-infra-tagger" is recognized
as the base account. Therefore, the role "CDDOTagging" is not a switch
target, but a condition of the role immediately after signing.
—
Reply to this email directly, view it on GitHub
<#333 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEF6HOVX5ABJLT2VOODUGBDYEAZCZAVCNFSM6AAAAAA7GN5URWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBWHE4DCMRYGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@towerbe It is not possible to share exactly the same settings as ~/.aws/config. Adding 'dhitagger' makes 'devops-infra-tagger' changed from a profile of Simple Configuration to an base account of Complex Configuration. |
When I try to configure a second profile using the first profile as its source no profiles show up in the list at all.
To Reproduce
Steps to reproduce the behavior:
[profile devops-infra-tagger]
aws_account_id = 000000000000
role_name = CDDOTagging
color = 3b9170
Everything works fine.
[profile dhitagger]
role_arn = arn:aws:iam::111111111111:role/CDDOTagging
source_profile = devops-infra-tagger
I use this method for CLI connections all the time with no issues. Also am following your configuration instructions. Don't understand why this is not working.
Expected behavior
The profile list should display and be pickable as per your instructions.
Environment
The text was updated successfully, but these errors were encountered: