Skip to content

Latest commit

 

History

History
46 lines (37 loc) · 2.23 KB

google_compute_router_nats.md

File metadata and controls

46 lines (37 loc) · 2.23 KB
Raw
title platform
About the google_compute_router_nats resource
gcp

Syntax

A google_compute_router_nats is used to test a Google RouterNat resource

Beta Resource

This resource has beta fields available. To retrieve these fields, include beta: true in the constructor for the resource

Examples

describe google_compute_router_nats(project: 'chef-gcp-inspec', region: 'europe-west2', router: 'inspec-gcp-router') do
  its('names') { should include 'inspec-router-nat' }
end

Properties

Properties that can be accessed from the google_compute_router_nats resource:

See google_compute_router_nat.md for more detailed information

  • names: an array of google_compute_router_nat name
  • nat_ip_allocate_options: an array of google_compute_router_nat nat_ip_allocate_option
  • nat_ips: an array of google_compute_router_nat nat_ips
  • drain_nat_ips: an array of google_compute_router_nat drain_nat_ips
  • source_subnetwork_ip_ranges_to_nats: an array of google_compute_router_nat source_subnetwork_ip_ranges_to_nat
  • subnetworks: an array of google_compute_router_nat subnetwork
  • min_ports_per_vms: an array of google_compute_router_nat min_ports_per_vm
  • udp_idle_timeout_secs: an array of google_compute_router_nat udp_idle_timeout_sec
  • icmp_idle_timeout_secs: an array of google_compute_router_nat icmp_idle_timeout_sec
  • tcp_established_idle_timeout_secs: an array of google_compute_router_nat tcp_established_idle_timeout_sec
  • tcp_transitory_idle_timeout_secs: an array of google_compute_router_nat tcp_transitory_idle_timeout_sec
  • log_configs: an array of google_compute_router_nat log_config
  • enable_endpoint_independent_mappings: an array of google_compute_router_nat enable_endpoint_independent_mapping
  • routers: an array of google_compute_router_nat router
  • regions: an array of google_compute_router_nat region

Filter Criteria

This resource supports all of the above properties as filter criteria, which can be used with where as a block or a method.

GCP Permissions

Ensure the Compute Engine API is enabled for the current project.