Do I Need a DPLY
A handy reference guide for engineers wondering if they need a deployment JIRA ticket (DPLY).
Remember: When in doubt, the answer is always "Yes".
Common Scenarios
-
✓
Deploy a new application version
"It's just a small bug fix" - Sorry, you still need a DPLY.
-
✓
Execute any write operation on a database
"It's just changing one row!" - Yes, you need a DPLY.
-
✓
Change environment variable
"But it's just turning on debug logs" - DPLY required.
-
✓
Change Optimizely toggle
"Even if it's in the admin UI?" - Yes, still need a DPLY.
-
✓
Modify vendor configuration via HTTP
"But I'm just using their official API!" - DPLY, please.
-
✓
Add/remove feature flag
"Even just to turn it off?" - Yes, DPLY required.
-
✓
Update a CDN asset
"It's just a small CSS tweak!" - DPLY, no exceptions.
-
✓
Restart a service
"Even if it's hung?" - Yes, DPLY first, restart second.
Try Your Own Scenario
IMPORTANT REMINDERS
- "Just this once" is not a valid reason to skip a DPLY
- "It works on my machine" doesn't mean you don't need a DPLY
- No, a Slack message is not a replacement for a DPLY
- Create a DPLY even if you're "absolutely sure nothing could go wrong"