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

how to store env variables #9

Closed
adrai opened this issue Mar 3, 2016 · 1 comment
Closed

how to store env variables #9

adrai opened this issue Mar 3, 2016 · 1 comment
Labels

Comments

@adrai
Copy link

adrai commented Mar 3, 2016

https://github.com/claudiajs/claudia-api-builder/blob/master/README.md#the-request-object

have I to update the claudia.json file to automatically save/update additional stage variables?

@gojko
Copy link
Member

gojko commented Mar 3, 2016

no, you should set the stage variables in AWS directly. I don't like keeping stage variables inside the project folder structure because they often contain secret access keys.

You can set stage variables from the AWS web console (see Set Stage Variables Using the Amazon API Gateway Console), or using the AWS CLI, like this:

aws apigateway create-deployment --rest-api-id API_ID \
  --stage-name production --variables accessKey=5465876375e273re

See the DynamoDB CRUD example project for an example of how that's used.

it is good to use the set-version claudia command to create a completely new stage before you set the vars for the first time, as it will save you manual access configuration.

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

No branches or pull requests

2 participants