Closed Dostonbek1 closed 2 weeks ago
@Dostonbek1 I'm not familiar yet with the new pipeline to run e2e-ui, those failures are expected?
@Alex-Izquierdo the failures are not related to the API, there was a merge on the UI that introduced those failures; they are working on reverting it now. https://github.com/ansible/ansible-ui/pull/3023
e2d test run with an updated test suite: https://github.com/ansible/eda-server/actions/runs/10563200958
Look at the e2e test failures here, I would narrow in on:
The tests are getting 400 errors because the policies related to local resource management. Follow the config for the "stage" target...
You can set settings like:
The settings we want to change are:
ALLOW_LOCAL_ASSIGNING_JWT_ROLES
to TrueALLOW_SHARED_RESOURCE_CUSTOM_ROLES
to TrueAnd I think those would look like EDA__ALLOW_LOCAL_ASSIGNING_JWT_ROLES
.
Then you may want to apply those to all of your standalone environments. This may require a follow-up change to the aap-dev environment to set the back to false, but no one will even notice that's broken.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
Looks like the 1 e2e failure is unrelated, and the failures we hoped to fix are addressed by the rebase :+1:
This PR updates django-ansible-base to latest from devel branch, hash -
d0b961f