Add test that fails when `oadm migrate` is required
Open
Nobody has claimed this yet.
area/techdebt
lifecycle/frozen
priority/P2
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 4.8k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 53
Description
- Add a test that directly writes old versions of objects to etcd. When we remove support for a type, reading that type from etcd will fail and remind us that an
oadm migratestep is required for that release.
We should not need this for a while.
cc @liggitt @smarterclayton do we need anything else?
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
The issue names no file or existing test entry point. Start by locating tests for versioned objects, etcd storage, and oadm migrate; then determine how old objects are written and read. Done means a test fails when removed type support makes migration necessary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100