Medialive getInput function

[williamsbdev]

Describe what happened

We are getting an "encoder" error when trying to do a lookup of the AWS Medialive Input when trying to lookup using the getInput function (we're using the getInputOutput).

Sample program

const name = 'example';

  const inputSecurityGroup = new aws.medialive.InputSecurityGroup(name, {
    whitelistRules: [
      {
        cidr: '1.1.1.1/32',
      },
    ],
  });

  const input = new aws.medialive.Input(name, {
    name,
    type: 'RTMP_PUSH',
    destinations: [
      {
        streamName: `live/${name}`,
      },
      {
        streamName: `live/${name}-backup`,
      },
    ],
    inputSecurityGroups: [inputSecurityGroup.id],
  });

  const medialiveInputOutput = aws.medialive.getInputOutput({
    id: input.id,
  });

Log output

pulumi up --stack brandon
Previewing update (brandon):

     Type                    Name             Plan       Info
     pulumi:pulumi:Stack     brandon-brandon             1 error
 ~   └─ aws:medialive:Input  trs              update     [diff: -vpc~vpc]

Diagnostics:
  pulumi:pulumi:Stack (brandon-brandon):
    error: Error: invocation of aws:medialive/getInput:getInput returned an error: cannot derive an encoder for data source "aws_medialive_input": Cannot derive an encoder for property "destinations": issue deriving an object encoder: Cannot derive an encoder for property "vpc": when deriving converters for an element of a collection: LookupSchemaPath failed at walk.NewSchemaPath(): walk.ElementStep{} is not applicable
        at Object.callback (/Users/brandon.williams/Projects/brandon/node_modules/@pulumi/aws/node_modules/@pulumi/runtime/invoke.ts:172:37)
        at Object.onReceiveStatus (/Users/brandon.williams/Projects/brandon/node_modules/@grpc/grpc-js/src/client.ts:360:26)
        at Object.onReceiveStatus (/Users/brandon.williams/Projects/brandon/node_modules/@grpc/grpc-js/src/client-interceptors.ts:458:34)
        at Object.onReceiveStatus (/Users/brandon.williams/Projects/brandon/node_modules/@grpc/grpc-js/src/client-interceptors.ts:419:48)
        at /Users/brandon.williams/Projects/brandon/node_modules/@grpc/grpc-js/src/resolving-call.ts:163:24
        at processTicksAndRejections (node:internal/process/task_queues:77:11)

Affected Resource(s)

The getInput function for the Medialive Input.

Output of pulumi about

CLI
Version 3.111.0
Go Version go1.22.1
Go Compiler gc

Plugins
NAME VERSION
aws 6.41.0
aws 5.43.0
dynatrace 0.1.0
nodejs unknown

Host
OS darwin
Version 14.4.1
Arch arm64

This project is written in nodejs: executable='/opt/homebrew/bin/node' version='v21.6.1'

Current Stack: brandon

TYPE URN
pulumi:pulumi:Stack urn:pulumi:brandon::brandon::pulumi:pulumi:Stack::brandon-brandon
pulumi:providers:aws urn:pulumi:brandon::brandon::pulumi:providers:aws::default_6_41_0
aws:medialive/inputSecurityGroup:InputSecurityGroup urn:pulumi:brandon::brandon::aws:medialive/inputSecurityGroup:InputSecurityGroup::example
aws:medialive/input:Input urn:pulumi:brandon::brandon::aws:medialive/input:Input::example

Found no pending operations associated with brandon

Backend
Name mm-williamsb2
URL s3://pulumi-state-1234
User brandon.williams
Organizations
Token type personal

Dependencies:
NAME VERSION
@pulumi/aws 6.41.0
@pulumi/pulumi 3.93.0
rs-accounts 0.1.3
@types/jest 29.5.8
@types/node 20.9.0

Additional context

I was able to produce the expected result using Terraform:

Sample program:

terraform {
  backend "s3" {
    bucket = "pulumi-state-1234"
    key    = "app-state"
    region = "us-east-1"
  }
}

resource "aws_medialive_input_security_group" "example" {
  whitelist_rules {
    cidr = "10.0.0.8/32"
  }
}

resource "aws_medialive_input" "example" {
  name                  = "example-input"
  input_security_groups = [aws_medialive_input_security_group.example.id]
  type                  = "RTMP_PUSH"

  destinations {
    stream_name = "main"
  }
  destinations {
    stream_name = "backup"
  }

  tags = {
    ENVIRONMENT = "prod"
  }
}

data "aws_medialive_input" "example" {
  id = aws_medialive_input.example.id
}

output "destinations" {
  value = data.aws_medialive_input.example.destinations
}

Log output:

terraform apply
aws_medialive_input_security_group.example: Refreshing state... [id=5614083]
aws_medialive_input.example: Refreshing state... [id=9913515]
data.aws_medialive_input.example: Reading...
data.aws_medialive_input.example: Read complete after 0s [id=9913515]

Changes to Outputs:
  + destinations = [
      + {
          + ip   = "18.210.155.34"
          + port = "1935"
          + url  = "rtmp://18.210.155.34:1935/main"
          + vpc  = null
        },
      + {
          + ip   = "100.29.92.85"
          + port = "1935"
          + url  = "rtmp://100.29.92.85:1935/backup"
          + vpc  = null
        },
    ]

You can apply this plan to save these new output values to the Terraform state, without changing any real
infrastructure.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes


Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Outputs:

destinations = tolist([
  {
    "ip" = "18.210.155.34"
    "port" = "1935"
    "url" = "rtmp://18.210.155.34:1935/main"
    "vpc" = tolist(null) /* of object */
  },
  {
    "ip" = "100.29.92.85"
    "port" = "1935"
    "url" = "rtmp://100.29.92.85:1935/backup"
    "vpc" = tolist(null) /* of object */
  },
])

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 @williamsbdev, thanks for reporting this issue. We'll take a look, definitely looks like a bug

[flostadler]

Thanks for the example! I was able to reproduce this and pin-point it to the following issue: pulumi/pulumi-terraform-bridge#2020

Sorry that you're running into this, I'll work with the team to get this fix prioritized

[a1flecke]

Thanks for the example! I was able to reproduce this and pin-point it to the following issue: pulumi/pulumi-terraform-bridge#2020

Sorry that you're running into this, I'll work with the team to get this fix prioritized

Looking forward to this bug fix. Thanks for jumping on it

[guineveresaenger]

Hi folks! Once the changes from pulumi/pulumi-terraform-bridge#2142 are applied to AWS, you should no longer see this issue - and the registry will show the relevant docs for this type as well.

Please do re-open this issue if we missed an edge case.

[pulumi-bot]

This issue has been addressed in PR #4160 and shipped in release v6.43.0.