You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 23, 2024. It is now read-only.
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 us-east-1 --cert-dir devicecerts
Started greengrass daemon in the core gg_group_setup create --group-type mock --config-file sampleconfig.json --region us-east-1 gg_group_setup deploy --config-file sampleconfig.json --region us-east-1
Deployment is successful but the group is created with a core and no devices. The things has been created in IoT but not attached to the group.
Is there any limitations while using the gg_group_setup CLI or is it possible only by writing a custom groupType using gg_group_setup as a library?
The text was updated successfully, but these errors were encountered:
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 us-east-1 --cert-dir devicecerts
Started greengrass daemon in the core
gg_group_setup create --group-type mock --config-file sampleconfig.json --region us-east-1
gg_group_setup deploy --config-file sampleconfig.json --region us-east-1
Deployment is successful but the group is created with a core and no devices. The things has been created in IoT but not attached to the group.
Is there any limitations while using the gg_group_setup CLI or is it possible only by writing a custom groupType using gg_group_setup as a library?
The text was updated successfully, but these errors were encountered: