-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Add unit tests for OperatorSDK cmd layer #3246
Copy link
Copy link
Closed
Labels
area/testingIssue related to testing the operator-sdk and subcomponentsIssue related to testing the operator-sdk and subcomponentskind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone
Metadata
Metadata
Assignees
Labels
area/testingIssue related to testing the operator-sdk and subcomponentsIssue related to testing the operator-sdk and subcomponentskind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Feature Request
Per the discussion with @estroz and at the triage meeting on Monday, it would be nice if the cmd layer of OperatorSDK was thoroughly tested with golang unit tests. This is an umbrella issue to track progress on that work. It would be best to focus efforts on the commands that will be surviving the kubebuilder refactor, which I believe are the commands listed here.