-
Notifications
You must be signed in to change notification settings - Fork 875
bug: remove the need for expects' unbuffer command while using coder cli to push a template #17033
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for reporting. I have also seen this error intermittently. It's a good investigation to try to find the root cause. |
Have you tried to push with |
shows no such command like that on push. same for global help
I do see in source code there is mention of force-tty Line 65 in b791672
I guess I can give it a try. Thanks. |
Yes, that works...
|
So,... as stated I suppose you could say the bug is "fixed" since |
Is there an existing issue for this?
Current Behavior
cli version
Coder v2.20.0+03b5012 Tue Mar 4 19:21:19 UTC 2025
(I tried a new cli as well, same issue)
I'm working in a GitHub Actions Workflow environment.
I have an on-prem Coder Server install (Coder v2.20.0+03b5012 Tue Mar 4 19:21:19 UTC 2025)
I'm using coder cli and an access token provided vie GH secrets
I have a directory with a pre-existing and previously pushed template (shown from within GH Action WF)
when I issue
coder template push docker --ignore-lockfile -y
I get this error...
I double-triple confirmed that the directory this was running in had the
main.tf
file.I got suspicious, so I ssh'd into the runner and manually replicated the command, (over ssh) and it succceeded!
So, I got took that knowledge and made a wild guess that there is a requirement that tty-like relationship is expected to the cli.
I changed the gh wf to install
expect
and that allows me to add
unbuffer
before the whole command.And that works.
Relevant Log Output
Expected Behavior
I should not have to use
unbuffer
or any other tty-like command in a headless environment to engage withtemplates push
Steps to Reproduce
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: