Sometimes you just need to rebuild your docker containers and that's where the problem started. When my containers came back, it wouldn't start because of a TypeError being thrown.
File "/usr/local/lib/python3.8/site-packages/djstripe/models/__init__.py", line 25, in <module>
from .core import (
File "/usr/local/lib/python3.8/site-packages/djstripe/models/core.py", line 30, in <module>
from ..signals import WEBHOOK_SIGNALS
File "/usr/local/lib/python3.8/site-packages/djstripe/signals.py", line 8, in <module>
webhook_processing_error = Signal(providing_args=["data", "exception"])
TypeError: __init__() got an unexpected keyword argument 'providing_args'
Hmmm...
So I reviewed what was running on my docker containers. I had 4 containers: django with pipenv, celery, rabbitmq, and postgres. I ruled out postgres and rabbitmq out of the gate since the error is clearly a Python error.
Focusing on the django container, I eventually found the error - took me the whole afternoon. At first I thought it was a docker bug but it wasn't. It was because of how pipenv was getting and installing the packages. Let me explain.
Our pipenv file that had django was set to install the latest version so it was written as django = "*". When I rebuilt the container and the dockerfile executed it downloaded the latest version of django which was 4.00rc-1.
The fix was to set the version: django = "~=3.2".
The moral of the story is don't blindly set your pipenv file to "*" and instead be explicit with the versions. Luckily pipenv does support semantic versioning meaning it will install minor versions of django 3.2 like 3.2.2 but not Django 4.0.
