Allow a custom Executor as a parameter
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 85
- Forks
- 26
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 22
Description
Hello!
- Vote on this issue by adding a 👍 reaction
- If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
Logging a suggestion from one of our demos. We should make it possible for the user to pass a custom Executor and make everything in the Pulumi SDK use that executor. Currently we often use the default Executor. One possible scenario where this is interesting: a single-threaded Executor to debug concurrency issues.
Affected area/feature
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the pulumi-java SDK by locating where the default Executor is created and used. Review the issue's proposed custom Executor scenario and determine the API design needed to pass it through the SDK. Done means users can provide an Executor and SDK operations consistently use it, including a single-threaded implementation for debugging concurrency issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100