Repository navigation
docs(api): clarify kind-wide Helm timeout overrides - #4493
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to The timeout wording clarifies how settings apply to an application kind. No actionable issue is established that would prevent merging. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review details
Pre-merge checks |
|
523cd4f to
5acee18
Compare
Aleksei Sviridkin (lexfrei)
left a comment
There was a problem hiding this comment.
∆Sergey∆ (@opsmon) LGTM. Every rewritten sentence matches the code. Both annotations are read only from the ApplicationDefinition (start.go:339-358), and the precedence in rest.go:1676-1684 is what the new text says: flag defaults first, then helm-install-timeout for both sides, then helm-upgrade-timeout for upgrade only. Only the two flag help strings reach users, and the touched packages build and vet clean.
Two optional nits. The reflow left a short line at start.go:329. Three test comments still say per-Application (rest_helmrelease_spec_test.go:207, rest_timeout_test.go:22 and :140).
Head branch was pushed to by a user without write access
5acee18 to
9c7fbe8
Compare
Aleksei Sviridkin (lexfrei)
left a comment
There was a problem hiding this comment.
∆Sergey∆ (@opsmon) LGTM. The new test comments and the reflowed start.go comment match the code. The annotations are read only from the ApplicationDefinition (start.go:339-358), and the upgrade timeout overrides the install one (rest.go:1676-1684). Build, vet and the timeout tests are clean.
Timeout annotations are read from an ApplicationDefinition and therefore affect every Application of that kind. Describing them as per-Application hides their actual scope and the upgrade override precedence. Fixes cozystack#4382 Assisted-by: LLM Signed-off-by: frolov.so <[email protected]>
9c7fbe8 to
9b35fa0
Compare
What this PR does
Clarifies that Helm install and upgrade timeout annotations are configured on an ApplicationDefinition and apply to every Application of that kind.
It also documents that the upgrade-specific timeout takes precedence over the shared install timeout and the global upgrade default.
Fixes #4382
Screenshots
N/A — this change only updates comments and CLI help text.
Downstream repositories
Release note
Summary by CodeRabbit
ApplicationDefinition, rather than per Application.