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
Is your feature request related to a problem? Please describe.
Pepr pods are taking too long to be ready. We need to boot the store faster. This is intentionally vague because a spike needs to be done to see how to achieve this.
After chatting with team:
Make configurable
Remove Math.random to a constant
Make loop for setupWatch
Make sure there is good logging
Describe the solution you'd like
Given a fresh Pepr pod is deployed
When it is time to boot the store
Then it is done in the fastest way possible
Describe alternatives you've considered
(optional) A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
## Description
Reduces start time by 66.6% by creating the store faster.
## Related Issue
Fixes#645
<!-- 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] Test, docs, adr added or updated as needed
- [x] [Contributor Guide
Steps](https://github.com/defenseunicorns/pepr/blob/main/CONTRIBUTING.md#submitting-a-pull-request)
followed
Signed-off-by: Case Wylie <cmwylie19@defenseunicorns.com>
Is your feature request related to a problem? Please describe.
Pepr pods are taking too long to be ready. We need to boot the store faster. This is intentionally vague because a spike needs to be done to see how to achieve this.
After chatting with team:
Describe the solution you'd like
Describe alternatives you've considered
(optional) A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: