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
Frankly, in it's current form I see no reason to include this method in the gem.
For it to be useful, it should by default do decryption and recursive lookup. And it should format it's out put as a array of simple name,value hashes. path should be a positional parameter, options a second positional parameter. This would allow user to override recursion or decryption, or add search filters, but not alter next_token behavior.
The text was updated successfully, but these errors were encountered:
ashleygould
changed the title
method parameters for path does not check for next_token
method parameters_for_path does not check for next_tokenFeb 13, 2021
If more than
MaxResults
params are available, this method will fail to retrieve all parameters.See
get_parameters_by_path
documentation in https://github.com/aws/aws-sdk-ruby/blob/master/gems/aws-sdk-ssm/lib/aws-sdk-ssm/client.rb (starting at line 5911)Also: https://docs.aws.amazon.com/sdk-for-ruby/v2/api/Aws/SSM/Client.html#get_parameters_by_path-instance_method
Frankly, in it's current form I see no reason to include this method in the gem.
For it to be useful, it should by default do decryption and recursive lookup. And it should format it's out put as a array of simple name,value hashes.
path
should be a positional parameter,options
a second positional parameter. This would allow user to override recursion or decryption, or add search filters, but not alter next_token behavior.example:
The text was updated successfully, but these errors were encountered: