planetscale / planetscale/vitess-operator
[`> v2.15.0`] Check resource spec before and after test upgrade
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 102
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 15
Description
Note to myself: once the next release (`v2.15.0`) is out, we should do that check before and after we upgrade.
Originally posted by @frouioui in https://github.com/planetscale/vitess-operator/pull/629#discussion_r1836896569
Contributor guide
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
The issue does not name a file or test; start by locating the test that upgrades the resource and the code that records its resource specification. Compare the specification before and after the v2.15.0 upgrade, and consider the work done when that comparison is covered by the test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100