You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 8, 2021. It is now read-only.
Let have different configurations from the same file, based on injected variables!
Description
Well, it mostly says itself. Being able to use ENV in .graphqlgen.yml would make it quite a lot easier to change settings based on the current environment. This is useful for all kinds of situations, e.g. having separate but very alike schema files for development and production builds.
Additional context
There are several ways to accomplish this, I'd like it the most if I were able to define a file with -e | --env-file and specify variables with ${env:MY_VARIABLE}.
Let have different configurations from the same file, based on injected variables!
Description
Well, it mostly says itself. Being able to use ENV in
.graphqlgen.yml
would make it quite a lot easier to change settings based on the current environment. This is useful for all kinds of situations, e.g. having separate but very alike schema files for development and production builds.Additional context
There are several ways to accomplish this, I'd like it the most if I were able to define a file with
-e | --env-file
and specify variables with${env:MY_VARIABLE}
.This is exactly similar to the prisma cli approach, you can get more info about that implementation here.
P.S If this is already possible, I can't find the info anywhere and I'll get incredibly embarrased haha. Have a nice day!
The text was updated successfully, but these errors were encountered: