1433148 - upgrade to boto3

Status: RESOLVED FIXED

(Socorro :: General, task, P2)

Description

[Will Kahn-Greene [:willkg] ET needinfo? me]

Socorro currently uses boto2, but Antenna uses boto3 and all future projects will use boto3. The moto project (which I'm looking at for mocking AWS things) uses boto3.

The boto2 docs suggest that boto3 is recommended for use and all new feature work is being done in boto3.

Miles prefers boto3.

Given that, we should upgrade to boto3. It's the future. It'll make our lives easier.

This bug covers upgrading Socorro from boto2 to boto3.

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

Making this a P2. This plus bug #1425475 will simplify some our multi-environment auth configuration. It's worth at least looking into how complicated it is.

Comment 2

[Will Kahn-Greene [:willkg] ET needinfo? me]

This would be helpful to do at some point probably in conjunction with rewriting the processor, but we've dealt with all the issues at this point and can push this off.

Comment 3

[Will Kahn-Greene [:willkg] ET needinfo? me]

I'm going to WONTFIX this. We're switching to GCP this year and given that, there's no point to upgrading to boto3 first.

Comment 4

[Will Kahn-Greene [:willkg] ET needinfo? me]

Reopening this because we're not going to GCP.

Comment 5

[Will Kahn-Greene [:willkg] ET needinfo? me]

Making this a P2 and block switching to SQS because we really want to be using boto3 to do that.

Comment 6

[Will Kahn-Greene [:willkg] ET needinfo? me]

Grabbing this to work on next.

Comment 7

[Will Kahn-Greene [:willkg] ET needinfo? me]

Attachment: pr 5032: bug 1433148: redo retry

Comment 8

[Will Kahn-Greene [:willkg] ET needinfo? me]

willkg merged PR #5032: "bug 1433148: redo retry" in 84ed509.

Comment 9

[Will Kahn-Greene [:willkg] ET needinfo? me]

Attachment: pr 5039: bug 1433148: switch from boto to boto3

Comment 10

[Will Kahn-Greene [:willkg] ET needinfo? me]

willkg merged PR #5039: "bug 1433148: switch from boto to boto3" in 9951f9c.

This will autodeploy to stage. The plan is to let it sit on stage and fix any issues that come up, then do a prod deploy in December.

Comment 11

[Will Kahn-Greene [:willkg] ET needinfo? me]

Pushed this to prod just now in bug #1600745. Everything looks super!