Deploy failed 'no tty present', but no sudo?

[mcescalante]

I am trying to deploy to a production system at a large datacenter that has many firewall and security rules. I am currently using my own account as the deploy account, and the deploy makes it all the way up to the following command:

-----> Launching
       $ cd "$release_path" 
       sudo: no tty present and no askpass program specified
 !     ERROR: Deploy failed.

I have combed (and grep'd) through source but cannot find any sudo command that would be triggering this. I am aware that adding NOPASSWD to my sudoers file will mitigate this, but that isn't an option in this production environment. I also added a -v flag to the ssh options, but there were no errors in the verbose ssh output that signaled what was wrong. On the server side, the PAM module seems to be throwing a "no password detected" but that doesn't make sense since I couldn't find a place sudo was ever being run.

Does anybody have any insights as to what's going on or what I could do to help this along? Cheers 😄

[mcescalante]

Just found it, it was a sudo left in my own config file on launch. Thanks for developing such wonderful software!