Pulumi is not started from backed jar file
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 85
- Forks
- 26
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 22
Description
What happened?
I'm trying to run pulumi from precompiled jar file (following the guide here: https://github.com/pulumi/pulumi-java/ )
First I'm starting new project and could check that compilation is working and pulumi do the job.
Then I'm packaging exactly this project, and building farjar (repro guide is here: https://github.com/golosegor/pulumi-execute-from-jar-issue )
Then I'm trying to run pulumi with complid code from folder nearby: https://github.com/golosegor/pulumi-execute-from-jar-issue/blob/main/repro-folder/Pulumi.yaml and getting GRCP unavailable exception
Example
I've created a repro
https://github.com/golosegor/pulumi-execute-from-jar-issue
Output of pulumi about
CLI
Version 3.100.0
Go Version go1.21.5
Go Compiler gc
Plugins
NAME VERSION
java unknown
Host
OS ubuntu
Version 23.10
Arch x86_64
Additional context
Output looks like that:
I0109 14:52:54.785976 297662 log.go:81] GetRequiredPlugins: plugins=[]
I0109 14:52:54.796470 297662 log.go:81] Run: program=.
I0109 14:52:54.796485 297662 log.go:73] Language host launching process: /home/eg/.sdkman/candidates/java/current/bin/java-jar ../demo/target/demo-1.0-SNAPSHOT-jar-with-dependencies.jar
Jan 09, 2024 2:52:55 PM com.pulumi.deployment.internal.DeploymentImpl$DefaultEngineLogger errorAsync
SEVERE: Running program [PID: 297717](/home/eg/.sdkman/candidates/java/17.0.9-tem/bin/java -jar ../demo/target/demo-1.0-SNAPSHOT-jar-with-dependencies.jar) failed with an unhandled exception:
io.grpc.StatusRuntimeException: UNAVAILABLE: io exception
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
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 reproduction repository and repro-folder/Pulumi.yaml, then run the packaged jar through the Pulumi project as described in the report. Compare the successful compiled-project run with the far-jar run and trace the reported gRPC UNAVAILABLE failure. Done means the precompiled jar starts successfully from the nearby Pulumi project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100