Add a view to show the currently running version
Bug #545111 reported by
Anthony Lenton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical SSO provider |
Fix Released
|
Wishlist
|
Łukasz Czyżykowski | ||
Django Formassembly integration |
New
|
Undecided
|
Unassigned | ||
Software Center Agent |
Fix Released
|
Undecided
|
Anthony Lenton |
Bug Description
Currently we need to check the available features or bugs to determine which version is running on staging or production.
There should be a view that reports the current running version of our code. Maybe even versions of other libraries too.
SSO Testcase ISD_201
Related branches
lp://staging/~canonical-isd-hackers/canonical-identity-provider/versions-view
- Szilveszter Farkas (community): Approve
- Ricardo Kirkner (community): Needs Fixing
-
Diff: 177 lines (+118/-1)8 files modifieddebian/control (+2/-1)
debian/rules (+3/-0)
identityprovider/__init__.py (+2/-0)
identityprovider/templates/versions.html (+27/-0)
identityprovider/tests/test_views_versions.py (+33/-0)
identityprovider/urls.py (+4/-0)
identityprovider/views/versions.py (+39/-0)
scripts/update-version (+8/-0)
visibility: | public → private |
Changed in canonical-identity-provider: | |
milestone: | none → 2.6.0 |
Changed in canonical-identity-provider: | |
importance: | Undecided → Wishlist |
Changed in canonical-identity-provider: | |
status: | New → Confirmed |
Changed in canonical-identity-provider: | |
milestone: | 2.6.0 → 2.7.0 |
tags: | added: 2sp |
tags: |
added: sp-2 removed: 2sp |
Changed in canonical-payment-service: | |
importance: | Undecided → Wishlist |
milestone: | none → beta2 |
description: | updated |
Changed in canonical-isd-qa: | |
milestone: | none → canonical-identity-provider+2.7.0 |
Changed in canonical-identity-provider: | |
status: | Fix Committed → Fix Released |
Changed in canonical-isd-qa: | |
importance: | Undecided → Wishlist |
milestone: | canonical-identity-provider+2.7.0 → canonical-payment-service+beta2 |
Changed in canonical-payment-service: | |
milestone: | beta2 → 1.0.0 |
Changed in canonical-payment-service: | |
assignee: | nobody → Michael Foord (mfoord) |
status: | New → In Progress |
Changed in software-center-agent: | |
status: | New → Confirmed |
milestone: | none → 10.10 |
Changed in software-center-agent: | |
status: | Confirmed → In Progress |
assignee: | nobody → Anthony Lenton (elachuni) |
Changed in canonical-payment-service: | |
status: | In Progress → Fix Committed |
Changed in software-center-agent: | |
status: | In Progress → Fix Committed |
Changed in canonical-isd-qa: | |
milestone: | canonical-payment-service+beta2 → canonical-payment-service+1.0.0 |
Changed in canonical-isd-qa: | |
status: | Fix Released → Confirmed |
Changed in canonical-isd-qa: | |
status: | Confirmed → Fix Committed |
Changed in canonical-isd-qa: | |
status: | Fix Committed → Fix Released |
Changed in canonical-payment-service: | |
status: | Fix Committed → Fix Released |
Changed in software-center-agent: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It's generally not a good idea to advertise which versions of libraries you're running in case there are known security vulnerabilities which expose you to attack. If we provide an info page, access should be limited in some way. Some ways we might do this are:
* restrict to admin users
* restrict to members of teams
* place the info page url behind a vpn