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.

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

Can't sequentially bootstrap more than one SDK client #1189

Closed
lauzadis opened this issue Jan 22, 2024 · 2 comments · Fixed by #1202
Closed

Can't sequentially bootstrap more than one SDK client #1189

lauzadis opened this issue Jan 22, 2024 · 2 comments · Fixed by #1202
Labels
bug This issue is a bug.

Comments

@lauzadis
Copy link
Member

Describe the bug

When trying to bootstrap a second SDK client after one has already been bootstrapped, the task succeeds but there is no client generated.

Expected behavior

The second client should be bootstrapped.

Current behavior

The bootstrap task succeeds but does not actually generate a client.

Steps to Reproduce

./gradlew --no-daemon -Paws.kotlin.native=false -Paws.services=lambda :codegen:sdk:bootstrap
# observe lambda client is generated
./gradlew --no-daemon -Paws.kotlin.native=false -Paws.services=ec2 :codegen:sdk:bootstrap
# observe task succeeds, but there is no EC2 client

Possible Solution

The bug is related to Gradle caching the generateSmithyBuild task results. I noticed this in the logs: Task :codegen:sdk:generateSmithyBuild UP-TO-DATE.

Adding a --rerun-tasks flag to the bootstrap command fixes the issue, but this problem should be fixed in the Gradle task itself.

Context

No response

AWS Kotlin SDK version used

1.0.40-SNAPSHOT

Platform (JVM/JS/Native)

JVM

Operating System and version

MacOS

@lauzadis lauzadis added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. and removed needs-triage This issue or PR still needs to be triaged. labels Jan 22, 2024
@aajtodd
Copy link
Collaborator

aajtodd commented Jan 22, 2024

Yeah I noticed this recently as well I think, this may be fixed in a WIP branch.

Copy link

github-actions bot commented Feb 6, 2024

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants