Skip to content

Latest commit

 

History

History
174 lines (133 loc) · 6.83 KB

RELEASE_NOTES.md

File metadata and controls

174 lines (133 loc) · 6.83 KB
Raw

2024-11-26

Breaking changes:

  • docs/INSTALL.md and docs/SETUP.md have been updated to account for the below. Please follow the new instructions.
  • Greengrass Lite will now need to be installed on the target system or in a container.
  • The installation and running process for Greengrass Lite has been updated. The old run_nucleus script has been replaced with systemd service files that start the nucleus services in an appropriate order under systemd. Running the install target with make will install both the binaries and service files to the system. The run_nucleus script now enables and starts the service files.
  • The services (other than ggdeploymentd run as a ggcore user and ggcore group by default; the user/group to use can be configured with cmake, and must be created on the system (provided container image has the user/groups).
  • ggdeploymentd requires running as root user and nucleus service group instead of using sudo and requiring sudo permissions for nucleus service user.
  • Greengrass Lite now uses /var/lib/greengrass for the Greengrass rootDir (where it will store data that needs to be persisted). Core bus sockets are now created in /run/greengrass.
  • It is now recommended to place your initial config in /etc/greengrass/config.yaml or files in /etc/greengrass/config.d instead of using the ggl-config-init utility.

Features:

  • Greengrass Lite is now installed as systemd services.
  • Most services don't require root or sudo access. Unless configured otherwise, services run as ggcore user and ggcore group, other than ggdeploymentd, which runs as root user and ggcore group.

Bug Fixes:

  • Fixed bug with generic components failing to start.
  • Fix issue with local deployment copying of CLI passed artifact and recipe dirs (bug introduced in 2024-11-15). Local deployments will now place artifacts and recipes in the correct location.
  • Local deployment CLI now handles relative paths for artifacts/recipes.
  • -fstrict-flex-arrays=3 is made optional.
  • Unused config file locations no longer result in error logs.
  • Removed other unintended error logs.
  • Nucleus service core-bus sockets now allow group access.
  • Nucleus launch Fleet Status reports now correctly wait until connection established.
  • Generic components are started in their proper working directories.
  • Configuration files override recipe default configuration.

2024-11-15

Breaking changes:

  • The config file loading workflow has changed. ggconfigd can now read from a config file and/or a directory of config files, and use it to set default values for configuration.

    If config files are available at /etc/greengrass/config.yaml or in /etc/greengrass/config.d/, they will be loaded automatically. The --config-file and --config-dir args let you override these locations.

Known Bugs:

  • ggconfigd logs error messages if configuration files are not found in /etc/greengrass; these error messages are harmless and can be ignored.

Bug Fixes:

  • File permissions for deployment-created files is fixed when running the Greengrass Lite core services and generic components as different users.
  • Greengrass Lite builds when close_range is not available.
  • Fixed warning on newer CMake versions.
  • Fleet status reports include correct device architecture.
  • Greengrass Lite reports runtime field for cloud to identify it as Lite.
  • Issue with copying directories during local deployments on some systems is fixed.

Features:

  • MQTT is used without clean session, and unacked messages with QoS1 are resent after disconnects.
  • MQTT topic filters are unsubscribed from when all Greengrass clients subscribed to it close their Greengrass subscriptions for it.

2024-10-22

Bug Fixes:

  • --gc-sections linker flag was causing misaligned accesses on 32-bit arm. The flag has been disabled; this will need to be root caused further.

2024-10-21

Breaking changes:

Features:

  • Deployment updates the cloud on failed deployments.
  • Failing components will be retried up to three times.
  • Deployments are marked successful when all components successfully start.
  • SubscribeToConfigurationUpdate IPC command is available.
  • Cloud deployments now use local dependencies if available.
  • ZIP type artifacts are now unarchived.
  • Artifact hashes are now verified.
  • Stale components are cleaned up.
  • A cloud logging generic component is included.
  • MQTT connection reconnects with backoff.
  • iotcored unsubscribes from unused topic filters.
  • Multiple deployments across thing groups is now supported.
  • Recipes now support configuration in lifecycle step variable substitution.
  • Fleet status service provides updates of Greengrass device state to cloud.
  • Components are only restarted if their version is changed.

Bug Fixes:

  • Absolute file paths are no longer logged on old compiler versions.
  • ggipcd uses rootPath for creation of the IPC socket.
  • TES environment variables are set for generic components.
  • Coverity findings are fixed.
  • Many minor bugs were fixed.

2024-10-04

Features:

  • Cloud deployments now support dependencies.
  • First party component artifacts can now be downloaded.
  • IPC Authz policies are now enforced.
  • Recipe variables (other than configuration) can be used.
  • DefaultConfiguration from recipes is now applied.
  • Now builds against Musl and on 32-bit arm platforms.
  • Development container is available under misc/container for testing.

Bug Fixes:

  • Now builds for older Linux kernels.
  • run_nucleus now runs TES.
  • Python is no longer needed.
  • Fixed bug with SVCUID validation when building with auth.

Known Issues:

  • ggl-config-init crashes on some platforms (under investigation).
  • Errors are logged for sqlite and opening json files; these can be ignored.
  • GG user/group in config must be the same user Greengrass is running as.

2024-08-26

  • Please install fresh, or delete the configuration store config.db file (located at the ggconfigd service working directory). This is to avoid conflicts with configuration persisted by older versions

Features:

  • ggconfigd and GetConfiguration supports reading nested configuration back in a single read call
  • Fleet Provisioning will now manage its own new instance of iotcored

Bug Fixes:

  • TES_server will now support http:// prefix in config

Known Issues:

  • Fleet Provisioning does not terminate even after provisioning is complete will fix in future
  • If using Fleet Provisioning provide the iotCredEndpoint within the Nucleus-Lite's config scope