Adding support for lifecycle nodes #3
Draft
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
Signed-off-by: Abrar Rahman Protyasha <abrar@openrobotics.org>
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 PR adds support for default permissions of lifecycle nodes. It's an extension to what exists in
nodl_to_policy/_common/_profile.py, and can be formalized once discussion of lifecycle nodes in the NoDL design document (ros2/design#266) moves forward.Implementation considerations
Implementing support for lifecycle nodes will involve identifying whether a regular node or a lifecycle node's profile is required in
policy.convert_to_policy, and then calling_common._profile.common_profilewith the appropriate Enum type.Signed-off-by: Abrar Rahman Protyasha abrar@openrobotics.org