{"id":324,"date":"2019-09-22T18:25:53","date_gmt":"2019-09-23T01:25:53","guid":{"rendered":"http:\/\/blog.nillsf.com\/?p=324"},"modified":"2019-09-22T18:26:03","modified_gmt":"2019-09-23T01:26:03","slug":"automating-clean-up-of-demo-resources","status":"publish","type":"post","link":"https:\/\/blog.nillsf.com\/index.php\/2019\/09\/22\/automating-clean-up-of-demo-resources\/","title":{"rendered":"Automating clean-up of demo resources"},"content":{"rendered":"\n

A while ago I wrote about a self-destructing VM<\/a>. The process was completely self-contained, and the VM deletes itself. This was a nice demo – but not too useful in my day-to-day, where I create demo’s of all kinds of different resources.<\/p>\n\n\n\n

In my case it’d be a lot better to have a daily automation script that would clean up after me. Kind of like a Roomba for Azure.<\/p>\n\n\n\n

Let’s think this through, think about what is required for this, and then build this out.<\/p>\n\n\n\n

Architecture<\/h2>\n\n\n\n

From a timeline perspective, this would have to look something like this:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Looking at this from right to left, this means we would need a system that asks for confirmation prior to deleting, that either deletes the resources or changes the tag value to a future date. <\/p>\n\n\n\n

This confirmation is triggered from a daily script that reads the tags, and triggers the confirmation email if the “to delete by” date is in the past. <\/p>\n\n\n\n

Finally, we need a (preferably) automated way to tag our resources with a date that we want them to be deleted by.<\/p>\n\n\n\n

Reasonably speaking, I see two options of “things”<\/em> we can delete, either a full resource group or actual individual resources. As I hate too many confirmations, I will create my workflow based on the resource groups rather than the resources themselves.<\/p>\n\n\n\n

So, thinking about options for the implementation, these are the options I see:<\/p>\n\n\n\n