CDK diff incomplete on MacOS

• I’m submitting a …

  • 🪲 bug report
  • 🚀 feature request
  • 📚 construct library gap
  • ☎️ security issue or vulnerability => Please see policy
  • ❓ support request => Please see note at the top of this template.

• What is the current behavior? On MacOS (Mojave) the cdk diff command only prints the ‘IAM Statement Changes’ section while there are several more changes (IAM policy changes and a lot of different changed resources). On two Linux machines (one running Ubuntu, one running Amazonlinux 2) with the same NodeJS version the cdk diff command on the same stack shows all the differences.

• What is the expected behavior (or behavior of feature suggested)? The cdk diff on MacOS should show the full set of changes just like it does on Linux.

• What is the motivation / use case for changing the behavior or adding this feature? As a developer using the CDK, I want to see all changes that the deployment would cause so that I don’t find a “bad surprise” after the deployment.

• Please tell us about your environment:

  • CDK CLI Version: 0.35.0
  • Module Version: 0.35.0
  • OS: OSX Mojave
  • Language: TypeScript
  • NodeJS Version: v10.15.3

• Other information

  • Usually, I am using zsh on my Macbook, but I also tried it with bash and sh - same result.
  • Edit: I played around with a few more combinations of diffs: in a cdk diff without any ‘IAM Statement Changes’, I can at least see an incomplete list of resource changes in the list of differences. So there might be a connection.

[lqueryvg]

@NGL321, thanks for responding, but I think this is my misunderstanding. I’ve seen “hype” on the internet saying that cdk diff is equivalent to terraform plan. I don’t think that’s true.

terraform plan compares the desired state (your code) against deployed resources. Whereas cdk diff compares the desired state against the stack. It doesn’t look at the deployed resources until you deploy, and it will only do that if it sees that your code has changed. You only find out about discrepancies between the stack and deployed resources at deployment time, so there’s always room for a little “surprise”, here or there 😉 😮

Bottom line, it’s not the same at all really.

[NGL321]

Hi Thomas, thanks so much for reaching out.

It would be super helpful if we could get a gist of your terminal, so we can better analyze what is going on.