According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: Iee69eae0043a401eb355a1fcb957879904882e85
After running tox -e py2, then there are many files named .coverage.*.
They should not have in the result of "git status" command.
Change-Id: I3ec3f9b8582f6a335ac42621c2273f6fb3433653
Closes-Bug: #1690002
This patch adds the basic framework for registering and using
default policy rules. Rules should be defined and returned from
a module in barbican/common/policies/, and then added to the
list in barbican/common/policies/__init__.py.
Also adds tox env to generate policy sample file.
Change-Id: If25b17ae7eed3f1a8e8e6f29701552a39d5a603f
etc/barbican/barbican.conf is generated when running tests with tox,
it's better to let repo ignore it.
Change-Id: I1f86cfd0bb20c678db62256203c48229a6380a6c
Currently etc/barbican/barbican.conf is maintained by hand and can not
be regenerated based on the config settings defined in the code.
A common pattern for OpenStack projects is to use oslo-config-generator
for that task.
Co-Authored-By: Randall Burt <randall.burt@rackspace.com>
Depends-On: I90870dcb49cd96f6bf0fe353fa6e779ffd87a5af
Closes-Bug: #1584789
Change-Id: I5f3dcd2fc982f1178ef7dd662c24d3166f91b266
Adds .ropeproject to .gitignore. .ropeproject is generated when
using python-rope for development.
Change-Id: I9ed402046892c3fcfb27a6a660819d933e5af8b2
This cycle, to address these problems for our ever-growing set of
projects, the release management team is introducing a new tool for
handling release notes as files in-tree, to allow us to simply and
continuously build the release notes for stable branch point releases
and milestones on the master branch. The idea is to use small YAML
files, usually one per note or patch, to avoid merge conflicts on
backports and then to compile those files in a deterministic way
into a more readable document for readers. Files containing release
notes can be including in patches directly, or you can create a
separate patch with release notes if you want to document a feature
than spans several patches. The tool is called Reno, and it currently
supports ReStructuredText and Sphinx for converting note input files
to HTML for publication. Reno is git branch-aware, so we can have
separate release notes documents for each release series published
together from the master build.
-- Excerpted from Doug Hellmann's email to the mailing list
http://lists.openstack.org/pipermail/openstack-dev/2015-November/078301.html
For more information about Reno:
http://docs.openstack.org/developer/reno/
Change-Id: I4028d52f5e67d2873b3dc9df279f78a15c35d84f
Add RST files to generate developer documentation using Sphinx. Also
add document build dependencies to test-requirements.txt.
Change-Id: Ie96ad02e0e5a6a8f92059b2a649851743830519d
Alembic migrations were introduced to Barbican a while ago but have not been
used recently. This CR revisits the migration logic and ensures that time-zero
database tables creation is distinguished from Alembic-base schema updates.
The associated database migration script is also revived, allowing for
schema migrations outside of the Barbican boot process.
Change-Id: I3e7fd7ac3f629da18329c22ad11cb9ccc1b7f9f9
Implements: blueprint db-revive-migrations
OpenStack uses pbr for setuptools/build and version releases. As
barbican looks towards incubation, migrate to being pbr based.
Change-Id: I3c7a389596ca579a5613ea98b21cdc6967e49cc7
Barbican must support RBAC on its various REST methods. This commit adds logic to enforce
RBAC rules defined in a policy.json to the REST resource API methods they need to
protect for unauthorized access. The implementation utilizes the latest oslo policy
module updates to read, parse and enforce RBAC rules.
Change-Id: I94b1709532540947ab3f1c9878c883a1fd167183
Implements: blueprint rbac-add-support