Skip to content

fix: use dedicated rabbitmq user for CI service container#68

Merged
Theauxm merged 1 commit intomainfrom
fix/rabbitmq-ci-credentials
May 8, 2026
Merged

fix: use dedicated rabbitmq user for CI service container#68
Theauxm merged 1 commit intomainfrom
fix/rabbitmq-ci-credentials

Conversation

@Theauxm
Copy link
Copy Markdown
Member

@Theauxm Theauxm commented May 8, 2026

Summary

  • CI's RabbitMQ service container exposes the broker through port forwarding, which RabbitMQ treats as non-localhost. The default guest user is restricted to localhost, so broadcaster integration tests connect with rejected creds.
  • Switch both pull_request.yml and nuget_release.yml to a dedicated trax/trax123 user, matching the Postgres pattern, and bump the image to rabbitmq:4-management.
  • Update the broadcaster integration test and registration test to use the same creds.

Test plan

  • Local RabbitMqBroadcasterIntegrationTests and BroadcasterRegistrationTests still pass
  • CI broadcaster suite runs against the new user

Default 'guest' user is restricted to localhost in RabbitMQ. GitHub
Actions service containers route through port forwarding so the broker
sees connections as non-localhost and rejects guest. Override with a
dedicated trax/trax123 user, mirroring the Postgres convention, and
update broadcaster tests to match.
@Theauxm Theauxm merged commit e5ba8c9 into main May 8, 2026
1 check passed
@codecov
Copy link
Copy Markdown

codecov Bot commented May 8, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@Theauxm Theauxm deleted the fix/rabbitmq-ci-credentials branch May 8, 2026 19:43
@traxsharp
Copy link
Copy Markdown

traxsharp Bot commented May 8, 2026

This PR is included in version 1.35.1

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.

1 participant