You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: