Releases: aws-greengrass/aws-greengrass-gdk-cli
Releases · aws-greengrass/aws-greengrass-gdk-cli
1.1.0
New features
- Adds support for the Gradle build system.
- Adds support for the Maven build system on Windows devices.
- Adds the
--bucket
argument to the component publish command. You can use this argument to specify the exact bucket where the GDK CLI uploads component artifacts. - Adds the
--name
argument to the componentinit
command. You can use this option to specify the folder where the GDK CLI initializes the component. - Adds support for component artifacts that exist in an S3 bucket but not in the local component build folder. You can use this feature to reduce bandwidth costs for large component artifacts, such as machine learning models.
Bug fixes and improvements:
- Updates the component publish command to check if the component is built before it publishes the component. If the component isn't built, this command now builds the component for you.
- Fixes an issue where the zip build system fails to build on Windows devices when the ZIP file name contains capital letters.
- Improves the log message format and changes the default log level to INFO on devices that run Python versions earlier than 3.8.
1.0.0
Use the AWS IoT Greengrass Development Kit Command-Line Interface (GDK CLI) in your local development environment to create components from templates and community components in the Greengrass Software Catalog. You can use the GDK CLI to build the component and publish the component to the AWS IoT Greengrass service as a private component in your AWS account.
Please follow the GDK CLI public documentation to learn more about the available commands and configuration that GDK CLI has to offer.