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
The Secrets UI for an environment is currently only available for Docker Swarms. However, podman understands secrets just fine. Stacks created under podman have no issue working with secrets, there's just no interface for creating or reviewing them. Instead I am stuck ssh'ing into the underlying host and running podman as root to create and manage the secrets I use.
Describe the solution you'd like
The Secrets UI should be available for environments operating under either podman or quadlet. Portainer seems to be able to detect both of these situations currently (as it's displayed under the Environment Info pane already).
Describe alternatives you've considered
I considered using git-crypt to store secrets more easily, but there's no way to configure the git deployment trigger for stacks to use that.
Additional context
podman (and quadlet) support secrets, so let's allow the portainer secret UI to interact with them!
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
-
Is your feature request related to a problem? Please describe
The Secrets UI for an environment is currently only available for Docker Swarms. However, podman understands secrets just fine. Stacks created under podman have no issue working with secrets, there's just no interface for creating or reviewing them. Instead I am stuck ssh'ing into the underlying host and running podman as root to create and manage the secrets I use.
Describe the solution you'd like
The Secrets UI should be available for environments operating under either podman or quadlet. Portainer seems to be able to detect both of these situations currently (as it's displayed under the Environment Info pane already).
Describe alternatives you've considered
I considered using git-crypt to store secrets more easily, but there's no way to configure the git deployment trigger for stacks to use that.
Additional context
podman (and quadlet) support secrets, so let's allow the portainer secret UI to interact with them!
Beta Was this translation helpful? Give feedback.
All reactions