salesforce / salesforce/rules_spring
Continue to add tools to the CLI
Nobody has claimed this yet.
- Dominant language
- Starlark
- Stars
- 257
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
I started the CLI project but then forgot about it.
https://github.com/salesforce/rules_spring/blob/main/springboot/cli.md
There is a debate how much should be added to the CLI, versus built directly into the build. Some tasks that could be done in the CLI:
- generate SBOM
- verify the internals of the springboot jar (essentially, packaging tests)
- extract OCI layers
The advantage of putting it in the CLI is that it keeps the rule/macro simpler. It also allows us to use the CLI tools with non-Bazel built springboot jars, which are also common in our company.
The advantags of putting it in the Bazel build is that they can be run in CI.
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 springboot/cli.md and review the existing CLI project. Compare the proposed tasks—SBOM generation, Spring Boot JAR internals verification, and OCI layer extraction—with the alternative of implementing them in the build. Done requires a decided scope and an agreed implementation location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- spring-boot
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100