Skip to content

Conversation

@pulledtim
Copy link
Contributor

No description provided.

@pulledtim pulledtim requested a review from wistefan August 26, 2025 09:47
Copy link
Collaborator

@wistefan wistefan left a comment

Choose a reason for hiding this comment

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

Why is it required to install the operator as "non-helm" in the local and test env? For a sequential startup, you could add a new execution to the helm-maven-plugin and render the operator into the infra folder. With the current solution, none of the two DB installations supported by the DSC is tested.

@pulledtim
Copy link
Contributor Author

Why is it required to install the operator as "non-helm" in the local and test env? For a sequential startup, you could add a new execution to the helm-maven-plugin and render the operator into the infra folder. With the current solution, none of the two DB installations supported by the DSC is tested.

Now deployed as separate step. Used the dsc chart as source to avoid multiple dependency versions while avoiding externalizing the dependency version.

@github-actions github-actions bot added the Stale label Oct 10, 2025
@github-actions github-actions bot closed this Oct 15, 2025
@wistefan wistefan reopened this Oct 22, 2025
@github-actions github-actions bot removed the Stale label Oct 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants