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
Following up on #341, we should look at a way to have piku "step out of the way" for unfettered ssh sessions, probably depending on a specific key. Quoting myself from that thread:
You'd do --passthrough (or add an environment variable to authorized_keys, which actually seems better) to "open up" for extra commands, with piku only handling deploys.
Then you could set up another key with the default "restricted" behavior for CI. We'd probably even remove the run command, since I keep forgetting to use '-t' for sane terminal handling
There are some security implications here, but I too would like to avoid having to do workarounds (like logging in as another user) just to get at the piku environment for some trivial app-specific tasks, and don't really like using the run command.
The text was updated successfully, but these errors were encountered:
Following up on #341, we should look at a way to have
piku
"step out of the way" for unfetteredssh
sessions, probably depending on a specific key. Quoting myself from that thread:There are some security implications here, but I too would like to avoid having to do workarounds (like logging in as another user) just to get at the
piku
environment for some trivial app-specific tasks, and don't really like using therun
command.The text was updated successfully, but these errors were encountered: