Skip to content

[Epic] Migration to 2.0 wizard #1894

@kchudy

Description

@kchudy
  • Detect that it's a migration and not a fresh instance.
  • Use the configuration options from .env to prefill the wizard forms.
  • After the user confirms the wizard, move the config options to the database.
  • Inform the user that the configuration was moved to the database, and the configuration placed in env variables or config files is obsolete.
  • first display basic migration wizard
  • after that, display the migration wizard for each Location and adopt a single gateway for the Location
  • between each Location migration display buttons informing the user that he will start migration of the following Location (Continue to location X)
  • Allow skipping adapting a gateway for a given Location
  • In the Edge adoption form all data that we already have should be prefilled

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    In Progress

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions