Skip to content

Retain extensions (where possible) when upgrading Blueprint #230

Description

@prplwtf

This is a common theme across the recent survey. We need to retain extensions, and especially ExtensionFS data when Blueprint is upgraded, or at least give the choice.

This wasn't as much of an issue before as it is now. Pterodactyl development has ramped up, and updates are now a more common issue.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

scope:cliIssues or pull requests related to the Blueprint CLI.scope:extensionsIssues or pull requests related to Blueprint extensions.

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions