|Zuul c402d70e47 Merge "Remove tox environment py27 and add py36"||6 days ago|
|airship_tempest_plugin||7 months ago|
|.gitignore||2 weeks ago|
|.gitreview||2 weeks ago|
|.zuul.yaml||2 weeks ago|
|README.rst||9 months ago|
|requirements.txt||2 weeks ago|
|setup.cfg||1 week ago|
|setup.py||9 months ago|
|test-requirements.txt||9 months ago|
|tox.ini||1 week ago|
The purpose of this plugin is to provide automated tests for all OpenStack Airship components.
This initial implementation is just to meet the first use case which is RBAC testing. For RBAC testing, we only need to hit the API endpoint and check role permission to the API being tested. Some of the REST clients will need to be rewritten if functional testing is desired. Those that need to be rewritten are documented in each service client code.
Testing can be done in a airship-in-a-bottle environment. Please refer to  and . Tempest and Tempest plugin installation can be done in a Python virtual environment.
Patrole documentation for requirements driven approach that is used: https://github.com/openstack/patrole/blob/master/doc/source/framework/requirements_authority.rst Patrole role-overriding: https://github.com/openstack/patrole/blob/master/doc/source/framework/rbac_utils.rst#role-overriding Patrole under-permission exception: https://github.com/openstack/patrole/blob/master/patrole_tempest_plugin/rbac_exceptions.py#L51 Patrole over-permission exception: https://github.com/openstack/patrole/blob/master/patrole_tempest_plugin/rbac_exceptions.py#L44
Future Considerations: ---------------------Will the airship-tempest-plugin continue to live here: https://github.com/att-comdev/airship-tempest-plugin or will it be moved under OpenStack? Will there exist a RBAC gate for all Airship projects?