update corellium API client and remove webplayer

[henrybarreto]

closes #2

[henrybarreto]

@Manouchehri, I was debug and noticed this message.

It seems to indicate that some AWS configuration is missing. Am I right?

Could you, please, confirm that our AWS variables are set?

[Manouchehri]

This is what we have set:

Hmm, nothing here should ever be contacting AWS, since we aren't even using AWS for our S3 bucket (we're using Backblaze B2). =P

https://developer.hashicorp.com/terraform/language/settings/backends/s3

It looks like we're missing one of these options for that failing test?

[henrybarreto]

This is what we have set:

Hmm, nothing here should ever be contacting AWS, since we aren't even using AWS for our S3 bucket (we're using Backblaze B2). =P

https://developer.hashicorp.com/terraform/language/settings/backends/s3

It looks like we're missing one of these options for that failing test?

Nice tip! I added the skip for the account ID to check if we get a good result.

[henrybarreto]

Perfect! The skip solved one issue, but emerged another one.

It seems that backblaze doesn't allow some headers that target to S3.

Unsupported header 'x-amz-sdk-checksum-algorithm' received for this API call.

The backblaze documentation has a text snippet talking about it:

I have found this problem in others project too.

• https://www.drupal.org/project/backup_migrate_aws_s3/issues/3355375
• https://forums.percona.com/t/unsupported-header-x-amz-checksum-algorithm-breaks-pitr-backup/24758
• https://forum.mattermost.com/t/can-connect-to-b2-via-s3-setting-but-till-cannot-upload-any-file/15351

What do you think we could do in this case?

[Manouchehri]

Hmm, yeah maybe this is a Backblaze issue. https://github.com/hashicorp/terraform/issues/34054

Is it okay if I go ahead and switch the creds and S3 endpoint to use IDrive again?

[Manouchehri]

Switching now to IDrive E2, one sec.

[henrybarreto]

Hmm, yeah maybe this is a Backblaze issue. hashicorp/terraform#34054

Is it okay if I go ahead and switch the creds and S3 endpoint to use IDrive again?

I think so

[Manouchehri]

Done, I have switched to IDrive E2. Can you try it out to see if it gets further?

[henrybarreto]

Done, I have switched to IDrive E2. Can you try it out to see if it gets further?

Of course. I will rerun and check it again.

[Manouchehri]

Let me try emptying the bucket (which had old files in it).

[Manouchehri]

Okay, I nuked all the files in the bucket. It's empty now, try rerunning.

[Manouchehri]

I feel like I'm doing something stupid with the bucket config due to lack of sleep. =P

Going to call it a night and look at this tomorrow again to see what I'm doing wrong. =)

[henrybarreto]

I feel like I'm doing something stupid with the bucket config due to lack of sleep. =P

Going to call it a night and look at this tomorrow again to see what I'm doing wrong. =)

Me too lol

Tomorrow we check this problem again.

[henrybarreto]

@Manouchehri, could we run the tests again to remind what the problem it raises?