pub struct GetAddressesArgsBuilder<S: State = Empty> { /* private fields */ }
Expand description
Use builder syntax to set the inputs and finish with build_struct()
.
Implementations§
source§impl<S: State> GetAddressesArgsBuilder<S>
impl<S: State> GetAddressesArgsBuilder<S>
sourcepub fn build_struct(self) -> GetAddressesArgswhere
S: IsComplete,
pub fn build_struct(self) -> GetAddressesArgswhere
S: IsComplete,
Finish building and return the requested object
sourcepub fn filter(
self,
value: impl Into<Output<Option<String>>>,
) -> GetAddressesArgsBuilder<SetFilter<S>>where
S::Filter: IsUnset,
pub fn filter(
self,
value: impl Into<Output<Option<String>>>,
) -> GetAddressesArgsBuilder<SetFilter<S>>where
S::Filter: IsUnset,
Optional (Some / Option setters). Default: <pulumi_wasm_rust::Output<Option<String>> as Default>::default()
.
A filter expression that filters resources listed in the response. The expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either “=”, “!=”, “>”, “<”, “<=”, “>=” or “:”. For example, if you are filtering Compute Engine instances, you can exclude instances named “example-instance” by specifying “name != example-instance”. The “:” operator can be used with string fields to match substrings. For non-string fields it is equivalent to the “=” operator. The “:” comparison can be used to test whether a key has been defined. For example, to find all objects with “owner” label use: “”“ labels.owner: “”“ You can also filter nested fields. For example, you could specify “scheduling.automaticRestart = false” to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: “”“ (scheduling.automaticRestart = true) (cpuPlatform = “Intel Skylake”) “”“ By default, each expression is an “AND” expression. However, you can include “AND” and “OR” expressions explicitly. For example: “”“ (cpuPlatform = “Intel Skylake”) OR (cpuPlatform = “Intel Broadwell”) AND (scheduling.automaticRestart = true)
sourcepub fn maybe_filter(
self,
value: Option<impl Into<Output<Option<String>>>>,
) -> GetAddressesArgsBuilder<SetFilter<S>>where
S::Filter: IsUnset,
pub fn maybe_filter(
self,
value: Option<impl Into<Output<Option<String>>>>,
) -> GetAddressesArgsBuilder<SetFilter<S>>where
S::Filter: IsUnset,
Optional (Some / Option setters). Default: <pulumi_wasm_rust::Output<Option<String>> as Default>::default()
.
A filter expression that filters resources listed in the response. The expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either “=”, “!=”, “>”, “<”, “<=”, “>=” or “:”. For example, if you are filtering Compute Engine instances, you can exclude instances named “example-instance” by specifying “name != example-instance”. The “:” operator can be used with string fields to match substrings. For non-string fields it is equivalent to the “=” operator. The “:” comparison can be used to test whether a key has been defined. For example, to find all objects with “owner” label use: “”“ labels.owner: “”“ You can also filter nested fields. For example, you could specify “scheduling.automaticRestart = false” to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based on resource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: “”“ (scheduling.automaticRestart = true) (cpuPlatform = “Intel Skylake”) “”“ By default, each expression is an “AND” expression. However, you can include “AND” and “OR” expressions explicitly. For example: “”“ (cpuPlatform = “Intel Skylake”) OR (cpuPlatform = “Intel Broadwell”) AND (scheduling.automaticRestart = true)