Lost logging support for django management commands

Bug #1731313 reported by Celso Providelo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snap Store Server
Fix Released
Undecided
Unassigned

Bug Description

Since r3571 [1] we have lost logging support in django management commands, messages are simple swallowed by the module.

The rationale for removing django logging configuration was because we were moving the webapp to talisker, which provides properly configured logging.

Talisker also offers a runner for standalone scripts (`talisker.run`), but that's not available in the revision used by SCA. So, to continue in this path, we would have to upgrade talisker, rollout and make sure there are no regressions, then come back to the mgmt. actions and find a way wrap them with talisker runner (Makefile ?).

[1] https://code.launchpad.net/~ricardokirkner/software-center-agent/django-logging-no-more/+merge/310998

Celso Providelo (cprov)
Changed in snapstore:
status: New → Confirmed
Changed in snapstore:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.