stackabletech / stackabletech/opa-operator
docs test unpredictable
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 21
- Forks
- 5
- Avg merge
- 12h 44m
- Merged PRs (30d)
- 11
Description
The docs tests are not awaiting an OPA update to test if the ConfigMap was loaded. This should be fixed somehow. Ideally we could know once the bundle is loaded, but it looks like we cannot know that, in that case we'd need to use a "sleep"
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 the docs test that checks whether the ConfigMap was loaded and inspect how it waits for the OPA update. Reproduce the timing failure, then make the test wait reliably for bundle loading or use the stated fallback; done means the test no longer depends on unpredictable timing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100