redhat-developer / redhat-developer/mapt
[Discussion] Timeout param to MaxLifeTime param
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
While I was working on limit the time for a cluster to come up I realize that the term used to define the time for auto destroy the cluster could be mislead as you may thing it could be the timeout for the actual operation (i.e. create the cluster) but not for time the resource should live...
As proposal we may change the name (from timeout to maxLifeTime) and may leave timeout to allow setting the max amount of time the execution can run before ends with error.
WDYT?
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 does not name any files, tests, or entry points. Search the Go code for uses of timeout and the cluster auto-destroy setting, then review the discussion before deciding whether the names and behaviors should be separated. Done requires an agreed proposal and corresponding tests, but the issue does not define that outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100