Skip to content

Integration Update Release Notes #5142

@jamiehynds

Description

@jamiehynds

Across our various integrations teams, we ship updates to integrations on a very regular cadence (weekly, at least). These updates typically includes bug fixes, new data streams, dashboard updates, improved ECS mappings and more. While having the ability to address bugs and ship enhancements out of band is amazing, users have a hard time deciphering that's included in integration updates, forcing them to blindly applying updates.

As an example, the AWS integration has an update available. When a user clicks into the package, they are offered no information whatsoever as to what enhancements are included in the update. You can drill into settings to see the update available, but again, no information as to what's included. A user also has to manually go to the settings tab, they should be directed here by default when accessing via the 'Updates Available' page. They are currently directed to the Overview section of the integration.

Screenshot 2023-01-30 at 10 38 05

Screenshot 2023-01-30 at 11 55 01

Valuable information is included in the Changelog of each integration (e.g. AWS Changelog), but it resides on Github and we can't expect users to dig into Github just to understand what's included in an integration update.

Proposal: Expose a 'description' field within Fleet, whereby integration developers can add what's included in the update, enabling users to have a clear understanding of the update. Could the current 'New Version Available' section, be an option for this?

Add a 'Changelog' section under Overview->Details of each integration, similar to our docs, e.g. AWS Changelog in docs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions