terraform-provider-iterative icon indicating copy to clipboard operation
terraform-provider-iterative copied to clipboard

Published 20 hours ago • verified publisher icon iterative

`task` After task completion computing resources should be released (destroyed)

Open DavidGOrtega opened this issue 2 years ago • 4 comments

Right now even after the task execution we are still maintaining the resources created. A task should be just only a resource linked to the bucket and not to all the infrastructure used during computing. With #299 we might not even worried about keeping the tasks forever since we should not hit any cloud resources limit.

DavidGOrtega avatar Nov 25 '21 14:11 DavidGOrtega

related to #289 to some extend

DavidGOrtega avatar Nov 25 '21 14:11 DavidGOrtega

Maybe we can merge this issue with #289? The problem is the exactly the same, and the scope is very similar.

0x2b3bfa0 avatar Nov 25 '21 15:11 0x2b3bfa0

Its not the same issue indeed, and i can see the the code wont be the same. We will need to have two steps destroy. I might not want to destroy the task NEVER and that does not mean that I like the have the rest around

DavidGOrtega avatar Nov 25 '21 16:11 DavidGOrtega

Related to https://github.com/iterative/terraform-provider-iterative/issues/320#issuecomment-984777798

0x2b3bfa0 avatar Dec 02 '21 16:12 0x2b3bfa0