openstack/charm-cinder
Code Issues Proposed changes

Configure Cinder to use new audit middleware testing class

Browse Source 
Updated Cinder to use the new Keystone Audit Middleware testing class
in zaza-openstack-tests rather than the previous hardcoded functional
tests. This provides more flexibility and resiliency in the functional
testing of charms using the audit middleware feature.

func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1212
Change-Id: I63192c7db128e3d640e33911d8507cafddc3d5a0
This commit is contained in:
Myles Penner 2024-05-29 15:13:18 -07:00
parent e25b5d38fb
commit d6b92955c3
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
tests/tests.yaml
View File

@ -27,8 +27,11 @@ tests:
- zaza.openstack.charm_tests.cinder.tests.CinderTests
- zaza.openstack.charm_tests.cinder.tests.SecurityTests
- zaza.openstack.charm_tests.policyd.tests.CinderTests
- zaza.openstack.charm_tests.audit.tests.KeystoneAuditMiddlewareTest
tests_options:
audit-middleware:
service: cinder
policyd:
service: cinder
force_deploy: