Console CI/CD backend deployment fails for Python Lambda (Unable to import module)

[dcfranca]

** Please describe which feature you have a question about? **
Ok, not exactly a cat dying, but I didn't know how to summarize it on the headline, so I decided to go with a clickbait.
To be honest, I don't know if this question fit best here or on amplify-cli, feel free to move it if needed.

I have the following scenario:
2 branches, each branch is linked to an Amplify environment
Branch: dev -> Amplify env: dev
Branch: master -> Amplify env: staging

They are connected via Amplify Console, so every time something is pushed to them, they deploy the environment, backend and frontend.

I have a lambda function, created via Amplify, which uses is a Python function, and uses docxtpl package, which uses MarkupSafe

I have a Pipfile with the following:

[packages]
docxtpl = "*"

Whenever I push the backend via amplify-cli it works fine, and my function works as expected.
However, every time I deploy it via amplify console (which means every time I update the branches), my function breaks, and I start getting the following errors on my logs:

Unable to import module 'index': No module named 'markupsafe'

What I sometimes do is adding this line to my Pipfile:

MarkupSafe = "*"

and pushing locally the backend again

But, tbh, I don't think this is the solution, it is just because it recognizes something has changed in the function and then re-deploy, because when I remove the MarkupSafe works as well

It is happening every time I happen to deploy, it is really annoying having to do it every time
Any clue what I can do to fix once for all? Or at least where to look for better debugging information?

Thanks

** Provide additional details**

[hsspain]

@dcfranca We will look into this. Can you provide your App ID and region?

[dcfranca]

@hsspain any email I can send this information to?

[hsspain]

@dcfranca [email protected]

[dcfranca]

@hsspain Sent, let me know if you need anything else.

[dcfranca]

@swaminator Any update on this issue?

I confirm that the dependencies files has nothing to do with the bug, even if I just change a counter variable and push from amplify cli it works

[dcfranca]

@hsspain @swaminator Anyone?

[dcfranca]

@swaminator @hsspain @ericclemmons @ericclemmons

[ganipcanot]

Closing due to age - please re-open if still experiencing issues.

[dcfranca]

@ganipcanot I don't understand why this was closed, I'm still waiting for response, and yes, I'm still experiencing this issue

[siegerts]

Hi @dcfranca, apologies for closing this. Reopening now to track alongside the issue that you've experienced in the CLI. We can always transfer, if needed. Also, just readjusting the title a bit to be more representative (😄 ), so that other customers are able to find if they are experiencing the same.

[dcfranca]

@siegerts Thanks :)

[Jordan-Mesches]

I have the exact same problem, in my staging branch where I push the backend using the cli works completely fine, but in my prod branch's backend( which get's pushed in the console when it see's a new git commit), doesn't work and says Runtime.ImportModuleError: Unable to import module 'index': No module named 'markupsafe'

[dcfranca]

Thanks @Jordan-Mesches, now I don't feel so alone with this issue :D
It seems to be direct related to the markupsafe dependency for some reason

[Jordan-Mesches]

So has anyone figured out a solution to this problem?

[dcfranca]

@Jordan-Mesches Unfortunately, it doesn't seem so =/

[stemwinder]

This is also occurring for us across three lambdas we are trying to add to our Amplify project. None of the three are picked up by Amplify Console when it creates virtual environments and builds the functions.

EDIT: I was able to correct this by manually adding an amplify.state file to the root of the Lambdas' directories.

[josefaidt]

Hey @dcfranca and @stemwinder apologies for the delay here, but I wanted to confirm whether y'all were still experiencing this issue?

[dcfranca]

Hey @dcfranca and @stemwinder apologies for the delay here, but I wanted to confirm whether y'all were still experiencing this issue?

I haven't used Amplify for years now, so I don't know if this is still happening

[josefaidt]

Sorry about that @dcfranca I know it's been a few years on this one :/ I'll close this out for now as we have not received recent reports around this behavior, but will keep it in mind the event we do receive a report

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.