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
I'm curious if someone could explain the generation of the persistent volume (2GB) disk that is created as part of Composer but it is not destroyed via terraform?
Is this something that Terraform should be managing and it is not?
For some background context:
We generate our projects with the factory module. We are occasionally tasked with deleting these projects. When the module attempts to turn off the compute API we get errors in all the projects that had a composer instance.
Which can be time-consuming to then go and manually remove these.
Kind regards,
Dan
The text was updated successfully, but these errors were encountered:
Hi,
I'm curious if someone could explain the generation of the persistent volume (2GB) disk that is created as part of Composer but it is not destroyed via terraform?
Is this something that Terraform should be managing and it is not?
For some background context:
We generate our projects with the factory module. We are occasionally tasked with deleting these projects. When the module attempts to turn off the compute API we get errors in all the projects that had a composer instance.
Which can be time-consuming to then go and manually remove these.
Kind regards,
Dan
The text was updated successfully, but these errors were encountered: