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
#2832 (#2588) introduced the WritableOperation interface which extends the Editable interface.
This allows NonNamespaceOperation to perform edit method calls when neither the item or the name of the resource has been specified. This is not allowed.
…ations shouldn't be allowed in NonNamespaceOperation (fabric8io#3772)
Remove reference to `WritableOperation<T>` interface from
NonNamespaceOperation as it exposes `edit()`, `patch()` and other
mutating operations.
Signed-off-by: Rohan Kumar <rohaan@redhat.com>
…ations shouldn't be allowed in NonNamespaceOperation (#3772)
Remove reference to `WritableOperation<T>` interface from
NonNamespaceOperation as it exposes `edit()`, `patch()` and other
mutating operations.
Signed-off-by: Rohan Kumar <rohaan@redhat.com>
…ations shouldn't be allowed in NonNamespaceOperation (#3772)
Remove reference to `WritableOperation<T>` interface from
NonNamespaceOperation as it exposes `edit()`, `patch()` and other
mutating operations.
Signed-off-by: Rohan Kumar <rohaan@redhat.com>
(cherry picked from commit 89ec394)
manusa
changed the title
edit() should not be allowed as a NonNamespaceOperation
edit() should not be allowed as a ~~NonNamespaceOperation~~
Apr 5, 2022
Describe the bug
#2832 (#2588) introduced the
WritableOperation
interface which extends theEditable
interface.This allows NonNamespaceOperation to perform edit method calls when neither the item or the name of the resource has been specified. This is not allowed.
Operations such as:
should not be possible.
Fabric8 Kubernetes Client version
5.2.0 onwards
Expected behavior
Runtime
other (please specify in additional context)
Kubernetes API Server version
other (please specify in additional context)
Environment
other (please specify in additional context)
Fabric8 Kubernetes Client Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: