No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

You can detect it using Pulumi policies (<https://www.pulumi.com/docs/using-pulumi/crossguard/>) or by associating your own logic with your Route53 records - maybe using a builder or factory, or a wrapping resource with a proxy setter that includes extra validation, or anything along those lines.

The logic could be added to the provider package, too. Maybe this is your chance to join the <#CB81H6DG9|> community? :)

Thanks Paul! It may solve this particular Route53 Record issue, but not others. There may be other ways that causes an invalid aws api call

Yes, always. Some of them are completely undetectable to Pulumi even with the most strict checks. S3 bucket names have to be globally unique: there's no way to check without actually attempting to create an S3 bucket (as far as I know).