service/finspace: Fix SDK's ContentType sent for requests #3896
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
skmcgrail
approved these changes
May 4, 2021
skotambkar
approved these changes
May 4, 2021
Updates the service/finspace and service/finspacedata to send the expected Content-Type value for requests.
jasdel
force-pushed
the
fixup/FinspaceHeaders
branch
from
125fe12
to
f75b428
Compare
jasdel
force-pushed
the
fixup/FinspaceHeaders
branch
from
f75b428
to
dccd80f
Compare
aws-sdk-go-automation
pushed a commit
that referenced
this pull request
May 5, 2021
=== ### Service Client Updates * `service/auditmanager`: Updates service API and documentation * `service/kinesisanalyticsv2`: Updates service API and documentation * `service/nimble`: Updates service documentation * `service/sagemaker`: Updates service API and documentation * Amazon SageMaker Autopilot now provides the ability to automatically deploy the best model to an endpoint ### SDK Bugs * `service/finspace`: Fix Content-Type header sent in request ([#3896](#3896)) * Fixes the Content-Type header sent by the SDK in requests to the API * `service/finspacedata`: Fix Content-Type header sent in request ([#3896](#3896)) * Fixes the Content-Type header sent by the SDK in requests to the API
Merged
aws-sdk-go-automation
added a commit
that referenced
this pull request
May 5, 2021
Release v1.38.34 (2021-05-05) === ### Service Client Updates * `service/auditmanager`: Updates service API and documentation * `service/kinesisanalyticsv2`: Updates service API and documentation * `service/nimble`: Updates service documentation * `service/sagemaker`: Updates service API and documentation * Amazon SageMaker Autopilot now provides the ability to automatically deploy the best model to an endpoint ### SDK Bugs * `service/finspace`: Fix Content-Type header sent in request ([#3896](#3896)) * Fixes the Content-Type header sent by the SDK in requests to the API * `service/finspacedata`: Fix Content-Type header sent in request ([#3896](#3896)) * Fixes the Content-Type header sent by the SDK in requests to the API
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updates the service/finspace and service/finspacedata to send the expected Content-Type value for requests.