AWS Connect error getting ContactFlow

[jrwpatterson]

Describe what happened

Trying to run the aws.connect.getContactFlow or new aws.connect.getContactFlow I am getting an error.

I believe it is related to this bug aws/aws-sdk-go-v2#2909

Sample program

await aws.connect.getContactFlow({
          instanceId: connectExisting.id,
          name: "ExampleConnectFlow",
        });

Log output

 reading Connect Contact Flow: operation error Connect: DescribeContactFlow, https response error StatusCode: 200
, RequestID: 109c6b92-287f-4715-b63f-ec1a5ea64bb5, deserialization failed, failed to decode response body with invalid
 JSON, expected Boolean to be of type *bool, got string instead
    at Object.callback (/.sst/platform/node_modules/@pulumi/aws/node_modules/@pu
lumi/runtime/invoke.ts:285:37)
    at Object.onReceiveStatus (/.sst/platform/node_modules/@grpc/grpc-js/src/cli
ent.ts:360:26)
    at Object.onReceiveStatus (/.sst/platform/node_modules/@grpc/grpc-js/src/cli
ent-interceptors.ts:458:34)
    at Object.onReceiveStatus (/.sst/platform/node_modules/@grpc/grpc-js/src/cli
ent-interceptors.ts:419:48)
    at /.sst/platform/node_modules/@grpc/grpc-js/src/resolving-call.ts:132:24
    at processTicksAndRejections (node:internal/process/task_queues:85:11) {
  promise: Promise { <rejected> [Circular *1] }

Affected Resource(s)

No response

Output of pulumi about

Using SST on Pulumi

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[flostadler]

Hey @jrwpatterson, so sorry you're running into this issue!
You're correct that this is related to this bug (aws/aws-sdk-go-v2#2909) in the AWS SDK. The Amazon Connect service is incorrectly serializing the IsDefault field of ContactFlow as a string.

This is the upstream bug issue we're tracking for this to be resolved: hashicorp/terraform-provider-aws#40267.

If AWS fixes this server side and starts returning the right data type this should start working again automatically. In case they align the SDK with the service, we'll have to pull in an updated version of the SDK through our upstream provider.
We'll monitor the linked issues to resolve this ASAP once the upstream issues are resolved.

[jrwpatterson]

@flostadler hashicorp/terraform-provider-aws#40419 it looks to be updated if we can get a fix!

[flostadler]

@jrwpatterson it doesn't look like upstream made any changes, the linked PR is just an update to the changelog. Seems like AWS fixed it server side. Can you retest and check if this is fixed for you now?