feat: leverage zola draft mechanism

content/posts/drafts/environment-aspects.md → content/posts/environment-aspects.md

@@ -1,6 +1,7 @@
 +++
 title = "6 Key Aspects of Architecting Your Environments for Sprawl"
 date = 2023-05-31T10:49:27-05:00
+draft = true
 +++
 
 Naming is Hard, but often times when it comes to environments [read: 1 or more systems deployed together] Naming is Hard because there is so much to cover and sooo many constraints.

content/posts/drafts/getting-more-bang-for-your-buck-with-pagerduty.md → content/posts/getting-more-bang-for-your-buck-with-pagerduty.md

@@ -1,4 +1,8 @@
-
++++
+title = "Getting more bang for your buck with PagerDuty"
+date = 2023-05-31T10:49:27-05:00
+draft = true
++++
 # Problems or at least statements of reality
 
 * Dealing w/ alerting on build/decom seems to be a consistently painful and inconsistent

content/posts/drafts/naming-pro-tips.md → content/posts/naming-pro-tips.md

@@ -1,6 +1,7 @@
 +++
 title = "Naming Pro Tips"
 date = 2023-05-31T10:49:27-05:00
+draft = true
 +++
 So, naming is hard. We've all agreed with this for a long while now.
 

content/posts/drafts/service-accounts.md → content/posts/service-accounts.md

@@ -1,3 +1,9 @@
++++
+title = "Service Accounts"
+date = 2023-05-31T10:49:27-05:00
+draft = true
++++
+
 Tell me if this sounds familar.  You start a new job and notice that there are still a bunch of changes happening on all these different applications that your team or the company use.  You ask for information on it and find out that they are having to re-authenticate a bunch of systems because the original setup was done by the employee they hired you to replace.  It probably comes as no suprise, and its good they are getting it cleaned up.
 
 But what path did they use to fix it?  Hopefully, a service account, but not always.