I've considered guessing, but this proved problematic, as it is not possible to know if the 404 is a result of a no such bucket or no such key.
We need to change this in the docs to reflect the SDK will raise a NotFound.
@sirmxanot In the “Parameters” section of the #wait_until
method you linked documentaiton for, it indicates that the accepted waiter names and the operations they call are specified in the #waiter_names
method. It is linked from there. In the #waiter_names
method, it shows the API call being pulled and links to that:
For RDS:
http://docs.aws.amazon.com/sdkforruby/api/Aws/RDS/Client.html#waiter_names-instance_method
Aws.service()
or is there more to it? I am driving some operations that definitely need waiters and I would rather get them into the SDK than implement the semantics myself by hand.
Aws::Waiters::Errors::NoSuchWaiterError: no such waiter :instance_profile_available; valid waiter names are:
no matter what. Link: harvard-dce/aws-sdk-ruby@bd9510c
This is great for determining the underlying resource ID name. However CloudFormation.resources.json looks like this:
"Stack": {
"identifiers": [
{ "name": "Name" }
],
There's no memberName
to reveal the underlying name (e.g. "StackName"). Which example is the standard, and what is the best way to determine the underlying resource ID name?
KeyNames
vs. key_names