operator-controller
operator-controller copied to clipboard
operator-framework
Closes #1122 ## Reviewer Checklist - [ ] API Go Documentation - [ ] Tests: Unit Tests (and E2E Tests, if appropriate) - [ ] Comprehensive Commit Messages - [...
As outlined in the [Do not use Boolean Fields subsection of the OpenShift API Conventions](https://github.com/openshift/enhancements/blob/master/dev-guide/api-conventions.md#do-not-use-boolean-fields), boolean fields are to be replaced with an enumeration of values that describe the action...
As outlined in the [Use JSON Field Names in GoDoc subsection of the OpenShift API Conventions](https://github.com/openshift/enhancements/blob/master/dev-guide/api-conventions.md#use-json-field-names-in-godoc), field names referenced in the GoDoc should use the JSON field names. The updates...
# Approved Release Blockers - [ ] https://github.com/operator-framework/catalogd/issues/426 - [x] #1296 # Proposed Release Blockers # Non-blockers - [ ] #1307 - [ ] https://github.com/operator-framework/operator-controller/issues/1022 # Resolved - [x] https://github.com/operator-framework/operator-controller/issues/1239...
In order for us to support sourcing bundles directly, as is requested in #597, we need the ClusterExtension API to be structured such that one and exactly one sourcing mechanism...
As outlined in the [Write User Readable Documentation in the GoDoc subsection of the OpenShift API Conventions](https://github.com/openshift/enhancements/blob/master/dev-guide/api-conventions.md#write-user-readable-documentation-in-godoc), each field should be sufficiently documented such that an end user can answer:...