-
Notifications
You must be signed in to change notification settings - Fork 107
Deployment Error: teradatasqlalchemy Module Not Found on Azure #1648
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
Hello @Mikeflames , I am happy to check more details on it. could you please try SCM_DO_BUILD_DURING_DEPLOYMENT and ENABLE_ORYX_BUILD are set to true and see verify if you are still facing the same issue. if yes, please share me an requirement.txt pls |
Could please share me an requirement.txt ? |
Libraries :- Specifically used this import :-
|
I have used Blob trigger , but it cannot connect on deployed Azure Function :- On Local everything works fine |
Hi @Mikeflames Please check this and see if it helps: #1299 (comment) |
Hi @Catastrophe1 , I tried the above solutions , didn't worked , have attached SS above. |
Hi Team , any Updates have been facing this issue ,tried approaches but didn't worked out ? |
Hi @Sagarthore11 / @Catastrophe1 , Any Work-arounds ? I also tried this fix to register module explicitly, but that too didn't worked out :-
|
I am experiencing a deployment issue with my Azure Function where the teradatasqlalchemy module is not recognized during deployment, despite working correctly locally. The error messages are as follows:
2025-03-07T09:51:43Z [Error] Failed to create engine: No module named 'teradatasqlalchemy.dialect' 2025-03-07T09:51:43Z [Error] Teradata data fetch/store error: No module named 'teradatasqlalchemy.dialect'
Local Setup: Everything works as expected.
Azure Deployment:The error occurs during deployment.
The teradatasqlalchemy module should be correctly installed and recognized during Azure deployment, allowing the Azure Function to run without errors.
Attempted Solutions
Verified that teradatasqlalchemy is correctly listed in requirements.txt.
Attempted to disable remote build by setting ENABLE_ORYX_BUILD = false and SCM_DO_BUILD_DURING_DEPLOYMENT = 0.
Additional Context
This issue seems related to how dependencies are handled during remote builds in Azure. Any assistance in resolving this would be greatly appreciated.
Similar Issue which was closed #1299
The text was updated successfully, but these errors were encountered: