-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate Django returner #62644
Deprecate Django returner #62644
Conversation
It's likely that the Django returner never worked - it can only fire signals from within the same process that the Django server is running in, which *won't* be the process that Salt is running in. Deprecating and marking for removal.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we removing the returner and not fixing it or moving to a salt extension?
bump @waynew did you see my comments above? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spoke to @waynew offline about this. The returner has actually never worked, which means there has been no usage of this returner either.
What does this PR do?
Deprecates the Django module so we can remove it. TBH we could probably just go
ahead and remove it.
It's likely that the Django returner never worked - it can only fire
signals from within the same process that the Django server is running
in, which won't be the process that Salt is running in. Deprecating
and marking for removal.
Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.