Infra/lemur
5
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
lemur/.gitignore

42 lines
516 B
Plaintext
Raw Normal View History

Closes #278 and #199, Starting transition to marshmallow (#299) * Closes #278 and #199, Starting transition to marshmallow
2016-05-05 12:52:08 -07:00
/.cache
initial commit
2015-06-22 13:47:27 -07:00
.coverage
.tox
.DS_Store
/.tmp/
*.egg-info
*.pyc
*.log
*.egg
*.db
*.pid
*.enc
Allow LetsEncrypt renewals and requesting certificates without specifying DNS provider
2018-08-13 14:22:59 -07:00
*.env
initial commit
2015-06-22 13:47:27 -07:00
MANIFEST
test.conf
pip-log.txt
reversing PR due to internal resolved addresses
2020-07-06 14:08:31 -07:00
package-lock.json
initial commit
2015-06-22 13:47:27 -07:00
/htmlcov
/cover
/build
/dist
/node_modules/
/bower_components/
/docs/html
/docs/doctrees
/lemur/static/dist/
/lemur/static/app/vendor/
/wheelhouse
- support multiple bundle configuration, nginx, apache, cert only - update vault destination to support multi cert under one object - added san list as key value - read and update object with new keys, keeping other keys, allowing us to keep an iterable list of keys in an object for deploying multiple certs to a single node
2019-02-25 09:42:07 -05:00
/lemur/lib
/lemur/bin
/lemur/lib64
/lemur/include
initial commit
2015-06-22 13:47:27 -07:00
docs/_build
.editorconfig
.idea
Add .pytest_cache dir to .gitignore (#1512)
2018-08-03 18:12:05 +03:00
.pytest_cache
Various minor cleanups and fixes (#938) * Documentation fixes * Various docstring and help string fixes * Minor code cleanups * Removed redundant .gitignore entry, ignored package-lock.json. * 'return' statement in certificates.service.render was redundant * Split up too long line * Non-matching tags in templates
2017-09-26 01:33:42 +03:00
lemur/tests/tmp
add per user api keys to the backend (#995) Adds in per user api keys to the backend of lemur. the basics are: - API Keys are really just JWTs with custom second length TTLs. - API Keys are provided in the exact same ways JWTs are now. - API Keys can be revoked/unrevoked at any time by their creator as well as have their TTL Change at anytime. - Users can create/view/list their own API Keys at will, and an admin role has permission to modify all api keys in the instance. Adds in support for lemur api keys to the frontend of lemur. doing this required a few changes to the backend as well, but it is now all working (maybe not the best way though, review will determine that). - fixes inconsistency in moduleauthor name I inputted during the first commit. - Allows the revoke schema to optionally allow a full api_key object. - Adds `/users/:user_id/api_keys/:api_key` and `/users/:user_id/api_keys` endpoints. - normalizes use of `userId` vs `userId` - makes `put` call respond with a JWT so the frontend can show the token on updating. - adds in the API Key views for clicking "API Keys" on the main nav. - adds in the API Key views for clicking into a users edit page. - adds tests for the API Key backend views I added.
2017-12-04 09:50:31 -07:00
/lemur/plugins/lemur_email/tests/expiration-rendered.html
/lemur/plugins/lemur_email/tests/rotation-rendered.html
Reference in New Issue Copy Permalink