Skip to content

Conversation

@metacosm
Copy link
Collaborator

This allows to not run into compatibility between index versions.

public class ControllerManagerTest {

@Test(expected = OperatorException.class)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Are we using junit4 here?

Copy link
Collaborator

Choose a reason for hiding this comment

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

config(TestCustomResource.class), null));
}

@Test(expected = OperatorException.class)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Same here, this should be different in Junit5,

Copy link
Collaborator

@csviri csviri left a comment

Choose a reason for hiding this comment

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

JUnit5 should be used, ootherwise LGTM

While we originally planned to make it possible to register controllers
with the same CR but with different version (see #637), that behavior
should actually be forbidden since only one CR version can be served,
see #94 for more details.
@metacosm metacosm merged commit 0287c0c into master Oct 29, 2021
@metacosm metacosm deleted the fixes branch October 29, 2021 09:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

It should be possible to add controllers for different versions of the same CustomResource

3 participants