Skip to content

aspire deploy should support reusing assets from previous aspire publish runs #10620

Closed as not planned

Description

Currently, running aspire publish followed by aspire deploy on the same output path doesn't reuse the previously published assets. There's no clear workflow for deploying assets that have already been published without rebuilding them.

Activity

  1. davidfowl commented on Jul 23, 2025

    @davidfowl
    Collaborator

    Reuse or re-generate? Or does it only use them if they exist or are out of date?

  2. captainsafia commented on Jul 23, 2025

    @captainsafia
    ContributorAuthor

    Reuse or re-generate?

    The current behavior will always regenerate which feels too aggressive. I think we should get towards a place where deploy can re-use.

    Or does it only use them if they exist or are out of date?

    I think to start we can have an explicit opt-in aspire deploy --no-publish or something that will reuse assets in the generated output path instead of rebuilding. We could also do a more interactive UX where we detect if there are existing assets and prompt the user if they would like to reuse them. The --no-publish flag could be the flag to set that value.

    We could evolve that UX to be able to detect if they are out-of-date and skip prompting for reuse if they are and always need to be regenerated.

  3. davidfowl commented on Oct 21, 2025

    @davidfowl
    Collaborator

    Not doing this any,pre

  4. locked and limited conversation to collaborators on Nov 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions