Support Package Name Override
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
I'm helping @NoamSternRedis with their Pulumi package and in-order to publish the Java package to maven, we need an escape hatch with pulumi-java-gen to override the package name.
Currently, using a combination of the package name in schema.json and BasePackage in resources.go, we're able to get com.redis.rediscloud - but we need this to be com.redis.pulumi-rediscloud, which currently isn't possible.
Affected area/feature
Codegen
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 by tracing package-name handling in pulumi-java-gen, including the schema.json package name and BasePackage in resources.go. Determine where an override can be exposed and verify that the generated Maven package can become com.redis.pulumi-rediscloud without breaking the existing behavior; the issue does not name a test file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100