CronSchedule changes values on BackupConfig
Summary
When creating a BackupConfig and using the value */2
on the Base Backup Schedule section, those values are saved as:
- NaN/NaN,
- NaN,
- NaN/2, or
- */2
The values are not saved correctly. Although the values are not valid, there is no validation to prevent non valid values from being saved.
Steps to reproduce
- Create a new BackupConfig.
- Use
*/2
on every field on the Base Backup Schedule fields. - Save the BackupConfig.
- Go to the
Edit
section of the new BackupConfig. The values that were actually saved will appear. Those are NaN/NaN, NaN, NaN/2, or */2.
Expected Behaviour
- Values should be saved properly.
- There should be a validation to prevent non valid values from being saved.
Environment
- StackGres version: 1.0.0-RC1