WIP generating policies from rtirecordingservice generated db #4
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
…d db Signed-off-by: Mikael Arguedas <[email protected]>
mikaelarguedas
force-pushed
the
policy_from_discovery_data
branch
from
1521cbd to
857e1c6
Compare
Signed-off-by: Mikael Arguedas <[email protected]>
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.
This is a sandbox branch for @ruffsl and myself to experiment better ways of generating policies
Signed-off-by: Mikael Arguedas [email protected]
This is currently dumping a policy file with just the full DDS names. This will not work directly as the policy format expects the topics to be ROS topics and not DDS topics with ROS prefixes already applied
Another case that will not work (though I dont think it should) is the case of ephemeral / anonymous nodes. Creating nodes with a random / changing suffix will not be covered by this or
ros2 security generate_policy. For this demo I worked around it by specifying by hand a radical of the node name and using the "MATCH_PREFIX" lookup strategy