You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to improve automation in all repos for the Kuadrant components. We're aiming for:
good coverage of automation tasks related to code style, testing, CD/CD (image builds, releases), etc
consistency across components
automation as manageable code – i.e. less mouse clicks across scaterred UI "settings" pages and more Gitops, more YAMLs hosted as part of a code base.
As part of a preliminary investigation (#21) of the current state of such automation, the following desired workflows and corresponding status for the Kuadrant Operator repo were identified. Please review the list below.
A. Linters & Code style
A1. Built-in auto-format (go fmt, go vet, cargo fmt)
Workflows do not have to be implemented exactly as in the list. The list is just a driver for the kind of tasks we want to cover. Each component should assess it as it makes sense considering the component's specificities. More details in the original epic: #21.
You may also want to use this issue to reorganize how current workflows are implemented, thus helping us make the whole thing consistent across components.
We want to improve automation in all repos for the Kuadrant components. We're aiming for:
As part of a preliminary investigation (#21) of the current state of such automation, the following desired workflows and corresponding status for the Kuadrant Operator repo were identified. Please review the list below.
go fmt
,go vet
,cargo fmt
)go test
,cargo test
)Workflows do not have to be implemented exactly as in the list. The list is just a driver for the kind of tasks we want to cover. Each component should assess it as it makes sense considering the component's specificities. More details in the original epic: #21.
You may also want to use this issue to reorganize how current workflows are implemented, thus helping us make the whole thing consistent across components.
For an example of how Authorino and Authorino Operator intend to organise this for Golang code bases, see respectively Kuadrant/authorino#351 (comment) and Kuadrant/authorino-operator#96 (comment).
The text was updated successfully, but these errors were encountered: