c750fd6d6c
CONFspirator was written to just specifically for Adjutant and it allows us to do oslo.config style config management and definition with nested groups and for yaml. This is a major change that touches vast amounts of the code simply because of how much the config touches. Actions, Tasks, DelegateAPIs, and Notification Handlers now can define config in their own class and this will be added to the config. All the other config is located in `adjutant.config`, with everything now registed nicely on the config tree, and grouped in much saner ways. CONFspirator will also now allow Adjutant to be entirely configured via environment variables. We have removed `modify_dict_settings` because that is now entirely handled by CONFspirator's test utils. `NotificationEngine`s are now `NotificationHandler`s. `test_settings.py` is gone! And we now have better ways to define test settings and defaults. Project line length bumped to 88, and bugbear added to enforce that instead. Story: 2004488 Change-Id: I1d97d72d06b3a3a5df90355d3a4b4fe414381424
Team and repository tags
Adjutant
A basic workflow framework built using Django and Django-Rest-Framework to help automate basic Admin tasks within an OpenStack cluster.
Primarily built as user registration service that fits into the OpenStack ecosystem alongside Keystone, its purpose to fill functionality missing from Keystone. Ultimately it is just a framework with actions that are tied to an endpoint and can require certain data fields and perform actions via the OpenStack clients as well as talk to external systems as needed.
Useful for automating generic admin tasks that users might request but otherwise can't do without the admin role. Also allows automating the signup and creation of new users, but also allows such requests to require approval first if wanted. Due to issuing of uri+tokens for final steps of some actions, allows for a password submit/reset system as well.
Documentation
Documentation can be found at: https://docs.openstack.org/adjutant/latest
Documentation is stored in doc/, a sphinx build of the documentation can be generated with the command tox -e docs.
An API Reference is stored in api-ref. This is also a sphinx build and can be generated with tox -e api-ref.