New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[operatorhub] Accept CatalogSource as a default source #300
[operatorhub] Accept CatalogSource as a default source #300
Conversation
c9c852a
to
cd7a436
Compare
/test e2e-aws-console-olm |
cd7a436
to
3fb15b9
Compare
pkg/defaults/catsrcHelpers.go
Outdated
strings.EqualFold(spec1.Address, spec2.Address) && | ||
strings.EqualFold(spec1.DisplayName, spec2.DisplayName) && | ||
strings.EqualFold(spec1.Publisher, spec2.Publisher) && | ||
strings.EqualFold(spec1.Image, spec2.Image) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should probably include the updatestrategy as well (updateStrategy.pollInterval
IIRC), so that we can update the default polling on these images
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ecordell addressed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good aside from Evan's comparison comment
/approve
pkg/defaults/catsrcHelpers.go
Outdated
) | ||
|
||
func ensureCatsrc(client wrapper.Client, config map[string]bool, catsrc olm.CatalogSource) error { | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
super nit: this space is not in style
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: anik120, kevinrizza The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
3fb15b9
to
85b94cd
Compare
/lgtm |
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/hold |
85b94cd
to
e57f16a
Compare
Updates OLM to 0.14.1
This PR enhances the OperatorHub API's capablity to accept a CatalogSource as a default source along with OperatorSource.
e57f16a
to
df1d951
Compare
/lgtm |
/hold cancel |
In operator-framework#300, the OperatorHub API was enhanced to accept both OperatorSource and CatalogSource as defaults. However, when an existing OperatorSource in a cluster was switched to a CatalogSource, the old OperatorSource persisted. This PR fixes the issue, and removes the obsolete OperatorSource, so that there's only one source for a catalog of operators.
In operator-framework#300, the OperatorHub API was enhanced to accept both OperatorSource and CatalogSource as defaults. However, when an existing OperatorSource in a cluster was switched to a CatalogSource, the old OperatorSource persisted. This PR fixes the issue, and removes the obsolete OperatorSource, so that there's only one source for a catalog of operators.
In operator-framework#300, the OperatorHub API was enhanced to accept both OperatorSource and CatalogSource as defaults. However, when an existing OperatorSource in a cluster was switched to a CatalogSource, the old OperatorSource persisted. This PR fixes the issue, and removes the obsolete OperatorSource, so that there's only one source for a catalog of operators.
In operator-framework#300, the OperatorHub API was enhanced to accept both OperatorSource and CatalogSource as defaults. However, when an existing OperatorSource in a cluster was switched to a CatalogSource, the old OperatorSource persisted. This PR fixes the issue, and removes the obsolete OperatorSource, so that there's only one source for a catalog of operators.
In operator-framework#300, the OperatorHub API was enhanced to accept both OperatorSource and CatalogSource as defaults. However, when an existing OperatorSource in a cluster was switched to a CatalogSource, the old OperatorSource persisted. This PR fixes the issue, and removes the obsolete OperatorSource, so that there's only one source for a catalog of operators.
In operator-framework#300, the OperatorHub API was enhanced to accept both OperatorSource and CatalogSource as defaults. However, when an existing OperatorSource in a cluster was switched to a CatalogSource, the old OperatorSource persisted. This PR fixes the issue, and removes the obsolete OperatorSource, so that there's only one source for a catalog of operators.
In operator-framework#300, the OperatorHub API was enhanced to accept both OperatorSource and CatalogSource as defaults. However, when an existing OperatorSource in a cluster was switched to a CatalogSource, the old OperatorSource persisted. This PR fixes the issue, and removes the obsolete OperatorSource, so that there's only one source for a catalog of operators.
Description of the change:
This PR enhances the OperatorHub API's capablity to accept a
CatalogSource as a default source along with OperatorSource.
Motivation for the change:
In Openshift 4.5, we want to be able to support both OperatorSources
and CatalogSources as default source types.
Reviewer Checklist
/docs