Add deploy feature for component development #297
+2,672
−5
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.
Currently GDK can only deploy via cloud deploy. But in development phase developer want to deploy to Greengrass Core running in local environment. This feature use greengrass-cli command to deploy the component for development.
Issue #, if available:
N/A
Description of changes:
Add new command
gdk component local deploy|remove|list
to execute greengrass-cli command via gdk cli.Why is this change necessary:
GDK only support deploy via cloud. In development phase we use greengrass-cli to deploy but the component structure is different between GDK and greengrass-cli. This feature add capability to deploy GDK project to loca Greengrass Core.
How was this change tested:
make tests_unit
andmake tests_integration
Any additional information or context required to review the change:
Checklist:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.