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
As described in #1261 (comment) OADP should not add nullable keys to CRDs' YAML files
Solution would be
remove hack from Makefile (seems the right one, as motivation was another tool that uses OADP needing that), as tried in feat: Nullable logic in code #1261
transform necessary fields in pointers, so they can be nil in Go (and null in YAML) (also removing hack)
The text was updated successfully, but these errors were encountered:
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.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
openshift-cibot
added
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Jan 22, 2025
As described in #1261 (comment) OADP should not add nullable keys to CRDs' YAML files
Solution would be
nil
in Go (andnull
in YAML) (also removing hack)The text was updated successfully, but these errors were encountered: