palantir / palantir/go-java-launcher
Output progress of start command
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 76
- Forks
- 29
- Avg merge
- 11h 34m
- Merged PRs (30d)
- 25
Description
What happened?
In my product, a sysadmin manually starts a "bootvisor" service using ./service/bin/init.sh start from an extracted tarball. Currently they get no output that the service started, so I'd like to give them some output.
Current
$ ./service/bin/init.sh start
$
Did it start? Did it fail on startup? Unknown
Proposed
$ ./service/bin/init.sh start
Started.
$
This doesn't have to happen all the time, I'd be happy to put it behind a flag for just this one service.
I first looked at sls-packaging, but the init.sh start script there just delegates to this go java launcher: https://github.com/palantir/sls-packaging/blob/587e544f6e8aad549d2567da5dba8dad61f5799d/gradle-sls-packaging/src/main/resources/init.sh#L60
Contributor guide
No contributing guide indexed for this repository
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 init.sh start entry point mentioned in the issue and trace its delegation into the Go Java launcher; the linked sls-packaging script provides context for that handoff. Determine how startup success or failure is reported and whether service-specific output can be enabled. Done means the start command clearly reports its result without changing unrelated services.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java, shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100