Open ljupcovangelski opened 3 years ago
I think the motivation here is important: Why do we need this?
It's clearly better than doing it manually, but it also requires lots of delicate decisions per provider of what to delete as you pointed out @ljupcovangelski. So the effort/benefit doesn't look all that good in my view.
Even if we eventually decide to build this, I think it's a no-brainer to wait until we have migrated providers to terraform. Otherwise, the provider code will become very hard to maintain.
Currently in the docs we are recommending or manual uninstall or destroy of the
Airy Core
resources, which were created withairy create
.We need to discuss and decide if we are going to introduce
airy destroy
and how it will work.For example, we can create
Airy Core
in AWS in an existing VPC. Soairy destroy
shouldn't destroy the VPC in that case. Also to be considered if we introduce other installation methods (for example namespaced installation in an existing kubernetes cluster).