On doc/source/api_curl_examples.rst the GET /v3/endpoints
example response section had http://localhost:35357/v2.0 but
API v2 was removed so it was modified to http://localhost:5000/v3.
Change-Id: Ic51c2d530296c9a92245b34b50fea5e82036d163
Originally, the "extra" in token data is generated by auth plugin
and then will be return to users within token data.
In Kilo, the "extra" in token data was deprecated[1], after that
if the auth plugin generate the "extra", a warning log will be
raised. To stop the warning, the auth plugins should stop
generating "extra" field.
After two releases, in Mitaka, the "extra" in token data was
removed[2], but the "extra" was still created by default as an
empty dict {}. Actually, "extra" should not be created any more
in Mitaka because Keystone has warned the auth plugins for two
releases.
Now in Rocky, it's safe enough to remove the "extra" from token
issue flow at all since it has never been used from Mitaka. The
only concern for the out tree plugins about the removal is that
if they still put "extra" into auth_context, Keystone will raise
KeyError. But can it be happened? Only if the out tree plugins
ignore the warning in Kilo, and still contain "extra" but never
use them from Mitaka. For most auth plugins which follow the
Keystone deprecation step, this patch is a silent change.
[1]: https://review.openstack.org/#/c/162662
[2]: https://review.openstack.org/#/c/249480
Change-Id: I828cc0ad3ac265abdfea2e1571806add128ae51e
Add documentation in the User section on managing, using, and rotating
application credentials.
Since application credential support didn't make it into
python-openstackclient in the Queens release, show examples using
python-keystoneclient.
Change-Id: I24bc51d2f3741771ba321fc05d49fd111aa76c15
The curl examples we keep in our documentation contain examples for
interacting with the now removed v2.0 APIs. This commit removes those
examples since we no long support v2.0, except for the ec2token API
until the T release. The curl examples didn't have any v2.0 ec2token
examples.
Change-Id: I7e16421873de1c2ebf13db971bef80a2d74e5823
Some docs present in developer documentation section
are related to APIs and API examples. Following the
reorganisation of docs in four categories, those docs
are migrated to the user/API doc section.
Change-Id: Id7f7b5601295036a54c6840015d0f0b4b2d23a21
* remove online_schema_migration_examples since they overlap
with a section in the best practices doc
* move developer docs to doc/source/devref and rename where
appropriate
* moved content in developer.rst around, so the more often used
functions (releasenotes, docs, sample config and tests are
near the top).
* general clean up
Change-Id: If00b6535564644ff1f5b78e232edbac5d6e686f0
Part of CURL response is not accurate anymore
- There will be no service catalog returned if we get
a token from a existing token.
- Miss `audit_ids` in the response.
Closes-Bug: #1459532
Change-Id: I81db8db37f4ffdad01f976a16c14f45f411db76d
Currently, `curl http://0.0.0.0:35357` and `curl http://0.0.0.0:35357/v2.0/`
no longer have the same response, since keystone has it's V3 APIs. Update
the doc to differentiate the two Curl example.
Change-Id: I08f5e3bd502ebd78ea775ea4135b5c3ffb80e9c7
Getting a user's roles isn't going to be implemted according to bug reports
(bug 1418015 and bug 933565). This commit removes the test case from
test_content_types.py and removes documentation from example curl calls.
Change-Id: Id317cc28d961316be6a7b8278c5242382784f10f
Related-Bug: 933565
Related-Bug: 1418015
There were curl examples for v2 APIs, but none for V3. This change
adds some that I've found handy.
Also, added an example of getting the revocation list using the v2
API. This is handy for checking token revocations.
Partial-Bug: #1283943
Change-Id: I228dc479b29db730873ba95207e4ace85c20e1fe
The code-block directive wasn't used for literal blocks in the
curl examples document, so they weren't highlighted nicely.
Change-Id: If0165ec666003682695c06a9b4ae840016b8355b
The keystone developer docs index page had two links to the same
API examples page: "Service API Examples Using Curl" and
"Admin API Examples Using Curl". This is because the API examples
document had 2 top-level sections.
Partial-Bug: #1283943
Change-Id: I8204268aa482e59f9108d515b69e9c37a12a9e08
Remove PDF link.
Replace deep html links with links to the docs.openstack.org site.
Change-Id: Ic7c2218bf43a221e8d753a910fdfb2243851214d
Closes-Bug: #1313127
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
I recall these attributes being discussed at one point
(pre-incubation?), but have never been supported by OpenStack and don't
appear to be defined in any v2.0 WADL/XSD specification.
Change-Id: Ia5b691972c70456e3d62750173e2bfc6e9aec55a
Closes-Bug: 1273831
erus