Skip to content
This repository has been archived by the owner on Jun 26, 2024. It is now read-only.

[Discussion] Any issue with using SBO as dependency in other operator #1073

Closed
wtrocki opened this issue Nov 10, 2021 · 4 comments
Closed

[Discussion] Any issue with using SBO as dependency in other operator #1073

wtrocki opened this issue Nov 10, 2021 · 4 comments
Labels
kind/question Further information is requested

Comments

@wtrocki
Copy link

wtrocki commented Nov 10, 2021

Context:
redhat-developer/app-services-operator#290

Would adding ServiceBindingOperator as olm dependency case any issues for your team.

@wtrocki wtrocki added the kind/bug Something isn't working label Nov 10, 2021
@pedjak pedjak added kind/question Further information is requested and removed kind/bug Something isn't working labels Nov 10, 2021
@slemeur
Copy link

slemeur commented Nov 12, 2021

Not at all if we have proper integration tests and e2e tests.
What do you envision necessary for that? and how would we coordinate the effort?

cc @pmacik

@wtrocki
Copy link
Author

wtrocki commented Nov 12, 2021

No need for actions from sbo side. The only issue I could see are sandbox releases. we need to make sure we would not duplicate sbo in this scenario.
our team will check that. CC @secondsun

@wtrocki wtrocki closed this as completed Nov 12, 2021
@pedjak
Copy link
Contributor

pedjak commented Nov 12, 2021

No need for actions from sbo side. The only issue I could see are sandbox releases. we need to make sure we would not duplicate sbo in this scenario.

Right. Actually if an operator strongly depends on an API delivered by some other operator, then this should be declared in operator bundle, similar to how we do this in rpm/deb world.

@wtrocki
Copy link
Author

wtrocki commented Nov 12, 2021

Yes!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants