Skip to main content

equinix_fabric_route_filter_rules (Data Source)

Fabric V4 API compatible data resource that allow user to fetch route filter for a given search data set

Additional Documentation:

Example Usage​

data "equinix_fabric_route_filter_rules" "rf_rules" {
  route_filter_id = "<route_filter_policy_id"
  limit = 100
  offset = 5
}

output "first_route_filter_rule_name" {
  value = data.equinix_fabric_route_filter_rules.rf_rules.data.0.name
}

output "first_route_filter_rule_description" {
  value = data.equinix_fabric_route_filter_rules.rf_rules.data.0.description
}

output "first_route_filter_rule_prefix" {
  value = data.equinix_fabric_route_filter_rules.rf_rules.data.0.prefix
}

output "first_route_filter_rule_prefix_match" {
  value = data.equinix_fabric_route_filter_rules.rf_rules.data.0.prefix_match
}

Schema​

Required​

  • outer_operator (String) Determines if the filter list will be grouped by AND or by OR. One of [AND, OR]
  • route_filter_id (String) UUID of the Route Filter Policy the rule is attached to

Optional​

  • filter (Block List, Max: 8) Filters for the Data Source Search Request (see below for nested schema)
  • limit (Number) Number of elements to be requested per page. Number must be between 1 and 100. Default is 20
  • offset (Number) The page offset for the pagination request. Index of the first element. Default is 0.
  • sort (Block List) Sort criteria for the Data Source Search Request (see below for nested schema)

Read-Only​

  • data (List of Object) The list of Rules attached to the given Route Filter Policy UUID (see below for nested schema)
  • id (String) The ID of this resource.
  • pagination (Set of Object) Pagination details for the Data Source Search Request (see below for nested schema)

Nested Schema for filter​

Required:

  • operator (String) Operators to use on your filtered field with the values given. One of [ =, !=, LIKE, NOT LIKE, IN, NOT IN, ILIKE]
  • property (String) Possible field names to use on filters. One of [ /type, /name, /uuid, /state, /prefix]
  • values (List of String) The values that you want to apply the property+operator combination to in order to filter your data search

Nested Schema for sort​

Optional:

  • direction (String) The sorting direction. Can be one of: [DESC, ASC], Defaults to DESC
  • property (String) The property name to use in sorting. One of [/type /uuid /name /state /prefix /prefixMatch /changeLog/createdDateTime /changeLog/updatedDateTime]. Defaults to /changeLog/updatedDateTime

Nested Schema for data​

Read-Only:

  • action (String)
  • change (Set of Object) (see below for nested schema)
  • change_log (Set of Object) (see below for nested schema)
  • description (String)
  • href (String)
  • name (String)
  • prefix (String)
  • prefix_match (String)
  • state (String)
  • type (String)
  • uuid (String)

Nested Schema for data.change​

Read-Only:

  • href (String)
  • type (String)
  • uuid (String)

Nested Schema for data.change_log​

Read-Only:

  • created_by (String)
  • created_by_email (String)
  • created_by_full_name (String)
  • created_date_time (String)
  • deleted_by (String)
  • deleted_by_email (String)
  • deleted_by_full_name (String)
  • deleted_date_time (String)
  • updated_by (String)
  • updated_by_email (String)
  • updated_by_full_name (String)
  • updated_date_time (String)

Nested Schema for pagination​

Read-Only:

  • limit (Number)
  • next (String)
  • offset (Number)
  • previous (String)
  • total (Number)
Was this page helpful?