This PR introduces the only missing endpoint validation (the PC API proxy) and switches away from the flask-restful approach for defining resources. This was done because this dependency was only needed for two locations in the code and doesn't bring any value to project at the moment.
How Has This Been Tested?
manually, by triggering post, delete and get operations on the PC API
unit tests
e2e
References
PR Quality Checklist
[ ] I added tests to new or existing code
[ ] I removed hardcoded strings and used our i18n solution instead (see here)
[x] I made sure no sensitive info gets logged at any time in the codebase (see here) (e.g. no user info or details, no stacktraces, etc.)
[x] I checked that infrastructure/update_infrastructure.sh runs without any error
[x] I checked that npm run build builds without any error
[x] I checked that clusters are listed correctly
[x] I checked that a new cluster can be created (config is produced and dry run passes)
[x] I checked that login and logout work as expected
Description
This PR introduces the only missing endpoint validation (the PC API proxy) and switches away from the flask-restful approach for defining resources. This was done because this dependency was only needed for two locations in the code and doesn't bring any value to project at the moment.
How Has This Been Tested?
References
PR Quality Checklist
i18nsolution instead (see here)npm run buildbuilds without any errorIn order to increase the likelihood of your contribution being accepted, please make sure you have read both the Contributing Guidelines and the Project Guidelines
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.