Skip to content
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.

Sign up for GitHub

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

Jump to bottom

I cannot build s3 with smithy-rs #3852

Closed
Alfiec7113 opened this issue Sep 27, 2024 · 2 comments
Closed

I cannot build s3 with smithy-rs #3852

Alfiec7113 opened this issue Sep 27, 2024 · 2 comments

Comments

@Alfiec7113
Copy link

Alfiec7113 commented Sep 27, 2024 •
edited
Loading

I tried using the example

This is the only service I've not been able to build.

On both windows and Ubuntu
gradlew -Paws.sdk.models.path=../aws-sdk-rust/aws-models -Paws.services=+s3 :aws:sdk:assemble

image
@ysaito1001 ysaito1001 mentioned this issue Oct 4, 2024
Merged
1 task
@ysaito1001
Copy link
Contributor

Hi @Alfiec7113, thank you for reporting this issue! I have submitted a fix to correct those ./gradlew incantations.

Let us know if that does not fix the issue on your end.

github-merge-queue bot pushed a commit that referenced this issue Oct 4, 2024
@ysaito1001
Fix AWS SDK generation examples in aws/sdk README (#3862)
796ec3a 
## Motivation and Context
#3852 

## Testing
Manually executed the updated examples and confirmed they passed on my
mac.

## Checklist
<!--- If a checkbox below is not applicable, then please DELETE it
rather than leaving it unchecked -->
- [x] For changes to the smithy-rs codegen or runtime crates, I have
created a changelog entry Markdown file in the `.changelog` directory,
specifying "client," "server," or both in the `applies_to` key.

Even though the fix is for AWS SDK code generation examples, I think the
release notes for the fix should only appear in the `smithy-rs`
repository. Customers subscribing to the `aws-sdk-rust` repository
should not need to know.

----

_By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice._
@ysaito1001
Copy link
Contributor

The fixed merged and the README has been updated in the main branch. Again, feel free to reopen if you still encouter the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ysaito1001 @Alfiec7113