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

regarding appsync env var settings, it was mentioned here that it has been included in the past release: <https://github.com/pulumi/pulumi-aws/issues/3877>
However, I can't seem to find any documentation on how to add env var to appsync instances.

I'm sorry, this issue was wrongfully closed. Support for environment variables in appsync is not implemented yet. I reopened the issue.

In the meantime you could give the <https://www.pulumi.com/registry/packages/aws-native/api-docs/appsync/graphqlapi/|GraphQlApi> from aws-native a try.
I see that that one supports configuring environment variables.

is there a big difference in both of them? asking coz i am not starting from scratch. got a couple of things running in prod already

The APIs of the two resources (`aws` vs `aws-native`) are slightly different, but you can mix&amp;match resources from both providers.

I'm not an expert in AppSync though, there could be subtle differences in the two.

looks like it doesnt support schema field. likely alot of breaking changes.

what's the fundamental differences between aws and aws-native? why are there 2 versions?

The `aws` provider has hand written integrations for the different AWS services. Due to that it can be more tailored to the specific use cases, but adding support for new features/services requires more effort.

`aws-native` on the other hand relies on <https://aws.amazon.com/cloudcontrolapi/|AWS Cloud Control> as an entry point into AWS. With this service, AWS provides a standard CRUD API for all (supported) services. Generally all services supported in AWS CloudFormation are supported here as well. Due to the generic nature of `aws-native`, it supports new features pretty much as soon as AWS adds CloudFormation support for them

Generally we recommend folks to use resources from `pulumi-aws` if they're supported in both