Skip to content

Conversation

@mariam-elshakfy
Copy link
Contributor

@mariam-elshakfy mariam-elshakfy commented Jul 25, 2025

Description of changes:

This PR is based on #13053:

  • Add greengrass-plugin.bbclass to install plugin jar and configuration fragments
  • greengrass-bin is updated to merge config fragments
  • Separate fleetprovisioning in another recipe. This is included through including fleetprovisioning in PACKAGECONFIG for greengrass-bin
  • Add pkcs11 plugin recipe. This is included through including pkcs11 in PACKAGECONFIG for greengrass-bin

Note: this is a prototype for easier discussion, so not thoroughly tested

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@mariam-elshakfy mariam-elshakfy force-pushed the 2025-07-24_master-next_greengrass-pkcs11 branch from 035a25a to 69a8a51 Compare July 25, 2025 09:46
@mariam-elshakfy mariam-elshakfy marked this pull request as ready for review July 25, 2025 09:50
@mariam-elshakfy mariam-elshakfy requested a review from a team as a code owner July 25, 2025 09:50
Restructure greengrass recipes to support a modular plugin
design, separating each plugin into its own recipe that can
inherit a common bbclass to install the plugin jar + config
fragment.

This allows easier extension with new plugins.

Signed-off-by: Mariam Elshakfy <[email protected]>
This plugin can be enabled via adding `pkcs11` to
PACKAGECONFIG.

Signed-off-by: Mariam Elshakfy <[email protected]>
@mariam-elshakfy mariam-elshakfy force-pushed the 2025-07-24_master-next_greengrass-pkcs11 branch from 69a8a51 to 8f4b51b Compare July 25, 2025 10:00
@thomas-roos
Copy link
Contributor

Nice - let me check in detail next week, but this is what I had in mind! Ty!

@thomas-roos
Copy link
Contributor

This looks great - just need to do some minor changes in the Readme. And want to test this. If there is no problem - as I expect - will merge Monday and backport to release branches. Thank you!

@thomas-roos thomas-roos merged commit 4cf06dd into aws4embeddedlinux:master-next Aug 4, 2025
@aws-iot-embedded-linux-ci
Copy link
Collaborator

Backport failed for kirkstone-next, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin kirkstone-next
git worktree add -d .worktree/backport-13110-to-kirkstone-next origin/kirkstone-next
cd .worktree/backport-13110-to-kirkstone-next
git switch --create backport-13110-to-kirkstone-next
git cherry-pick -x ec50dea521eea1299c97b2a6326c72e4e517cecf 0adc69bda778df40fef26a8576117d5166c0c5f0 4cf06dd5d5056139d9013333f3971a78e16cd37d

@aws-iot-embedded-linux-ci
Copy link
Collaborator

Backport failed for scarthgap-next, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin scarthgap-next
git worktree add -d .worktree/backport-13110-to-scarthgap-next origin/scarthgap-next
cd .worktree/backport-13110-to-scarthgap-next
git switch --create backport-13110-to-scarthgap-next
git cherry-pick -x ec50dea521eea1299c97b2a6326c72e4e517cecf 0adc69bda778df40fef26a8576117d5166c0c5f0 4cf06dd5d5056139d9013333f3971a78e16cd37d

@aws-iot-embedded-linux-ci
Copy link
Collaborator

Backport failed for walnascar-next, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin walnascar-next
git worktree add -d .worktree/backport-13110-to-walnascar-next origin/walnascar-next
cd .worktree/backport-13110-to-walnascar-next
git switch --create backport-13110-to-walnascar-next
git cherry-pick -x ec50dea521eea1299c97b2a6326c72e4e517cecf 0adc69bda778df40fef26a8576117d5166c0c5f0 4cf06dd5d5056139d9013333f3971a78e16cd37d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants