barbican/.gitignore
Thomas Bechtold 06b76aa6e8 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
2017-04-05 08:02:35 +02:00

75 lines
737 B
Plaintext

.venv
.python-version
*.sqlite
*.py[cod]
# C extensions
*.so
# Packages
*.egg
.eggs
*.egg-info
dist
build
eggs
parts
var
sdist
develop-eggs
.installed.cfg
lib
lib64
# Installer logs
pip-log.txt
*.err.log
# Unit test / coverage reports
cover
.testrepository
.coverage
.tox
nosetests.xml
coverage.xml
flake8.log
# Translations
*.mo
# Mr Developer
.mr.developer.cfg
.project
.pydevproject
# Pycharm
.idea
*.iml
# Sqlite databases
*.sqlite3
*.db
# Misc. generated files
versiononly.txt
*.orig
myapp.profile
*.out.myapp
AUTHORS
ChangeLog
# Editors
*~
.*.swp
# Mac OS
.DS_Store
# Rope
.ropeproject
# files created by oslo-config-generator
etc/barbican/barbican.conf.sample
# Files created by releasenotes build
releasenotes/build