Description of problem:
Able to provide any string in source repo
Version-Release number of selected component (if applicable):
mta-operator-bundle-container-6.2.0-24
How reproducible:
100%
Steps to Reproduce:
1. Analyze an application
2. On the Custom rules window -> Repository tab -> provide any string as "Source repository"
Actual results:
No error is shown. Git repo accepts any string and the Next button is enabled
Expected results:
URL validation should be enforced just like while creating a custom migration target
Attachments:
Screenshot
- mentioned on