Skip to content
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

Enhancement request: per-environment headers #11

Closed
karmajunkie opened this issue Dec 7, 2016 · 2 comments
Closed

Enhancement request: per-environment headers #11

karmajunkie opened this issue Dec 7, 2016 · 2 comments

Comments

@karmajunkie
Copy link

I typically have headers that vary on a per-environment basis, e.g. JWT auth tokens that are use different keys between dev, staging and prod. It would be a great enhancement to be able to add these to the environment, which right now allows for setting variables but not the headers.

Many thanks for the hard work!

@andevsoftware
Copy link
Contributor

andevsoftware commented Dec 7, 2016

@karmajunkie Hi, Since 1.1 it's possible to set headers on the environment level. Although I think in your case project level headers would be enough if the handling of those headers is the same on each environment. You could for example add the header Authorization: {{authToken}} to the project and set the authToken variable with a different token value on each environment.

@karmajunkie
Copy link
Author

Ahh, I see, I misunderstood the role of variables here. I was thinking that they were used as defaults for the graphql variables. I might suggest a link to some documentation around that or something, but otherwise I see now how to accomplish what I was looking for. I'll close this, thanks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants