-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support environment variables for AppSync #3877
Comments
Thanks for the feature request @stooj ! At a glance it appears that https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/appsync_graphql_api could have supported environment variables, in which case this Pulumi projected provider would land the functionality as well, does that look right? I'm not yet very familiar with AppSync so double-checking. It appears there are no issues tracking this upstream yet, but if this is what's needed I can open one. |
Thanks @t0yv0 - I agree that it needs an upstream issue. I'll open one up. |
Appsync env vars are supported in the terraform aws-sdk-go-v2 sdk, but the AppSync service in the terraform provider has not been ported to v2 yet: https://github.com/hashicorp/terraform-provider-aws/blob/main/internal/service/appsync/graphql_api.go There is an open issue and an unmerged PR that will close this issue once it gets merged and released. |
I stumbled across this issue trying to track down the same feature. The aforementioned unmerged PR is now merged. 🙂 |
Which was included in v6.42.0 of pulumi-aws. 🎊 @SethThomas - are they still not working or are you using an older version? |
The upstream issue got closed, and we received confirmation that it works on our side, closing |
This issue is not resolved yet. The upstream provider did upgraded the appsync SDK to use But upstream did not implement this feature yet, so this is not exposed in any way. Support for it is tracked here: hashicorp/terraform-provider-aws#38051 |
In the meantime you could give the |
Hello!
Issue details
AWS AppSync supports environment variables in GraphQL resolvers and functions.
When managing graphQL resources, could we have an option to manage the environment variables as well?
Docs to configure env vars using the cli
Affected area/feature
The text was updated successfully, but these errors were encountered: