Account object creates an un-necessary request about cloud-client-ruby HOT 2 OPEN

While unideal, you can use the same workaround for passing {} into the Site class when constructing it. I'm not sure there's a nice compromise between fetching Site-object data and fetching other endpoint data for the Site APIs.

from cloud-client-ruby.

To me an ideal solution would be to make the initializer more specific:
Account.new(load:true), Account.new(load:false) or Account.new(data: {....}) with the first being the default.

A simpler alternative would be to allow an initializer of the form Account.new(false) which would be a small modification to CloudResource#initialize

from cloud-client-ruby.