Replies: 1 comment
-
Could this be extended to all json definition? I'd like to create a template for our mock server where container port is fixed and user should choose only host port e.g |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is your feature request related to a problem? Please describe.
Nope...
Describe the solution you'd like
Currently Portainer stack templates (type=2 or 3) must supply a hardcoded url and stackfile to specify the correct stack file to include. In our case it would be great if the "stackfile" could be dynamically set based on a UI variable.
For example, we have to support 4 different platforms/environments for our stacks to run on, each of which requires a unique stack file for various differences (image arch, volumes, etc). Currently that means we need to create 4 different stack templates for Portainer, each pointed to their respective stackfile.
What would be great is if we could use one of the UI variables to set/modify that stackfile location. For example, we'd include an env variable like:
and then potentially use it in some way like:
Such that 1 app template could service multiple platforms/environments, which in our case would reduce the app template list by 3/4's.
Describe alternatives you've considered
Potentially the "stackfile" param could just allow for UI based variables directly just as the "env" section does currently. Off hand I'm not sure if that would entail more work or not though.
Additional context
Thanks for your work here... super helpful project :)
Beta Was this translation helpful? Give feedback.
All reactions