You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
openshift-cibot
added
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
May 1, 2024
There are several time fields in DPA, some being
spec.configuration.velero.args.backup-sync-period
spec.configuration.velero.args.default-backup-ttl
spec.configuration.velero.args.default-item-operation-timeout
spec.configuration.velero.args.default-repo-maintain-frequency
spec.configuration.velero.args.fs-backup-timeout
spec.configuration.velero.args.garbage-collection-frequency
spec.configuration.velero.args.item-operation-sync-frequency
spec.configuration.velero.args.resource-timeout
spec.configuration.velero.args.store-validation-frequency
spec.configuration.velero.args.terminating-resource-timeout
spec.configuration.nodeAgent.timeout
spec.backupLocations[].velero.backupSyncPeriod
spec.configuration.velero.defaultItemOperationTimeout
spec.configuration.velero.resourceTimeout
And they are typed as
string
,metav1.Duration
andtime.Duration
.They should be all be the same type, for improved user and developer experience. They should also be validated in validators.
The text was updated successfully, but these errors were encountered: