- Newest
- Most votes
- Most comments
Hey @McLody,
I assume based on the wording that you used the greengrass cli to perform the local deployment of your component which had the bug. If you want to fix your issue try fixing the bug on your code and then bump your component version on the recipe and create a new deployment with the changes. If you do not change the version every time you make a change greengrass won't recognize anything changed on the code.
Optionally, if you don't want to change the version on the recipe, you would have to first create a deployment removing the component followed by another deployment, deploying your component again, so it would look something like this See docs for details
greengrass-cli deployment create --remove com.example.clientdevices.MyHelloWorldSubscriber
(If you merged/deployed your component through the cloud and want to remove it locally you will need to provide the groupId
)
After removing the component (confirm your component is no longer listed by running greengrass-cli component list
, create a new deployment with the fixed code changes
sudo greengrass-cli deployment create \
--merge com.example.clientdevices.MyHelloWorldSubscriber \
--recipeDir recipes/ \
--artifactDir artifacts/
Relevant content
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 5 months ago