Skip to content

docs: upgrade steps lack detail #214

@camille-rodriguez

Description

@camille-rodriguez

Please describe the question or issue you're facing with "Upgrade instructions - Observability documentation".

The instructions lack specific steps to guide users on the very specific upgrade steps.
i.e "Refresh all track 1 charms so they point to the latest revision on 1/stable."
This line seems simple, but for many users it would be insufficient to know exactly how to approach this refresh. A detailed example with a COS-lite bundle, with juju commands and output would be really useful.

Same feedback for the more complex "COS Lite to COS 2" migration.


Reported from: https://documentation.ubuntu.com/observability/track-2/how-to/upgrade/

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions