-
Notifications
You must be signed in to change notification settings - Fork 192
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
aws_sdk_eventbridge
does not re-export HttpResponse
#3591
Comments
To solve your immediate problem, if you import |
I returning the result of the |
Yes. It's defaulted in the |
The solution which @jdisanti proposed is fine if one needs to use |
|
Can that approach be used to construct variants with the |
Have the same use-case as @klawson88. Would like to create a wrapper around |
## Motivation and Context #3591 ## Description In early days of smithy-rs, we used to re-export [Request](https://docs.rs/aws-sdk-s3/0.25.0/aws_sdk_s3/client/customize/struct.Request.html) and [Response](https://docs.rs/aws-sdk-s3/0.25.0/aws_sdk_s3/client/customize/struct.Request.html) types. When we overhauled the underlying smithy runtime from middleware to orchestrator, we did not re-export the corresponding types [HttpRequest](https://docs.rs/aws-smithy-runtime-api/latest/aws_smithy_runtime_api/client/orchestrator/type.HttpRequest.html) and [HttpResponse](https://docs.rs/aws-smithy-runtime-api/latest/aws_smithy_runtime_api/client/orchestrator/type.HttpResponse.html) to client crates. This PR will re-export them in `crate::config::http`. ## Testing Added a new test file for `ClientRuntimeTypesReExportGenerator.kt` that verifies re-exports. ## Checklist <!--- If a checkbox below is not applicable, then please DELETE it rather than leaving it unchecked --> - [x] I have updated `CHANGELOG.next.toml` if I made changes to the smithy-rs codegen or runtime crates - [x] I have updated `CHANGELOG.next.toml` if I made changes to the AWS SDK, generated SDK code, or SDK runtime crates ---- _By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice._
…es (#3762) ## Motivation and Context smithy-lang/smithy-rs#3591 ## Description In early days of smithy-rs, we used to re-export [Request](https://docs.rs/aws-sdk-s3/0.25.0/aws_sdk_s3/client/customize/struct.Request.html) and [Response](https://docs.rs/aws-sdk-s3/0.25.0/aws_sdk_s3/client/customize/struct.Request.html) types. When we overhauled the underlying smithy runtime from middleware to orchestrator, we did not re-export the corresponding types [HttpRequest](https://docs.rs/aws-smithy-runtime-api/latest/aws_smithy_runtime_api/client/orchestrator/type.HttpRequest.html) and [HttpResponse](https://docs.rs/aws-smithy-runtime-api/latest/aws_smithy_runtime_api/client/orchestrator/type.HttpResponse.html) to client crates. This PR will re-export them in `crate::config::http`. ## Testing Added a new test file for `ClientRuntimeTypesReExportGenerator.kt` that verifies re-exports. ## Checklist <!--- If a checkbox below is not applicable, then please DELETE it rather than leaving it unchecked --> - [x] I have updated `CHANGELOG.next.toml` if I made changes to the smithy-rs codegen or runtime crates - [x] I have updated `CHANGELOG.next.toml` if I made changes to the AWS SDK, generated SDK code, or SDK runtime crates ---- _By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice._
aws_sdk_eventbridge::operation::put_events::builders::PutEventsFluentBuilder::send
returns aResult<PutEventsOutput, SdkError<PutEventsError, HttpResponse>>
butHttpResponse
is not available without adding theaws-smithy-runtime-api
crate as a dependency.The text was updated successfully, but these errors were encountered: