Skip to main content
Answer

Toolkit changes unchanged resources on deployment

  • May 16, 2025
  • 1 reply
  • 29 views
K
Seasoned
Forum|alt.badge.img+4

Hi.

Upon doing either a deploy or a dry-run deploy, the summary displayed by toolkit includes quite a few resources that have not changed. Like in this example, where the only thing I changed was a the handler-file for a cognite function:

┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━┳━━━━━━━━┳━━━━━━━┓
┃                                ┃   Would ┃  Would ┃   Would ┃        ┃       ┃
┃                                ┃    have ┃   have ┃    have ┃        ┃       ┃
┃                       Resource ┃ Created ┃ Delet… ┃ Changed ┃ Untou… ┃ Total ┃
┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━╇━━━━━━━━╇━━━━━━━┩
[...]
│             function schedules │       0 │      0 │       0 │      2 │     2 │
│                      functions │       1 │      1 │       0 │      1 │     2 │
│                     raw tables │       1 │      0 │       0 │     37 │    38 │
│         resource-scoped groups │      16 │     16 │       0 │     12 │    28 │
│                transformations │       0 │      0 │      35 │      7 │    42 │
│              workflow versions │       0 │      0 │       3 │      0 │     3 │
└────────────────────────────────┴─────────┴────────┴─────────┴────────┴───────┘

What could the reason be here? We’re working on both Windows and Linux on our project - could it be an encoding issue?

Best answer by Anders Albert

If you run cdf deploy --dry-run --verbose, Toolkit will print out what the difference is and thus why it is considering the resource to be changed. You can also use, for exampl, --include functions, to limit the resources printed in the terminal. I don’t think this is an encoding issue, it is likely a bug on our side. We had some challenges with comparing when there is server set properties on resources. So if after running with the --verbose flag and think this is a mistake, feel free to email me the terminal print out and we will fix it.

Mithila Jayalath

1 reply

Anders Albert
Seasoned Practitioner
Forum|alt.badge.img
  • Anders Albert
  • Seasoned Practitioner
  • Answer
  • May 19, 2025

If you run cdf deploy --dry-run --verbose, Toolkit will print out what the difference is and thus why it is considering the resource to be changed. You can also use, for exampl, --include functions, to limit the resources printed in the terminal. I don’t think this is an encoding issue, it is likely a bug on our side. We had some challenges with comparing when there is server set properties on resources. So if after running with the --verbose flag and think this is a mistake, feel free to email me the terminal print out and we will fix it.

K
H
Terms & ConditionsCookie SettingsAccessibility statement