Skip to content

Bug/work around authorizenet bug #670

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

Conversation

jusdino
Copy link
Collaborator

@jusdino jusdino commented Mar 24, 2025

Authorize.Net's python SDK, authorizenet currently has a bug that makes it uninstallable in environments that use the latest of python-maintained library management tools. Specifically, setuptools, with version 78+ stopped supporting some long-deprecated configuration arguments, which the authorizenet library still uses. In the hopes that Authorize.Net will quickly remedy this bug, we have adopted a temporary work-around to unblock our deploy pipelines: We've custom-built a docker image for building our lambdas that includes a downgraded version of setuptools.

This work-around is far from an ideal solution, so we should discuss it carefully before approving. Unfortunately, it is also the only short-term solution I can see to getting our pipeline unblocked.

Description List

  • Add a Dockerfile to build a custom SAM python lambda builder image with downgraded setuptools
  • Update PythonLambda to use this custom image, as hosted in a public registry we've created for the purpose

Testing List

  • Code review

@jusdino
Copy link
Collaborator Author

jusdino commented Mar 24, 2025

Work-around is OBE: setuptools released another update where they postponed pulling support for the deprecated config.cfg fields. So long as authorize.net updates before 2026, we should be OK.

@jusdino jusdino closed this Mar 24, 2025
@jusdino jusdino deleted the bug/work-around-authorizenet-bug branch March 24, 2025 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant