Change Details

Currently PAWS uses a trove db to manage user login data. This has no significant stateful data, and ideally is replaced on a cluster upgrade to prevent the confusing "Respawn" error that results from stale cookies. Lacking data that has any need to persist beyond the life of the cluster, can we simplify the deployment by adding a sql container to it? Pros: No more trove db to deploy separately Minikube can now more resemble the production cluster, by deploying the same sql container, rather than a sqlite file Cluster more of an atomic unit, preventing discord between a new cluster and an old database (namely the respawn button that does nothing) Cons: Furthered direct experience in the ephemeral nature of all things, are we ready for that?

Currently PAWS uses a trove db to manage user login data. This has no significant stateful data, and ideally is replaced on a cluster upgrade to prevent the confusing "Respawn" error that results from stale cookies. Lacking data that has any need to persist beyond the life of the cluster, can we simplify the deployment by adding a sql container to it? Pros: - No more trove db to deploy separately - Minikube can now more resemble the production cluster, by deploying the same sql container, rather than a sqlite file - Cluster more of an atomic unit, preventing discord between a new cluster and an old database (namely the respawn button that does nothing) - Collapses the 2 commit deploy in https://wikitech.wikimedia.org/wiki/PAWS/Admin#Deployment to one commit Cons: Furthered direct experience in the ephemeral nature of all things, are we ready for that?

Currently PAWS uses a trove db to manage user login data. This has no significant stateful data, and ideally is replaced on a cluster upgrade to prevent the confusing "Respawn" error that results from stale cookies. Lacking data that has any need to persist beyond the life of the cluster, can we simplify the deployment by adding a sql container to it? Pros: - No more trove db to deploy separately - Minikube can now more resemble the production cluster, by deploying the same sql container, rather than a sqlite file - Cluster more of an atomic unit, preventing discord between a new cluster and an old database (namely the respawn button that does nothing) - Collapses the 2 commit deploy in https://wikitech.wikimedia.org/wiki/PAWS/Admin#Deployment to one commit Cons: Furthered direct experience in the ephemeral nature of all things, are we ready for that?