Optional. The filter to list result by.
General filter string syntax:
<field> <operator> <value> (<logical connector>)
<field> can be "name", or "labels.<key>" for map field.
<operator> can be "<, >, <=, >=, !=, =, :". Of which ":" means HAS, and
is roughly the same as "=".
<value> must be the same data type as field.
<logical connector> can be "AND, OR, NOT".
Examples of valid filters:
"labels.owner" returns Namespaces that have a label with the key "owner"
this is the same as "labels:owner".
"labels.protocol=gRPC" returns Namespaces that have key/value
"protocol=gRPC".
"name>projects/my-project/locations/us-east/namespaces/namespace-c"
returns Namespaces that have name that is alphabetically later than the
string, so "namespace-e" will be returned but "namespace-a" will not be.
"labels.owner!=sd AND labels.foo=bar" returns Namespaces that have
"owner" in label key but value is not "sd" AND have key/value foo=bar.
"doesnotexist.foo=bar" returns an empty list. Note that Namespace doesn't
have a field called "doesnotexist". Since the filter does not match any
Namespaces, it returns no results.
Optional. The filter to list result by.
General filter string syntax:
<field> <operator> <value> (<logical connector>)
<field> can be "name", or "labels.<key>" for map field.
<operator> can be "<, >, <=, >=, !=, =, :". Of which ":" means HAS, and
is roughly the same as "=".
<value> must be the same data type as field.
<logical connector> can be "AND, OR, NOT".
Examples of valid filters:
"labels.owner" returns Namespaces that have a label with the key "owner"
this is the same as "labels:owner".
"labels.protocol=gRPC" returns Namespaces that have key/value
"protocol=gRPC".
"name>projects/my-project/locations/us-east/namespaces/namespace-c"
returns Namespaces that have name that is alphabetically later than the
string, so "namespace-e" will be returned but "namespace-a" will not be.
"labels.owner!=sd AND labels.foo=bar" returns Namespaces that have
"owner" in label key but value is not "sd" AND have key/value foo=bar.
"doesnotexist.foo=bar" returns an empty list. Note that Namespace doesn't
have a field called "doesnotexist". Since the filter does not match any
Namespaces, it returns no results.
Optional. The order to list result by.
General order by string syntax:
<field> (<asc|desc>) (,)
<field> allows values {"name"}
<asc/desc> ascending or descending order by <field>. If this is left
blank, "asc" is used.
Note that an empty order_by string result in default order, which is order
by name in ascending order.
Optional. The order to list result by.
General order by string syntax:
<field> (<asc|desc>) (,)
<field> allows values {"name"}
<asc/desc> ascending or descending order by <field>. If this is left
blank, "asc" is used.
Note that an empty order_by string result in default order, which is order
by name in ascending order.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-27 UTC."],[],[]]
