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
[9] pry(main)> p = ec2_resource.vpc_peering_connection('pcx-12345678')
=> #<Aws::EC2::VpcPeeringConnection id="pcx-12345678">
[10] pry(main)> ls p
Aws::Resources::Resource#methods: client data data_loaded? exists? identifiers inspect load reload wait_until
Aws::EC2::VpcPeeringConnection#methods: accept accepter_vpc accepter_vpc_info delete expiration_time id reject requester_vpc requester_vpc_info status tags vpc_peering_connection_id
instance variables: @client @data @identifiers
[11] pry(main)> p.exists?
NotImplementedError: #exists? is not implemented for Aws::EC2::VpcPeeringConnection
from /Users/tball/.rvm/gems/ruby-2.1.6@cookbook-test-provisioning/gems/aws-sdk-resources-2.1.16/lib/aws-sdk-resources/resource.rb:139:in `rescue in exists?'
Because it inherits from Aws::Resources::Resource it looks like it should define exists?.
The text was updated successfully, but these errors were encountered:
The base resource class defines #exists? in such a way to raise the NotImplementError if the appropriate waiter definition does not exist. It relies on a waiter to check for the existence of the resource. I'll try to add a waiter that polls for the existence of a VPC peering connection and I'll share that shortly.
Because it inherits from
Aws::Resources::Resource
it looks like it should defineexists?
.The text was updated successfully, but these errors were encountered: