9ca374091b
The `keystone-manage token_flush` command was useful when we supported token format that were actually written to disk. Now that keystone has moved towards formats that don't require physical storage in the name of scalability, we no longer need the token_flush utility. This commit logs a warning when using `keystone-manage token_flush` so that people are aware they don't need to use it anymore if they are using supported upstream non-persistent token providers. Change-Id: I14d1e8a3ae367c8f13b6819a1a216f3f8f6b001a Closes-Bug: 1759289
11 lines
483 B
YAML
11 lines
483 B
YAML
---
|
|
fixes:
|
|
- |
|
|
[`bug 1759289 <https://bugs.launchpad.net/keystone/+bug/1759289>`_]
|
|
The ``keystone-manage token_flush`` command no longer establishes a
|
|
connection to a database, or persistence backend. It's usage should be
|
|
removed if you're using a supported non-persistent token format. If you're
|
|
relying on external token providers that write tokens to disk and would
|
|
like to maintain this functionality, please consider porting it to a
|
|
separate tool.
|