(cli): "To get rid of this warning, please upgrade to boostrap version >= undefined"

[Plasma]

What is the problem?

The output of cdk diff and cdk deploy are showing the following console warning after printing stack names:

(To get rid of this warning, please upgrade to bootstrap version >= undefined)

For example:

> cdk diff --profile MyProfile
Including dependency stacks: MyStack
Stack MyStack123
(To get rid of this warning, please upgrade to bootstrap version >= undefined)
There were no differences
Stack MyStack456
(To get rid of this warning, please upgrade to bootstrap version >= undefined)
There were no differences

Reproduction Steps

Unable to reproduce outside my current CDK project.

What did you expect to happen?

This error to not appear, or the undefined value to indicate a value to upgrade to, or for the error to have been fixed after a cdk bootstrap was ran.

What actually happened?

The error persists even after a npm install -g aws-cdk, cdk boostrap --profile MyProfile succeeding, and using the latest .NET AWS CDK at time of writing (1.140.0).

CDK CLI Version

2.8.0 (build 8a5eb49)

Framework Version

No response

Node.js Version

n/a

OS

Windows

Language

.NET

Language Version

1.140.0 C# NuGet

Other information

A brand new cdk init project does not show this error, it must be related to my CDK project.

[frjtrifork]

We are seeing the same warning (for some time now) in our existing aws-cdk typescript project.

We are at 1.140.0 but the warning was also being logged in 1.139.0 (and maybe earlier as well)

[adeelamin15]

Observing same warning as well with python based aws-cdk project on MacOS and Linux. Using cdk version 2.8.0 and also cdk bootstrap is showing it is up to date.

[NGL321]

This seems concerning. As long as it is limited to a warning rather than a blocker, I am going to leave it as a high priority rather than urgent and investigate it as such.

If this becomes a blocker, please comment to indicate and we can urgently investigate.

Could you also indicate here whether you are experiencing this in v2 releases as well, or just v1?

@frjtrifork how long is some time? Even a general estimate will help narrow the possible commits that could have introduced this.

[adeelamin15]

@NGL321 For me it is coming with v2 release. I have been using v2 release since quite a time and it wasn't there. Cannot say about v1.

[frjtrifork]

@NGL321 Our CICD pipeline that log this in a scheduled nightly run has been disabled for a while. So I don't have a specific time.

I can say that it is not in the logs from the CICD runs performed before December 15 where the pipeline scheduler was disabled. The scheduler was enabled again on January 21 where the warning does appear.

I have been running our cdk scripts locally a few times between Christmas and January 21 and I think I started seeing this around the time I updated to 1.139, but I cannot say for sure. Since it was just a warning I did not put much effort into investigating it.

[zessx]

I just upgraded from 2.0.0 (using it since early December) to 2.8.0 and now seeing this very same warning.

[Plasma]

I can see this warning was introduced ~16 days ago (cc @corymhall ) at 2256680 tagged with versions v2.8.0, v2.7.0, v1.140.0, v1.139.0.

Reviewing the code above, I don't have any errors printed before the warning, so assume its because stackSdk.didAssumeRole == false being triggered. I can see the PR this code was for at #18277 talks about assuming a role for diff and may have some role requirements?

@NGL321 can confirm its not blocking anything for me, its just a console warning at the moment.

[adeelamin15]

UPDATE

So it turns out that there was a great mismatch of minor versions between my cdk command line tool installed via npm and python library for cdk i.e. aws-cdk-lib . I just upgraded my requirements.txt to match with the version cdk cli and got rid of this warning.

[frjtrifork]

@Plasma - nice find.

Even though it is just a warning it would be nice if it at least would provide a version for the message.
If there is no lookupRole for the stack - then undefined is printed making it harder for the user to figure out what to do

In our case it has been almost a year since we did a cdk bootstrap in our production account and we are stil on 1.140.0 in production but will be migrating to 2.x in a few weeks.

const upgradeMessage = `(To get rid of this warning, please upgrade to bootstrap version >= ${stack.lookupRole?.requiresBootstrapStackVersion})`;