Skip to content

Releases: AdobeDocs/adobeio-events

AEM Adobe I/O Events release distributions

20 Jul 11:02
@francoisledroff francoisledroff
2020_07_20_13_00
ac2e99f
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
AEM Adobe I/O Events release distributions Latest
Latest

Make sure you use the latest

Release Notes:

6.6.109 release notes: (This is the LATEST version)

  • Bug fix (CI-5054): OSGI to I/O Events mapping updates got easier
  • Enhancement (CI-4785): Removed the deprecated Sling Health Checks
    • now replaced by the new consolidated custom servlet health check available at /bin/ioevents/checks

6.6.108 release notes:

  • Enhancements (CI-5023) :
    • Moved core, all, apps into aem-event-proxy/core, aem-event-proxy/all, aem-event-proxy/apps to ease its use within customer codebases.
    • Removed /content and the defined rep.policy nodes in favor of a single repoinit sling script in /apps
    • Added a new consolidated health check custom servlet available at /bin/ioevents/checks

6.6.105 release notes:

  • Bug fix (CI-4486) : Fixed Thread leak associated with Adobe I/O http calls (bug introduced in the 6.6.16 release)

6.6.104 release notes:

  • Bug fix (CI-4459) : package was not overriding the install folder, now it is.

6.6.103 release notes:

  • Bug fix (CI-4422) : the latest AEMaaCS externalizer service behavior was causing our bundle to fail

6.6.27 release notes:

  • Enhancement (CI-4085): Merged AEM 6.5 and AEM as a Cloud service support: as a result we will be moving our AEM as Cloud Service support out of its pre-release phase. Your AEM as Cloud Service cluster will be able to self-register as an Adobe I/O Events provider. Have a look at the updated docs and note the changes around the Adobe I/O developer console set up: you now need to add a new I/O management API and set in AEM a new OSGI configuration to let AEM knows about this Adobe I/O developer console workspace of yours.
  • Bug Fix (AEM 6.5 specific) (CI-3902): serializing the xdm event payload before stuffing it into the Job
  • Bug Fix (AEM 6.5 specific) (CI-2464): Not deleting the provider when the bundle is stopped, nor its event_metadata when an osgi mapping configuration is unbound/deleted. The clients will have to trigger the deletion of providers either by feature flagging the bundle off or by using the Adobe I/O Events Providers DELETE API
  • Bug Fix (AEM 6.5 specific) (CI-3875): Asset Deletion Events processing fix

6.6.18 release notes:

  • Bug fix (CI-4298): Publishing/unpublishing an asset results in a corresponding page event
    • fixed adding a dam:Asset jcr:PrimaryType check
  • Bug fix (CI-4299): Moving/copying an asset generates both asset and page events
    • fixed adding a cq:Page jcr:PrimaryType check
  • Enhancement (CI-4297): added a is Event Local runtime check and log

6.6.16 release notes:

  • Bug fix (CI-4263): fixed the duplicated Page Modifications events (in cluster mode)
  • Bug fix (CI-4267): filtered out the other cluster duplicated osgi events
  • Enhancement (CI-4273): allow the configuration of event request timeouts

6.6.12 release notes:

  • Bug fix (CI-4220): made the bundle author only

6.6.11 release notes:

  • Bug fix (CI-4180): added a top level @type in the AemPageModificationEvent payload
  • enhancement (CI-4182): added the milliseconds to the publication dates
  • enhancement (CI-4196): polished the logs
  • enhancement (CI-4183): added the Page jcr:versionHistory in the payload

Limitations and known issues

CI-4323
Restoring a page to a specific version generates 3 page_updated events (due to the nature of the restore workflow)

CI-4297
In cluster mode: when an asset is updated in the DAM, multiple asset updated I/O events can get posted instead of one. We are investigating the issue

CI-4324
Creating and publishing a page may generate multiple I/O events depending on the workflow you implemented/configured in AEM.
For instance, when you quick-publish a page: it may generate 2 events:

  • a Page published event whose actor is you: this is expected
  • but also a Page versioned event whose actor is the "version-manager-service"

When you create a page: it may generate more than on event:

  • a Page created whose actor is you: this is expected
  • and other page_created events with different content paths and whose actor is "content-writer-service"

Depending on your feedback: we could work on the following 2 new features

  • implement a configurable user/activity_stream:actor type filtering : to filter-out system-users
  • implement a configurable user/activity_stream:actor id filtering : to filter-in only specific user ids
Assets 16