Respect replaceOnChanges in SDK generation
Open
Nobody has claimed this yet.
kind/enhancement
- 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
For example here is what Node generator does:
https://github.com/pulumi/pulumi/blob/244d262af57e671620963abf069f7ac76068f15c/pkg/codegen/testing/test/testdata/replace-on-change/nodejs/cat.ts#L70-#L70
Per @mjeffryes this is not yet done for Java SDK generation. Important to include.
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 with the Node example in pkg/codegen/testing/test/testdata/replace-on-change/nodejs/cat.ts, then trace the corresponding Java SDK generation path and its tests. Confirm how replaceOnChanges is represented for Java and consider the feature complete when generated Java SDKs respect that setting like the Node generator.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100