bin/openquake and engine.py: Associate the current user with a calculation and outputs
Bug #926164 reported by
Lars Butler
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenQuake (deprecated) |
Fix Released
|
Medium
|
Lars Butler |
Bug Description
[et=6h]
[at=1.5h]
Currently, there is 1 user in the database (in the oq_user table): 'openquake'
- When a calculation is run, get the current username (using getpass.getuser(): http://
- If the user does not exist, create an oq_user record for that username
- If it already exists, great; do nothing
- Get the OqUser Django model object for the user record
- This is user should be the owner all subsequent oq_job_profile, oq_calculation, and output records.
The reason why we want to do this is so that results displayed by the openquake command line interface are filtered by 'owner'.
description: | updated |
Changed in openquake: | |
status: | New → Incomplete |
summary: |
- bin/openquake and engine.py: Associated the current user with a + bin/openquake and engine.py: Associate the current user with a calculation and outputs |
Changed in openquake: | |
status: | Incomplete → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Lars Butler (lars-butler) |
milestone: | none → 0.6.0 |
description: | updated |
Changed in openquake: | |
status: | In Progress → Fix Committed |
Changed in openquake: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Pull request: https:/ /github. com/gem/ openquake/ pull/690