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
You can now use the `!=` and `==` operators when filtering workflows by namespace field.
7
+
This provides more flexible query capabilities, allowing you to easily exclude specific namespaces or match exact namespace values in your workflow queries.
8
+
For example, you can filter with `namespace!=kube-system` to exclude system namespaces or `namespace==production` to target only production environments.
"'namespace' query param (%q) and fieldselector 'metadata.namespace' (%q) are both specified and contradict each other", namespace, fieldSelectedNamespace)
114
+
}
115
+
} elseifafter, ok:=strings.CutPrefix(selector, "metadata.namespace="); ok {
100
116
// for backward compatibility, the field selector 'metadata.namespace' is supported for now despite the addition
101
117
// of the new 'namespace' query parameter, which is what the UI uses
returnnil, status.Error(codes.PermissionDenied, fmt.Sprintf("Permission denied, you are not allowed to list workflows in namespace \"%s\". Maybe you want to specify a namespace with query parameter `.namespace=%s`?", options.Namespace, options.Namespace))
201
+
returnnil, status.Error(codes.PermissionDenied, fmt.Sprintf("Permission denied, you are not allowed to list workflows in namespace \"%s\". Maybe you want to specify a namespace with query parameter `.namespace=%s`?", targetNamespace, targetNamespace))
assert.Equal(t, err, status.Error(codes.InvalidArgument, "'namespace' query param (\"user-ns\") and fieldselector 'metadata.namespace' (\"other-ns\") are both specified and contradict each other"))
0 commit comments