Now that we support other-requirements.txt and there is a Project Team
Guide doc [1] on how to set a Python environment up for development, we
can take benefit of them and make our docs more concise.
[1] http://docs.openstack.org/project-team-guide/project-setup/python.html
Co-Authored-By: Hidekazu Nakamura <hid-nakamura@vf.jp.nec.com>
Change-Id: Idcfadb7922b75464af430264e55aadc442e1b0a8
Add the following query options to the api-ref:
* parents_as_list (key-only, no value expected)
* subtree_as_list (key-only, no value expected)
* parents_as_ids (key-only, no value expected)
* subtree_as_ids (key-only, no value expected)
Change-Id: Ie9362885d57112c81c7141c4238e9e3d5d3e0431
Closes-Bug: #1609175
This adds response tables to multiple tenant API calls within
the identity admin API.
Change-Id: I78ff3d981ed0a1d4dc42d0a81b0369e7275d4d85
Closes-Bug: #1572168
Running `tox -e api-ref` prints warning:
WARNING:test command found but not installed in testenv
cmd: /bin/rm
env: /opt/stack/keystone/.tox/api-ref
Maybe you forgot to specify a dependency? See also the whitelist_externals envconfig setting.
Change-Id: I4c1718dac22c374f048d9e04f42051e10021bb31
Rolling upgrades are being introduced in the Newton release, which will
substantially impact the process that deployers will have to follow to
upgrade keystone.
This will provide us a basis for documenting rolling upgrades (also,
it's about time we documented our current process).
bp manage-migration
Change-Id: I5a37c781b83967b12cda60b054c612df3c3cb697
The "is_domain" query parameter is missing from GET/UPDATE /v3/projects
documentation in the API site.
Change-Id: I059f7e2ac689ec799dbdcc30c071de26d1603c47
Closes-bug: #1609174
If we generate keystone.conf using "tox -e genconfig",
some options are different from the sample file.
So update it.
Change-Id: I7f20338d2fab60f692dc58ca731a6a56279224fe
hashlib.algorithms_guaranteed is a set so the order is not guaranteed. This
means that the order could be different every time 'tox -e genconfig'
is run.
Change-Id: Iaa46604fccb382f174836fa6e248abf0bd7c3674
This patch implements the following PCI-DSS requirements:
* PCI-DSS 8.2.4: Change user passwords/passphrases at least once every
90 days.
Once a user's password is expired, they will not be able to authenticate
and be required to reset their password. This patch adds a new
password_expires_at attribute to the user response.
Depends-On: I07c10de627898d6ac79578dc24292ded4a2190f1
Partially-implements: blueprint pci-dss
Change-Id: If8979dbfc202bc354b1537a5962143bb7b3be28e
The v2 API was deprecated in mitaka with change:
e63a8311fa2e5d7cccdb76b4cd3fc17719cc86c6
The api-ref needs to be updated to show that as
well since that's the main thing someone sees when
they are in the API docs.
The status value comes from:
https://wiki.openstack.org/wiki/VersionDiscovery#status
Change-Id: I6dc5d8fd26d0981e5d83e829fe2dd09b7b9b4c17
Many releases ago, we supported the notion of having migration
repositories per backend interface. If a backend needed to use the
database, it could manage it's own migrations independently from the
rest of keystone. That functionality was removed long ago, and this
blurb of text should have been removed with it.
Change-Id: If90e25ec556cf42322509ef28878e96120b0baad
In lieu of new more complicated role system role collections tend to grow,
so extracting all roles to normalize/populate trust scope should be more
granular. This patch is a rework of role treating logic in trust controller.
Change-Id: Id6945ff9be23250d72909beceaa9cd73eebde04f
