feat(codegen): add user agent for non AWS clients #2415
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I had disabled user agent plugin for non AWS clients earlier as it depended on serviceId which is not present for non AWS services. This enables it back. serviceId is optional, so omitting it for non AWS services.
Testing
Added unit tests.
Generated client for non AWS service in demo package and looked at headers sent to the service by this client and compared with AWS service's client.
Demo service client:
where 1.0.0-rc.1 is the version of generated client in its package.json.
AWS service client (used AccessAnalyzerClient):
I assume for browser client, the
user-agent
header would not be there but thex-amz-user-agent
would be.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.