Skip to content

Conversation

benluddy
Copy link
Contributor

If present, operator property information needs to be persisted until
bundle unpacking completes so that properties can be projected onto
ClusterServiceVersions.

This is an artifact of the fact that the on-cluster representation of an installed operator (ClusterServiceVersion) is inflated from a manifest that is contained within a bundle. The need for this may eventually be obviated by directly writing to Operator resources, but given that the lack of property projection is responsible for fairly serious dependency resolution problems today, I think that this medium-term solution makes sense. I have written a brief summary of property projection here.

If present, operator property information needs to be persisted until
bundle unpacking completes so that properties can be projected onto
ClusterServiceVersions.
Copy link
Member

@ecordell ecordell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 24, 2020
@benluddy benluddy merged commit 00844b5 into operator-framework:master Sep 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants