Impact on original macros due to the upgrade to the latest Python connector

[T-Ishii]

皆さんこんにちは。最新の Python コネクタへのアップグレードによる元のマクロへの影響について質問があります。

9月1日にAlteryx 2023.2から2024.2にアップグレードします。

このアップグレードには、最新の Python コネクタ (バージョン 3.1.0) のみが含まれる予定です。

現在、Alteryxコミュニティで作成された添付のマクロを使用しています。
最新のPythonコネクタのみが含まれるAlteryx 2024.2でもこのマクロが引き続き動作するか確認できる場所をご存知でしたら、ご教示いただければ幸いです。

また、マクロに変更が必要な場合は、必要な具体的な変更内容を共有していただけると非常に助かります。

お手数をおかけしますが、ご返信をよろしくお願いいたします。

[Gaurav_Dhama_ · Accepted solution]

From the look of it, does not look like there should be any major change, if any.

I would recommend that you open this code in Visual Studio and install python 3.10 in your system, create an environment with 3.10 and test it. If it fails, you can fix it there. By this you will know if there will be any change or not, and if there is you will already have a working code as backup once you make the changes in visual studio. So, your projects will have minimum impact.

[apathetichell · Accepted solution]

Hey @T-Ishii so the main issue is actually Alteryx specific connectors --- not because of the underlying code --- but because Alteryx tells Designer to look at specific locations for those tools --- and the specific locations use python3.8 in the directory structure. This should not be an issue with your macro.

While it's certainly possible you may have minor issues --- Boto3 is basically stable cross version (at least for things like S3 object actions). I would personally avoid python entirely in your case and use AWS CLI via run command tool. 

[apathetichell]

Also --- for best practice --- I'd recommend removing your attachment to your first post... While it's unlikely an AWS role would be an attack vector --- it's usually best policy to keep ARN's for roles secret. I personally try to keep S3 bucket names private as well. Both show up as cached in the .yxmc file.

[T-Ishii]

Thank you for your response! I'm relieved to hear that there’s no impact. Also, I’ve deleted the attached file. Thank you for the advice.