Closed msessa closed 2 years ago
This appears to be happening on 2.1.0
as well
I encounter the same problem. The v1.134.0
work fine ,but the v1.135.0
has the problem.
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or 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.
What is the problem?
CDK asset publishing doesn't correctly assume the target asset publishing role in certain cases and fails to deploy S3 artifacts.
The issue seems to have surfaced with the release of cdk 1.135.0 but was possibly introduced in earlier versions.
Initial investigation suggests this line isn't passing the stack's asset publishing role and instead making API calls as the base role.
When v1.135 is used to deploy against an account bootstrapped with stack
< v9
, this code branch will trigger the aboveaccount()
call which causesthis.host.aborted
to becometrue
and this line to never be reached.Reproduction Steps
AccountA
AccountB
with stack v8 ( cdk <= 1.134.0 ), and--trust
role inAccountA
AccountB
@aws-cdk/core:newStyleStackSynthesis
=true
What did you expect to happen?
CDK deploy assumes the asset publishing role in
AccountB
and correctly uploads artifactsWhat actually happened?
fail: Need to perform AWS calls for account <AccountB>, but the current credentials are for <AccountA>
CDK CLI Version
1.135.0
Framework Version
No response
Node.js Version
v14.16.0
OS
MacOS
Language
Typescript
Language Version
No response
Other information
Complete deploy log: