We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
We need to protect our cli commands, we currently do not have a mechanism for testing these and they require manual testing.
The text was updated successfully, but these errors were encountered:
chore: pepr build custom image (#1401)
29d1c8f
## Description Builds a Pepr module and read manifests from known locations to assert that the custom image was used. CI test for `npx pepr build --custom-image' End to End Test: <!-- if applicable --> (See [Pepr Excellent Examples](https://github.com/defenseunicorns/pepr-excellent-examples)) ## Related Issue Fixes #1370 <!-- or --> Relates to # ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [x] Other (security config, docs update, etc) ## Checklist before merging - [x] Unit, [Journey](https://github.com/defenseunicorns/pepr/tree/main/journey), [E2E Tests](https://github.com/defenseunicorns/pepr-excellent-examples), [docs](https://github.com/defenseunicorns/pepr/tree/main/docs), [adr](https://github.com/defenseunicorns/pepr/tree/main/adr) added or updated as needed - [x] [Contributor Guide Steps](https://docs.pepr.dev/main/contribute/#submitting-a-pull-request) followed --------- Signed-off-by: Case Wylie <cmwylie19@defenseunicorns.com>
cmwylie19
Successfully merging a pull request may close this issue.
Is your feature request related to a problem? Please describe.
We need to protect our cli commands, we currently do not have a mechanism for testing these and they require manual testing.
Describe the solution you'd like
The text was updated successfully, but these errors were encountered: