Using integ-runner for CDK apps with older aws-cdk-lib version

[tmokmss]

Hi, does integ-runner support using with older aws-cdk-lib version?

More specifically when I try to use integ-runner 2.60.0 with aws-cdk-lib 2.38.0, I get the following error:

Error: Resolution error: Resolution error: Resolution error: Resolution error: Context value '@aws-cdk/core:target-partitions' should be a list of strings, got: "@aws-cdk/core:target-partitions".
Object creation stack:
  at stack traces disabled.
Object creation stack:
  at stack traces disabled..
    at TestStack.regionalFact (/redacted/node_modules/aws-cdk-lib/core/lib/stack.js:1:9809)
    at ServicePrincipalToken.resolve (/redacted/node_modules/aws-cdk-lib/aws-iam/lib/principals.js:1:16812)
    at RememberingTokenResolver.resolveToken (/redacted/node_modules/aws-cdk-lib/core/lib/resolvable.js:1:1238)
    at RememberingTokenResolver.resolveToken (/redacted/node_modules/aws-cdk-lib/core/lib/private/resolve.js:1:4058)
    at resolve (/redacted/node_modules/aws-cdk-lib/core/lib/private/resolve.js:1:2661)
    at Object.resolve [as mapToken] (/redacted/node_modules/aws-cdk-lib/core/lib/private/resolve.js:1:1121)
    at TokenizedStringFragments.mapTokens (/redacted/node_modules/aws-cdk-lib/core/lib/string-fragments.js:1:1365)
    at RememberingTokenResolver.resolveString (/redacted/node_modules/aws-cdk-lib/core/lib/resolvable.js:4:358)
    at RememberingTokenResolver.resolveString (/redacted/node_modules/aws-cdk-lib/core/lib/private/resolve.js:1:4134)
    at resolve (/redacted/node_modules/aws-cdk-lib/core/lib/private/resolve.js:1:2045)

Subprocess exited with error 1
  FAILED     integ.-Test/DefaultTest (undefined/us-east-1) 18.366s
      Integration test failed: Error: Command exited with status 1

If I downgrade integ-runner to 2.38.0, or upgrade aws-cdk-lib to 2.60.0, both will work fine.

Reproduction steps:

Run the following commands:

git clone https://github.com/tmokmss/deploy-time-build.git
git checkout repro
yarn
yarn integ-runner --update-on-failed

code is here: https://github.com/tmokmss/deploy-time-build/tree/repro

[mrgrain]

It doesn't really, like you've found out. There's a bit of gray area in the sense that these packages only depend on very stable core features that have existed for a long time. But every now and then a change comes a long that makes it incompatible.