requirements.txt generated incorrectly when run using ansible on Debian 8

[abadyan-vonage]

I have a weird use case...
Running serverless deploy using the ansible module on a machine with Debian 8.
I am using a Pipfile (doesn't matter what's in it, I tried using an almost empty one too):

[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]


[dev-packages]

[requires]
python_version = "3.6"

The generated requirements.txt file then looks like this:

-i https://pypi.org/simple
^M⠋ Running..^M⠙ Running..^M⠹ Running..^M⠸ Running..^M⠼ Running..^M⠴ Running..^M⠦ Running..^M⠧ Running..^M⠇ Running..^M⠏ Running..^M⠋ Running..^M⠙ Running..^M⠹ Running..^M⠸ Running..^M⠼ Running..^M⠴ Running..^M⠦ Running..^M⠧ Running..^M⠇ Running..^M⠏ Running..^M⠋ Running..^M⠙ Running..^M⠹ Running..^M⠸ Running..^M✔ Complete

This doesn't happen when I run on macOS or when I use sls deploy directly (no ansible module).

Any ideas on root cause here?

[dschep]

That's peculiar. @ryansb, you use ansible with sls, any thoughts?

[ryansb]

That doesn't look like an ansible issue - my bet is that it's because the ansible module does the shell-out to SLS, and python-serverless-requirements is missing something that it would normally get from the env.

The Ansible module won't give all the env vars of the caller to the SLS command, so check that you don't have any major ${env:...} usages involved.

[abadyan-vonage]

@ryansb What do you mean? We do use env vars quite a lot, is that not supported with this plugin?

[AndrewFarley]

Just adding a label for visibility. If this is still an issue with the latest release of this project please respond, otherwise we will close