| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add support for doing language resolution for a request, based on the
Accept-Language HTTP header.
Using the lazy gettext functionality from oslo gettextutils, it is
possible to use the resolved language to translate an exception message
to the user requested language and return that translation from the API.
Co-authored-by: Luis A. Garcia <luis@linux.vnet.ibm.com>
Co-authored-by: Mathew Odden <mrodden@us.ibm.com>
Implements bp user-locale-api
Change-Id: Id8e92a42039d2f0b01d5c2dada733d068b2bdfeb
|
| |
|
|
|
|
|
|
|
|
|
| |
Similar to a range of other components (e.g. glance,nova,...) and recent
reviews by Monty.
Running individual tests can be done like this:
./run_tests.sh keystone.tests.test_drivers
Change-Id: I2482a48322150e5eb09b703326a94d8283f1c75b
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allow each of the extensions to have their own
sql migration repository instead of mixing them into
the common repo. db_sync must be called explicitly on the extension.
In the past, it was assumed that only migrations for backends backed in
sql would be run. In practice, however, all of the migrations were run
every time. The code has been modified to reflect this.
Adds parameter --extension to the cli for db_sync and db_version
to test out the migrations
bin/keystone-manage db_sync --extension example
will migrate to version 1 and
bin/keystone-manage db_sync --extension example 0
will migrate it back to 0
to check the version
bin/keystone-manage db_version --extension example
blueprint multiple-sql-migrate-repos
DocImpact
Change-Id: I6852d75bde6506c535fa3d74537e3c1bbd6578d8
|
| |\ |
|
| | |
| |
| |
| | |
Change-Id: I00667ca171d1be5acdacb472561cbf74baf6a852
|
| |/
|
|
| |
Change-Id: I5364d9d930ca0871bd839917b23ef3199eff3340
|
| |
|
|
| |
Change-Id: Iab416c941c7db00d3fd725e1c0e12ed7fc193dd0
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
The initial configuration file and sample data are both are helpful in getting
setup with a keystone development environment.
Change-Id: Ic100177abe8dda1510a183463e61e0b757986e97
|
| |/
|
|
|
|
| |
A short blurb indicating how to do development for LDAP
Change-Id: Id75d9f9af8742b44158ed739d34dbdccb62eccf2
|
| |\ |
|
| | |
| |
| |
| | |
Change-Id: Iad8e63ab57c927032e4bafab79c1f22cb485173f
|
| |/
|
|
| |
Change-Id: I9ecb5d945d950e44c918469ab2ae0478e22bc1a8
|
| |
|
|
| |
Change-Id: I78c55c3050573d6430028bfc3c3c5d8a8c3e93b0
|
| |
|
|
| |
Change-Id: I32a41a60bc36caaa6bbc71ac24b620a0bb66a6dc
|
|
|
* docs in doc/ rather than docs/
* write out changelog from git
* freeze requirements file
Change-Id: If28d5414f7b2747fd6835546c45e1acfac8a3563
|
