-
Notifications
You must be signed in to change notification settings - Fork 2
feat: Add UI regex-validation #349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
/run pipeline |
|
/run pipeline |
| { | ||
| "type": "regex", | ||
| "description": "The value provided for 'backup_crn' is not valid.", | ||
| "value": "^__NULL__$|^crn:.*:backup:" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be improved? The CRN format is well defined, whilst the .* is vague. Can we at least make sure backup in the appropriate block. eg. (.*:){x}
| { | ||
| "type": "regex", | ||
| "description": "The value provided for 'backup_crn' is not valid.", | ||
| "value": "^__NULL__$|^crn:.*:backup:" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be improved? The CRN format is well defined, whilst the .* is vague. Can we at least make sure backup in the appropriate block. eg. (.*:){x}


















Description
Add UI regex valiadation in ibm_catalog.json.
Release required?
x.x.X)x.X.x)X.x.x)Release notes content
This PR enables input validation in the UI for several string variables by leveraging the value_constraints array defined in the catalog. These constraints will be used by the UI to validate user input at runtime. The changed variables include:
prefix,existing_secrets_manager_instance_crn,existing_kms_instance_crn,existing_kms_key_crn,backup_crn,existing_backup_kms_key_crn,existing_mysql_instance_crn,remote_leader_crn.Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers