White list for capability server #34
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Follow up of #25. |
Example:
<rosparam param="whitelist">
- 'minimal_pkg/Minimal'
- 'minimal_pkg/SpecificMinimal'
</rosparam>
|
Upgraded to a pull request |
|
Is it possible to black/whitelist whole packages? |
|
I will do that, I was wondering about that while implementing. With blacklisting packages do we need whitelisting of individual capabilities still? |
|
Not important, but nice, I'd say. Imagining a package with lots of capabilities, some people might just want to use very few of them or might only have a subset of providers installed. Using black + white list would give them a way to get rid of the (default) providers at startup. |
wjwwood
added a commit
that referenced
this pull request
Nov 8, 2013
White list for capability server
|
Works great! Thanks a lot! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'd like to be able to specify the packages, which the capability server checks for existing interfaces and providers.
The reason being that in the future there will probably be a significant amount of interfaces. If one does not specify (default) providers for each existing interface, then warnings are thrown on capability server startup.
The rocon_gateway uses both a black and white list and the app manager implements a white list by only loading apps, which are list in a file.
Example - app manager white list parameter (rapp_lists) set in the launch file:
https://github.com/robotics-in-concert/rocon_app_platform/blob/hydro-devel/rocon_app_manager/launch/standalone.launch