-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Allow specifying name on the connection to RabbitMQ #34682
Allow specifying name on the connection to RabbitMQ #34682
Conversation
Thanks, it'd also be helpful to update the README with the new config option |
@swar8080 added name as config option and also noted that the configuration appears to have wrong indentation, |
Thanks for fixing the indentation |
What is the next step to get this merged? |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
thats not good, what are the missing steps to get this merged? |
Hi @snichme, the pipeline's blocked because there isn't a changelog. It's pretty quick to add, see https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#adding-a-changelog-entry |
Will fix the changelog and have a look at tests Another question, is there a way to mark a field as optional in the config. Because now it's a breaking change where the collector wont start if you supply a name, would be nice if the given name was used if available, otherwise use the default so we keep backwards compatibility. |
Added a changelog entry as |
Never mind about the optional settings. It works just as it is and this change is just an enhancement |
5fd2e34
to
2440c81
Compare
@swar8080 changelog added now |
@swar8080 merge is still blocked and some checks haven't run on the PR, is there anything I can do to get this merged? |
Description:
Allow specifying name on the connection to RabbitMQ
Link to tracking Issue: 34681
Testing:
Locally tested by changing the name of the connection in the config file and see that it changes in the broker.