The quotas Python API has been refactored to extract the logic that traverses users and groups to get the attributes.
How to test this PR
The logic has not changed, only refactored, and it's covered by the user quotas unit tests.
An example to call the API is given also in the docs; in order to test it, need to configure keycloak to be reachable on port 8080 and the host to be configured as in the generated values.yaml file
Sanity checks:
[x] The pull request is explicitly linked to the relevant issue(s)
[x] The issue is well described: clearly states the problem and the general proposed solution(s)
[x] In this PR it is explicitly stated how to test the current change
[x] The labels in the issue set the scope and the type of issue (bug, feature, etc.)
[x] The relevant components are indicated in the issue (if any)
[x] All the automated test checks are passing
[x] All the linked issues are included in one Sprint
[x] All the linked issues are in the Review state
[x] All the linked issues are assigned
Breaking changes (select one):
[x] The present changes do not change the preexisting api in any way
[ ] This PR and the issue are tagged as a breaking-change and the migration procedure is well described above
Possible deployment updates issues (select one):
[x] There is no reason why deployments based on CloudHarness may break after the current update
[ ] This PR and the issue are tagged as alert:deployment
Test coverage (select one):
[x] Tests for the relevant cases are included in this pr
[ ] The changes included in this pr are out of the current test coverage scope
Documentation (select one):
[x] The documentation has been updated to match the current changes
[ ] The changes included in this PR are out of the current documentation scope
Closes CH-152
Implemented solution
The quotas Python API has been refactored to extract the logic that traverses users and groups to get the attributes.
How to test this PR
The logic has not changed, only refactored, and it's covered by the user quotas unit tests. An example to call the API is given also in the docs; in order to test it, need to configure keycloak to be reachable on port 8080 and the host to be configured as in the generated values.yaml file
Sanity checks:
Breaking changes (select one):
breaking-changeand the migration procedure is well described abovePossible deployment updates issues (select one):
alert:deploymentTest coverage (select one):
Documentation (select one):
Nice to have (if relevant):