Version
latest
Bug Description
When creating a new stack, after entering the compose yaml text, if you press "Save All" without first using the "CTRL-S" save keyboard command, the stack will be "saved" but the compose yaml entered is not. In this scenario it does not prompt for individual container icons/webUI information.
However, when editing an existing stack, if you make a change to the stack compose YAML, pressing the Save All button does appear to save the changes (it briefly flashes the container icon/webUI dialog in this scenario.
I think this is 100% repro -- it happened to me multiple times, however now I'm sess certain
Expected Behavior
Save All should save everything changed (even new documents created) for a stack when pressed.
Steps to Reproduce
- Install compose.plugin
- Press "New Stack"
- Give Stack a name/description
- Enter some compose yaml into the stack compose window
- Press "Save All" button.
Relevant Logs
Compose
Additional Context
No response
Version
latest
Bug Description
When creating a new stack, after entering the compose yaml text, if you press "Save All" without first using the "CTRL-S" save keyboard command, the stack will be "saved" but the compose yaml entered is not. In this scenario it does not prompt for individual container icons/webUI information.
However, when editing an existing stack, if you make a change to the stack compose YAML, pressing the Save All button does appear to save the changes (it briefly flashes the container icon/webUI dialog in this scenario.
I think this is 100% repro -- it happened to me multiple times, however now I'm sess certain
Expected Behavior
Save All should save everything changed (even new documents created) for a stack when pressed.
Steps to Reproduce
Relevant Logs
Compose
Additional Context
No response