-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#15: Update to use aws sdk v3 #16
Conversation
} | ||
|
||
params = await ssm.getParametersByPath(config).promise() | ||
nextToken = params.NextToken | ||
config.NextToken = nextToken |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure why here we invoked getParametersByPath()
once again - we could have simply used the token from the previous call. Pointing it out just in case it gets missed in the review and if you think there's a valid reason for it.
I have removed the duplicate call for now. Tests seem to pass
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch.
const name = param.Name.split('/') | ||
const svc = name[3] | ||
svcs[svc] = svcs[svc] ? svcs[svc] + 1 : 1 | ||
} | ||
|
||
params = await ssm.getParametersByPath(config).promise() | ||
nextToken = params.NextToken | ||
config.NextToken = nextToken |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same issue as the previous comment here as well
} | ||
|
||
params = await ssm.getParametersByPath(config).promise() | ||
nextToken = params.NextToken | ||
config.NextToken = nextToken |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch.
#15
Also contains