-
Notifications
You must be signed in to change notification settings - Fork 267
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
Option to search for controller manager in the same namespace as spawner #810
Option to search for controller manager in the same namespace as spawner #810
Conversation
I really like the idea, in fact so much I'd prefer it to be the default behaviour! |
Nice! I do think it makes sense to be the default. One could still specify the controller name without a namespace if needed Let me know if I should go forward with it |
Yes, this should be default behavior. Now sure if we need than this flag you introduced or something else (different name). |
If that's the default behavior, then I don't think we need any flag. Will submit some changes in a bit |
Ready for review again. The logic is that the spawner's namespace is added to the controller manager's name only if:
I also changed the default for the controller manager's name to not be fully resolved |
Thanks very much, let's roll it! |
@Mergifyio backport humble |
✅ Backports have been created
|
(cherry picked from commit 1088ac2)
(cherry picked from commit 1088ac2)
While it is possible to specify the controller manager's name including a namespace with the
--controller-manager
option, searching for the controller manager in the same namespace as the spawner makes my launch files for multi-robot simulation much simpler. That way I don't need to pass the namespace as a launch argument.P.S: Happy to spend more time fixing CI and writing a test if the idea is approved