openstack/barbican
Code Issues Proposed changes
8443b878a7
barbican/.gitignore

85 lines
928 B
Plaintext
Raw Normal View History

Cleaned up repo/model/config files to be more like Glance;
2013-04-12 17:44:03 -05:00
.venv
Update .gitignore for pyenv Add .python-version to .gitignore file so that you can use pyenv local for barbican. Change-Id: I2b2bb01838c2d3c8d30266a1dd2f369bf2a8572c
2016-02-09 10:33:58 -06:00
.python-version
Cleaned up repo/model/config files to be more like Glance;
2013-04-12 17:44:03 -05:00
*.sqlite
Initial commit
2013-02-11 05:32:30 -08:00
*.py[cod]
# C extensions
*.so
# Packages
*.egg
hide the eggs newer versions of setuptools now create an "eggs" directory Change-Id: I3aefc11df71757fb69b3ecf9f90d0a3adf8898f8
2015-03-09 15:04:55 -05:00
.eggs
Initial commit
2013-02-11 05:32:30 -08:00
*.egg-info
dist
build
eggs
parts
var
sdist
develop-eggs
.installed.cfg
lib
lib64
# Installer logs
pip-log.txt
Adding err.log to git ignore list; Remove spurious log;
2013-05-24 17:41:05 -05:00
*.err.log
Initial commit
2013-02-11 05:32:30 -08:00
# Unit test / coverage reports
Revive Alembic-based database migration logic. 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
2014-03-24 23:31:49 -05:00
cover
Switch to stestr 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
2018-07-11 15:05:28 +07:00
.stestr/
Initial commit
2013-02-11 05:32:30 -08:00
.coverage
Creating redundancy files when running tox 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
2017-05-12 13:47:06 +07:00
.coverage.*
Initial commit
2013-02-11 05:32:30 -08:00
.tox
Address issue with oslo config rejecting cli options for logging
2013-04-16 18:19:53 -05:00
coverage.xml
Add role based access control (RBAC) to Barbican 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
2013-08-15 00:06:40 -05:00
flake8.log
Initial commit
2013-02-11 05:32:30 -08:00
# Translations
*.mo
# Mr Developer
.mr.developer.cfg
.project
.pydevproject
Flask Structure Created basic structure for a Flask app.
2013-02-16 13:22:46 -06:00
# Pycharm
.idea
Ignore IntelliJ module files.
2013-04-30 13:05:47 -05:00
*.iml
Adding SQLAlchemy persistence Basic structure for SQLAlchemy and models. Uses a hardcoded DB location which should be moved to a standard configuration.
2013-02-16 19:10:11 -06:00
# Sqlite databases
*.sqlite3
*.db
Merge of previous project work into this project
2013-04-01 18:26:03 -05:00
# Misc. generated files
versiononly.txt
Adding files to support database migration via alembic. Change-Id: I57b6b62ec6da37608729fb353dce73971a419722
2013-07-05 09:40:53 -05:00
*.orig
myapp.profile
*.out.myapp
Migrate to pbr OpenStack uses pbr for setuptools/build and version releases. As barbican looks towards incubation, migrate to being pbr based. Change-Id: I3c7a389596ca579a5613ea98b21cdc6967e49cc7
2013-12-06 17:31:02 +02:00
AUTHORS
ChangeLog
Add Sphinx developer documentation skeleton Add RST files to generate developer documentation using Sphinx. Also add document build dependencies to test-requirements.txt. Change-Id: Ie96ad02e0e5a6a8f92059b2a649851743830519d
2014-04-29 23:42:30 -05:00
# Editors
*~
.*.swp
Increased test coverage for app and updated .gitignore Change-Id: Ib8ad16a04682674c52d97fbe80ae7ccf62648b74
2014-06-30 15:15:57 -05:00
# Mac OS
.DS_Store
Add reno for release notes management 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
2015-11-30 10:57:55 -05:00
Add .ropeproject to .gitignore Adds .ropeproject to .gitignore. .ropeproject is generated when using python-rope for development. Change-Id: I9ed402046892c3fcfb27a6a660819d933e5af8b2
2017-01-28 05:17:25 +00:00
# Rope
.ropeproject
Use oslo-config-generator to generate barbican.conf.sample 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
2016-07-11 19:41:28 +02:00
# files created by oslo-config-generator
Update .gitignore to ignore barbican.conf etc/barbican/barbican.conf is generated when running tests with tox, it's better to let repo ignore it. Change-Id: I1f86cfd0bb20c678db62256203c48229a6380a6c
2017-04-12 10:21:20 +08:00
etc/barbican/barbican.conf
Use oslo-config-generator to generate barbican.conf.sample 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
2016-07-11 19:41:28 +02:00
etc/barbican/barbican.conf.sample
Add .ropeproject to .gitignore Adds .ropeproject to .gitignore. .ropeproject is generated when using python-rope for development. Change-Id: I9ed402046892c3fcfb27a6a660819d933e5af8b2
2017-01-28 05:17:25 +00:00
Maintain policy in code 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
2017-02-09 18:19:15 +08:00
# File created by oslopolicy-sample-generator
etc/barbican/policy.yaml.sample
Add reno for release notes management 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
2015-11-30 10:57:55 -05:00
# Files created by releasenotes build
releasenotes/build
Initial commit for Barbican api-ref Change-Id: Ie67aae021efc835d4a1fb5bbfffb8761ea41a3b4 Closes-Bug: #1667053
2017-02-23 21:14:35 +08:00
# Files created by API build
api-ref/build/
Add sample config and policy to documentation Change-Id: Ie21459821dbe654d5e097494efbfbd647c12044e
2018-01-24 17:03:54 +08:00
# Files created by doc build
doc/source/_static
Copy Permalink