Skip to content
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

Fix IRI *-broker status #1169

Conversation

so-sahu
Copy link
Contributor

@so-sahu so-sahu commented Nov 22, 2024

Proposed Changes

This PR addresses an issue in the getTargetIronCoreMachinePools method within the broker status IRI response. Currently, the method retrieves and returns a list of all MachinePools in the cluster, even when a specific MachinePool is provided. This behavior occurs due to a missing return statement when a single MachinePool is fetched.

@so-sahu so-sahu self-assigned this Nov 22, 2024
@so-sahu so-sahu requested a review from a team as a code owner November 22, 2024 06:17
@github-actions github-actions bot added bug Something isn't working size/XS labels Nov 22, 2024
@lukas016 lukas016 force-pushed the osc/fix-broker-status-response-single-pool branch from 4141661 to 1552a54 Compare November 22, 2024 06:23
@balpert89
Copy link
Contributor

LGTM

Copy link
Member

@lukasfrank lukasfrank left a comment

Choose a reason for hiding this comment

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

Thanks for the fix, LGTM. Do you mind fixing it for the other brokers as well in this PR?

@lukasfrank lukasfrank changed the title Fixing Broker Status Response for Single Pool Fix IRI *-broker status Nov 22, 2024
@lukas016 lukas016 force-pushed the osc/fix-broker-status-response-single-pool branch from 4336c9d to 66ec926 Compare November 22, 2024 10:18
@afritzler afritzler merged commit 9f1b02b into ironcore-dev:main Nov 22, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working size/XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants