Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delete schedule of deleted transformations #48

Open
tugceozgur opened this issue Mar 24, 2022 · 1 comment
Open

Delete schedule of deleted transformations #48

tugceozgur opened this issue Mar 24, 2022 · 1 comment

Comments

@tugceozgur
Copy link

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

@tugceozgur tugceozgur changed the title remove transformation or at least deactivate schedule of deleted transformations Delete schedule of deleted transformations Mar 24, 2022
@vvemel
Copy link
Contributor

vvemel commented Apr 4, 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?

@SunilVenekarKrishnamoorthy I think this is something to discuss.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants