You would not need to write a material. You could set up code independent of GoCD that runs on a schedule (e.g. a cron job) and query infrastructure. This job could trigger some kind of cleanup pipeline via the GoCD pipeline scheduling API.
I don't really know that I recommend it though -- GoCD is best at "moving bits through environments" not "random admin tasks". I think you might be happier if you just set up a cron job that queries the infrastructures and tears it down as needed and just keep the CI/CD tool out of it. -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
