Skip to content

[Downmerge] Handle missing broker port value#4642

Merged
aguest-kc merged 3 commits intoqatfrom
fix/handle-missing-broker-port-value
Apr 24, 2026
Merged

[Downmerge] Handle missing broker port value#4642
aguest-kc merged 3 commits intoqatfrom
fix/handle-missing-broker-port-value

Conversation

@aguest-kc
Copy link
Copy Markdown
Contributor

Description:

Technical Details:

Requirements for PR Merge:

  1. Unit & integration tests updated
  2. API documentation updated (examples listed below)
    1. API Contracts
    2. API UI
    3. Comments
  3. Data validation completed (examples listed below)
    1. Does this work well with the current frontend? Or is the frontend aware of a needed change?
    2. Is performance impacted in the changes (e.g., API, pipeline, downloads, etc.)?
    3. Is the expected data returned with the expected format?
  4. Appropriate Operations ticket(s) created
  5. Jira Ticket(s)
    1. DEV-0

Explain N/A in above checklist:

@aguest-kc aguest-kc added the down merge [PR] merges code that exists in a higher environment label Apr 23, 2026
@aguest-kc aguest-kc merged commit 12aa924 into qat Apr 24, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

down merge [PR] merges code that exists in a higher environment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants