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? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We need to exercise our Zarf install in a e2e test to make sure we are exercising branch of code.
The text was updated successfully, but these errors were encountered:
Relates to #1514
Sorry, something went wrong.
chore(testing): verify pepr can be deployed with zarf (#1531)
35bf589
## Description This PR adds a test to ensure pepr can be deployed with zarf. ## Related Issue Fixes #1516 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] 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
samayer12
Successfully merging a pull request may close this issue.
Describe what should be investigated or refactored
We need to exercise our Zarf install in a e2e test to make sure we are exercising branch of code.
The text was updated successfully, but these errors were encountered: