You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2018. It is now read-only.
I have a management command for Django to create a release. It accepts a revision and a branch as arguments and take the organisation, app id and the bearer from environment variables.
Is this something which would get some interests? It does pretty much the same as the fabric version and could be handy for those not using fabric.
The text was updated successfully, but these errors were encountered:
Thanks for your interest in improving the Opbeat module, that's great! We discussed adding a management command like this for a long time, so we're definitely open to add it.
For getting the org/app IDs and the secret token, it would probably be better to just import a client object from opbeat.contrib.django.models and get the variables from there. That way, you get the correct values, no matter if they are configured via environment variables or Django settings.
That would be very interesting! Currently, the Fabric-based model requires us to have the client codes hardcoded - unless we write some extra local configuration to cover multiple environments of an app on Opbeat (eg staging, production).
A management command would be excellent.
I have a management command for
Django
to create a release. It accepts a revision and a branch as arguments and take the organisation, app id and the bearer from environment variables.Is this something which would get some interests? It does pretty much the same as the
fabric
version and could be handy for those not usingfabric
.The text was updated successfully, but these errors were encountered: