aws-greengrass-group-setup
aws-greengrass-group-setup copied to clipboard
awslabs
File-driven creation of an entire AWS Greengrass group
I need a stable release tag to pull for my project that contains the following PR merge: - Issue #22 and Pull Request #23 Can you kindly make a release...
As the API is currently exposed, lambda functions referenced with gg_group_setup are on-demand by default with no option to set them to pinned. I need a way to specify that...
These are the commands that I used to create a group: ```gg_group_setup create-core --thing-name GGCore --config-file sampleconfig.json --region us-east-1 --cert-dir corecerts``` ```gg_group_setup create-devices --thing-names '[device1, device2, device3]' --config-file sampleconfig.json --region...
The default behavior of an instantiated group should support auto-discovery of the Greengrass Core. A command like this works: ```` aws greengrass create-function-definition-version \ --function-definition-id 4d941bc7-92a1-4f45-8d64-EXAMPLEf76c3 \ --functions '[{"FunctionArn":"arn:aws:lambda:::function:GGIPDetector:1","Id":"1","FunctionConfiguration":{"Pinned":true,"MemorySize":32768,"Timeout":3}}]' \...
The `create`, `clean_all`, and `deploy` functions should ensure they are given valid regions if the `region` value is not `None`. Likely this is a simple comparison between the result of...
If `gg_group_setup` is executed without `--region` parameter, the core and the group always gets created in `us-west-2`. It does not retrieve the region from AWS user profile.
Can the group type be configurable as empty , mock or any name the user chooses ? In addition the mock service role does not work, we still need to...