You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have removed one of our transformations from our config repo and even after it is deployed, I am still seeing the transformation is active and scheduled.
Deleted transformations can also be taken account while deploying changes with the cli. Is it possible to Delete Schedule for the transformation that has ben removed from the repo? fyi @chrfla-cognite@spex66
The text was updated successfully, but these errors were encountered:
tugceozgur
changed the title
remove transformation or at least deactivate schedule of deleted transformations
Delete schedule of deleted transformations
Mar 24, 2022
We cannot detect the transformations that used to be in the repo but were removed later on. CLI collects the transformations that are in the deploy folder, it detects if they should be updated or created. Checks notifications and schedules in the deploy list (whether they should be updated/deleted/created). This is expected behavior, which is the same as the old CLI.
Solutions that come to my mind:
A solution might be listing all transformations in the project and deleting the ones that are not in the deploy folder optionally.
Or another solution might be adding a source field to transformation configs in the backend. CLI deployments would set it to "CLI". And CLI would list the ones with source="CLI" and delete the ones that are not in the folder. But this has other details like what if user manually updates it in UI, is it still CLI sourced?
We have removed one of our transformations from our config repo and even after it is deployed, I am still seeing the transformation is active and scheduled.
Deleted transformations can also be taken account while deploying changes with the cli. Is it possible to
Delete Schedule
for the transformation that has ben removed from the repo? fyi @chrfla-cognite @spex66The text was updated successfully, but these errors were encountered: