zalando-incubator / zalando-incubator/stackset-controller
setting desired traffic to a non-existing version should fail
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 183
- Forks
- 29
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 5
Description
currently I can set traffic on a version that doesn't exist. It will correctly reduce the desired traffic to the existing versions but will not add the new version to the annotation (as it doesn't exist).
The actual traffic is not changed so it doesn't do much harm.
The client should probably fail or at least print something.
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
Start by tracing the traffic-setting path and how requested versions are checked against existing versions. Confirm the behavior for a nonexistent version and determine whether the expected outcome is a client error or a clear warning. Done means the invalid request is reported and does not silently alter desired traffic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100