You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently when you create a stack using a Compose stack template (i.e. template type = 3) which makes use of UI variables, it results in stack yaml that is not very friendly to edit or analyze. When editing the resulting stack in Portainer, none of the UI variables are made available in the UI for editing, nor are they physically replaced in the stack yaml. So, for example you may end up with something like:
Where UI template variables such as UR_LOCAL_PORT were/are set, but you can't see or edit the value. You can replace the ${UR_LOCAL_PORT} variable expansion to manually make a change, but that's not the best experience.
Describe the solution you'd like
Ideally I'd like to see the template UI variables made available for editing on the stack edit page -- set to their current values.
If that poses a problem, then at least replacing the variable expansions in the stack, so that you're editing a traditional stack template without "hidden" variable values still involved.
Describe alternatives you've considered
Open to anything, but those are the two I think could help. :)
This discussion was converted from issue #2750 on July 27, 2023 04:25.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
Currently when you create a stack using a Compose stack template (i.e. template type = 3) which makes use of UI variables, it results in stack yaml that is not very friendly to edit or analyze. When editing the resulting stack in Portainer, none of the UI variables are made available in the UI for editing, nor are they physically replaced in the stack yaml. So, for example you may end up with something like:
Where UI template variables such as
UR_LOCAL_PORTwere/are set, but you can't see or edit the value. You can replace the${UR_LOCAL_PORT}variable expansion to manually make a change, but that's not the best experience.Describe the solution you'd like
Ideally I'd like to see the template UI variables made available for editing on the stack edit page -- set to their current values.
If that poses a problem, then at least replacing the variable expansions in the stack, so that you're editing a traditional stack template without "hidden" variable values still involved.
Describe alternatives you've considered
Open to anything, but those are the two I think could help. :)
Beta Was this translation helpful? Give feedback.
All reactions