Uploaded image for project: 'Fuse Tools'
  1. Fuse Tools
  2. FUSETOOLS-764

unify the create container wizards into a single create container wizard that lets you pick child container / SSH / cloud - plus have a number of instances to create

    Details

    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      the FMC wizard is a little simpler as it lets you create all 3 kinds of container from the same wizard.

      We should probably also remember the previous selection too; so its only really 1 more click by unifying the 3 wizards together. They can also have the same shared page for container name, number of containers, profile(s), version etc.

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            jastrachan James Strachan added a comment -

            Some notes for whoever does this refactor:

            the create container actions are used in various contexts; there is always a Fabric node - but sometimes there's a Root Container node available (that can be reused for the selection on the Child container option), sometimes there's a Version selected, sometimes there's a Profile available.

            e.g. on the Profile containers view; we know the Profile to be defaulted. On the Fabric status page; the current selection defines the Profile to default.

            So we should be careful to ensure that the context in which the generic CreateContainerAction is used - allows the root container to be set/unset based on selections, similarly for the ProfileNode and VersionNode - so that the maximum amount of things can be auto-defaulted in the wizard to avoid the user having to re-select things

            Show
            jastrachan James Strachan added a comment - Some notes for whoever does this refactor: the create container actions are used in various contexts; there is always a Fabric node - but sometimes there's a Root Container node available (that can be reused for the selection on the Child container option), sometimes there's a Version selected, sometimes there's a Profile available. e.g. on the Profile containers view; we know the Profile to be defaulted. On the Fabric status page; the current selection defines the Profile to default. So we should be careful to ensure that the context in which the generic CreateContainerAction is used - allows the root container to be set/unset based on selections, similarly for the ProfileNode and VersionNode - so that the maximum amount of things can be auto-defaulted in the wizard to avoid the user having to re-select things
            Hide
            lhein Lars Heinemann added a comment -

            Closing issues which were not updated for >1 year. Please reopen and update the issues when needed.

            Show
            lhein Lars Heinemann added a comment - Closing issues which were not updated for >1 year. Please reopen and update the issues when needed.

              People

              • Assignee:
                lhein Lars Heinemann
                Reporter:
                jastrachan James Strachan
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development