Improved validation constraints for API signatures

[BarcoMasile]

Description

Added size constraints to API signatures validation

Changelog entry

How Has This Been Tested?

• manually
• all the test suits

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.)
• [ ] 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

In 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.

[BarcoMasile]

question: shouldn't the test reflect the newly introduced constraints somehow?

I'd say no since validators are part of the third library so since we have tests proving our mechanism (that relies on Marshmallow) works, then it's ok to assume they did their job also

[lazyoft]

question: shouldn't the test reflect the newly introduced constraints somehow?

I'd say no since validators are part of the third library so since we have tests proving our mechanism (that relies on Marshmallow) works, then it's ok to assume they did their job also

You are right. I'm ok with these changes.