Skip to content

[Feature Request] Deploy options for Git stacks #1272

Description

@radoeka

Problem statement

Triggered by the menu option that was added with #152, I started to look into the stack action buttons.

1. Button Order

Are the buttons 1 and 2 in the following screenshot doing the same/similar action, but one for a Git stack and the other for a Dockhand managed stack?

Image

If they're doing the same action can they/should they be put in the same column => should the rocket icon (2) be moved to column 1. Or should icon 1 be moved to column 3?

If that (move icon 1 or 2) will be done, all the log icons would be in the same column instead of either in column 2 or 3.... follow the red vertical line (it is not a straight line).

2. Redeploy options for the Git sync action button

If one clicks on the rocket icon (1) in the screenshot below, a redeploy menu pops up:

Image

This menu does not pop up for the Git sync button. The Git sync action button results in the following confirmation box:

Image

But there are no redeploy options. Shouldn't these redeploy options (similar to the Dockhand managed stack) be offered here as well? The options can be enabled permanently in the Git stack edit window. However, the 1 time option to activate redeploy options via Git sync action button misses, it seems.

Is it an idea to add them, or is there another design philosophy for Git stacks (gitops) compared to Dockhand managed stacks?

3 More multi selection action buttons

From Discord:

or even better "redeploy and pull all stacks with updates" would be 10/10

  • Is it possible to add a button to "select stacks with updates"? (the button could show up, after a multiple selection checkbox is clicked)
  • Once these stacks have been selected execute (a new) action button: Redeploy
  • The redeploy button should then result in the popup window with Pull, Build images, Force recreate options (looks a bit heavy to me when it is done for many stacks, but if it is possible, why not)
Image

Proposed solution

See previous section

Alternatives considered

Leave as it is, but then not all the same icons are under each other.

Additional context

NA

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions