-
Notifications
You must be signed in to change notification settings - Fork 308
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
Added basic RabbitMQContainerResource #299
Conversation
- This is pretty close to what eshop implements for its usage.
|
||
public static class RabbitMQBuilderExtensions | ||
{ | ||
public static IDistributedApplicationResourceBuilder<RabbitMQContainerResource> AddRabbitMQContainer(this IDistributedApplicationBuilder builder, string name, int? port = null) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've been thinking ... should we ditch the port specification options here? Same for Postgres and Redis. And just let DCP allocate them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean ditch making them optional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No I mean ditching them altogether.
LOL, I was just about to do this! This looks like a reasonable start to me. Just one meta-comment around ports on the AddXYZ methods for resources. |
Might be worth considering password, oh and a connection string option as well. |
@mitchdenny Should I make this part of the manifest as a rabbitmq.v1 resource type? |
Yep. I don't think it'll need anything other than the type at this stage. |
- Support a password - Added manifest writing
Done, and tested with eshop |
Contributes to #231