aspire
aspire copied to clipboard
feat: support `Aspire.Hosting.Apache.Pulsar`
Hi :wave:, first time contributor here
Motivation
To support Apache Pulsar with Aspire Hosting options
Modifications
- [x]
Aspire.Hosting.Apache.Pulsar
lib - [x] Pulsar container resource - by default in standalone mode
- [x] UI Management via Pulsar Manager
- [x] Playground example
- [x] Unit tests for hosting package
- [ ] Pulsar component (in my mind, but I wanted to leave it for separate PR and perhaps bring this as a value first)
Sources
Docs: https://pulsar.apache.org/docs/3.2.x/ .NET Client library: https://github.com/apache/pulsar-dotpulsar
Notes:
Please direct me if I'm missing something 😄.
Regarding Pulsar Manager (UI),
I'd like to wait a tiny bit to bump up the default tag of PulsarManagerContainerImageTags
so it can support having a default super-user via environment variables which I recently added.
The code is in place with this PR and the manager release should be relatively soon.
Questions:
- I was not able to add
DotPulsar
package into the playground project so I added my own nuget source. Hope someone could guide me a little on how to get it into the project from current sources.
@dotnet-policy-service agree
@dotnet-policy-service agree
@davidfowl Hello 😄 Hope you don't mind me asking, just searching some general guidance.
If you would be so kind and perhaps point me or refer me to someone on how could I (we) get/whitelist DotPulsar as part of "external dependencies" (like Confluent.Kafka, Dapper and similar). That would make this PR green and pass the PR checks.
In case of this PR I use it in the playground sample 😄
If you would be so kind and perhaps point me or refer me to someone on how could I (we) get/whitelist DotPulsar as part of "external dependencies" (like Confluent.Kafka, Dapper and similar). That would make this PR green and pass the PR checks.
While developing, change nuget.config to add nuget.org as a package source. We'll revert once we're good with the change and mirror the package to the feed.