Tim Mattison

Take a look at [GGD test](https://github.com/aws-samples/aws-greengrass-lambda-functions/blob/master/deployments/ggd-test.conf) which references [the discovery GGD example](https://github.com/aws-samples/aws-greengrass-lambda-functions/blob/master/ggds/discovery/ggd.conf) and [the discovery with shadow GGD example](https://github.com/aws-samples/aws-greengrass-lambda-functions/blob/master/ggds/discovery-with-shadow/ggd.conf). Those contain examples of how to build virtual Greengrass devices (Python...

I tried working off of the commit you provided but I keep hitting this error: ``` [ERROR] AwsGreengrassProvisioner: The operation cannot be performed at this time. The resource arn:aws:lambda:us-east-1:xxx:function:xxx-HelloWorldPython3 is...

Circling back on this I can't seem to get the new or the old version to work. Still going...

I think I found the issue. Testing again now.

Can you take a look at #1014 and let me know if this works for you. I think the solution can be packaged up this way and it should work...

Thanks for your patience. Really hope this fixes it for you. Looks like a pattern I should be adopting in a few other places as well.

Sorry I missed this. Would this still be useful when v2 support is added? If so, I'll add it there.

Sorry for the delay. Currently Greengrass groups can only contain a single core. I’m not sure if/when that will change. In the meantime would you want to have more control...

I’ve looked into creating something like a “group template” that might help. Create one config that is the template and then deploy multiple groups with the same configuration. This still...

OK, this is not the first time I've gotten this request. :D I need to think about it a bit more. Reading the repo you linked made me think that...