---
title: "Joshua Rubio (@spectreworks) | Hashnode"
description: "Joshua Rubio (@spectreworks) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@spectreworks"
---

@spectreworks

# Joshua Rubio

@spectreworks · Phoenix, USA · Joined May 2026

## Comments

[Awesome! That's a definite gap in what I described. Container health and application health aren't the same thing — a container can report healthy while a connection pool inside it is still holding a stale secret from before the restart, especially if the pool doesn't force re-authentication on reconnect. SELECT COUNT(\*) told me the data survived. It didn't tell me every service was actually serving traffic on the new credential versus a cached one. Those are different claims, and I was only checking the first. Folding this in going forward: an actual read/write check per dependent service, not just a row count or a container status, before calling a rotation done. Thanks Mateo!](https://hashnode.com/posts/rotating-a-live-credential-without-losing-any-data/6abca8e5f87d59f11e72407e/comment/6abdeefbfd4c32eb218b283c#reply-6abed69eba86f405ca7b777c)

Reply · Article · Oct 1 · [Rotating a Live Credential Without Losing Any Data](https://hashnode.com/posts/rotating-a-live-credential-without-losing-any-data/6abca8e5f87d59f11e72407e)
