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
This seems fairly clearly that the PIP_EXTRA_INDEX_URL is 'somehow' not on the lambda environment. as far as I can tell the only way to manipulate that environment is via pre-install scripts? I might be missing something obvious but I can't find anything in the documentation.
The text was updated successfully, but these errors were encountered:
I'm not sure yet if the best solution would be to stuff all the commands together in a shell script and execute it, or to let the user specify environment variables. If we use a shell script, we lose the ability to tell the user exactly which command failed. If we allow environment variables, the user still won't be able to set dynamic environment variables (e.g. get token and set that as the password).
If you're looking for a quick solution, you might be able to write the export line into ~/.bash_profile for it to be loaded by the following commands.
I'm having trouble getting turbolayers to work when using a private pypi repo. Chosen dependency management is pipenv
the lock file contains
with PIP_EXTRA_INDEX_URL being exposed on the environment
attempting to do something like this
will generate the error
This seems fairly clearly that the PIP_EXTRA_INDEX_URL is 'somehow' not on the lambda environment. as far as I can tell the only way to manipulate that environment is via pre-install scripts? I might be missing something obvious but I can't find anything in the documentation.
The text was updated successfully, but these errors were encountered: