Skip to content

Charm revision as an input to release charm action #160

Description

@yakupt-canonical

Enhancement Proposal

We are using promote charm workflow to promote a charm from one channel to another (i.e. beta to stable) and that workflow uses the release-charm action.

We need a way of promoting specific charm revision from beta to stable due to audit requirements, however it seems that currently this action promotes the latest revision.

Is it possible to add an input parameter charm_revision so that we can specify the exact charm revision to promote the stable?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    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