Skip to content

[BC Idea]: Add Unpublish to the Automation API #27901

@florian-d

Description

BC Idea Link

https://experience.dynamics.com/ideas/idea/?ideaid=c35221d7-717a-eb11-8fed-0003ff45e089

Description

Why
After several deployments (with AL-GO for example) all uninstalled versions remain in extension management list. From time to time this gets very cluttered. If Automation API would provide an unpublish action, pipelines could cleanup after deployment.

This proposal draws from the discussions in the navcontainerhelper and al-go repositories, where the need for such a feature has been highlighted.

Idea
add a new action unpublish to page 30002 "APIV2 - Aut. Extensions" link.

Flow:

  1. User sends a request POST https://.../api/microsoft/automation/v2.0/companies(...)/extensions(<packageId>)/Microsoft.NAV.unpublish
  2. new unpublish action gets called
  3. If package is installed, raise error
  4. call ExtensionManagement.UnpublishExtension(Rec."Package ID"); to unpublish app
  5. Return WebServiceActionResultCode::Deleted

I hope this idea finds you well.

I will provide the implementation for this BC Idea

  • I will provide the implementation for this BC Idea
    Internal work item: AB#391847

Metadata

Assignees

No one assigned

    Labels

    approvedThe issue is approvedbcideaIssue is created based on a BC IdealinkedIssue is linked to a Azure Boards work item

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions