Update Oslo wiki link in README

Use lastest Oslo wiki link.

Change-Id: I448aac133060fe7a4793ed5d92d7698db9984401
Lazy gettextutils behavior

gettextutils.enable_lazy() must be called before gettextutils._() is called to
ensure it has the desired lazy lookup behavior. This includes cases, like
keystone.exceptions, where gettextutils._() is called at import time.

Change-Id: I1db293978493868b6f7972b316fb6847c945ee30
Co-Authored-By: David Stanek <dstanek@dstanek.com>
Update curl api example to specify tenant

In the keystone api_curl_examples document, the curl example for
"POST /tokens" did not specify a tenant. This example utilized
the default tenant, which is not commonly used. Changed the
example to include "tenantName" as part of the example to prevent
future confusion.

DocImpact

Closes-Bug: #1269739

Change-Id: Iaad8c7c5a32bc6cff38c938dd36365cddd6741cb
Add the last of the outstanding helpstrings to config

Add the last of the outstanding help strings to the options defined
in keystone.common.config.

Adds in periods to the end of the helpstrings that were missing
proper ending punctuation.

DocImpact

Related-Bug: #1229941
Change-Id: Iebe0358a19f645220eb7b3dfca0dc868716f5bc8
Always include 'enabled' field in endpoint response

The 'enabled' field wasn't always returned in an endpoint response.

The 'enabled' attribute for endpoints was stored in the 'extra'
column as part of a JSON string. Now the 'enabled' attribute is in
its own column. It will also be easier to filter out disabled
endpoints now that enabled is a separate column.

With the 'enabled' field being a Boolean column in the database,
the server also needs to validate that the value is a Boolean (if
it's present). This is done in the same way that the server checks
the type of the 'enabled' value when creating users.

Closes-Bug: #1282266

Change-Id: I9b9379f4531c298c14508418dbfb629bdd6c2850
allow create credential with the system admin token

We are looking up trust_id during create credential, which means caller must
use a Keystone-issued token. This is unrealistic as create credential are
often done as part of bootstrap, using the static system admin token.
Furthermore, deployments which using external authorization will break as it
may not have a token_id in the request context.

For the above reasons, we'll skip trust_id lookup if the request token_id is
either absent or it is the static system admin token.

closes bug 1275145
closes bug 1263804

Change-Id: I6cda3c5f36c9754ab84e28ff9a9289887d6c9b77
Imported Translations from Transifex

Change-Id: Ib5db4752b6c764e11587126d2285aa0af79b2cc6
Mark revoke as experimental

Change-Id: Id0872daa159c58b502060ece9748d01da59519ea
Merge "Update Oslo wiki link in README"
Merge "Lazy gettextutils behavior"
Merge "Mark revoke as experimental"
Merge "Update curl api example to specify tenant"
Merge "Add the last of the outstanding helpstrings to config"
Merge "Always include 'enabled' field in endpoint response"
Merge "Imported Translations from Transifex"
Merge "allow create credential with the system admin token"