error:   sdk-v2/provider2.go:509: sdk.helper_schema: reading Route 53 Record (Z0XXX_s1-XXX_CNAME): operation error Route 53: GetHostedZone, serialization failed: serialization failed: input member Id must not be empty: provider=aws@6.77.0

error: Preview failed: refreshing urn:pulumi:projectprod::xxx_s1::aws:route53/record:Record::s1-XXX-YYY-record: 1 error occurred:
        * reading Route 53 Record (Z0XXX_s1-xxx_CNAME): operation error Route 53: GetHostedZone, serialization failed: serialization failed: input member Id must not be empty

I am facing the above error in Pulumi

Go

during refresh. Steps to reproduce: 1. Read an existing zone using below code:

proute53.LookupZoneOutput(ctx, proute53.LookupZoneOutputArgs{
		Name:        pulumi.String("<http://xxx.yyy.com|xxx.yyy.com>"),
		PrivateZone: pulumi.Bool(false),
	}, pulumi.Provider(p))

2. Plan and Apply to create a route53 record

publicXxxRecord, err := proute53.NewRecord(base.Ctx, fmt.Sprintf("%s-public-xxx-record", *xxxId), &proute53.RecordArgs{
		Name:   pulumi.Sprintf("%s-xxx", *xxxId),
		Type:   pulumi.String(proute53.RecordTypeCNAME),
		ZoneId: pulumi.String("Z0XXX"),
		Ttl:    <http://pulumi.Int|pulumi.Int>(300),
		Records: pulumi.StringArray{
			loadBalancer.xxx.LoadBalancer.DnsName,
		},
	})
	if err != nil {
		zlog.WithError(err).Errorf("Failed to create public xxx record for %s", base.Service)
		return nil, errors.New("failed to create public xxx record")
	}

3. Till here it works fine. Now do

pulumi refresh

and it breaks with the above error. The stack json looks fine and does not have any missing attributes. What am I doing wrong? I am using

<http://github.com/pulumi/pulumi-aws/sdk/v6|github.com/pulumi/pulumi-aws/sdk/v6> v6.77.0

<http://github.com/pulumi/pulumi/sdk/v3|github.com/pulumi/pulumi/sdk/v3> v3.162.0

<http://github.com/aws/aws-sdk-go|github.com/aws/aws-sdk-go> v1.55.6

<http://github.com/aws/aws-sdk-go-v2|github.com/aws/aws-sdk-go-v2> v1.36.3

Slack Conversation

Looks similar to this thread: https://pulumi-community.slack.com/archives/CRH5ENVDX/p1744785477524499

It is the same thread

Oh yeah, I see... did you post this to both channels or does #C84L4E3N1 somehow get it automatically?

I forwarded it to #C84L4E3N1