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

Allow for authentication via specifying access token or path to config.json #123

Closed
alex-p-chan opened this issue Sep 22, 2018 · 3 comments

Comments

@alex-p-chan
Copy link

Currently there is no way to login by specifying the location of the config.json or a similar method to netlifyctl, where you specify the access token.

It would be great if this feature were added in the cli.

@alex-p-chan alex-p-chan changed the title Allow for login via specifying access token or path to config.json Allow for authentication via specifying access token or path to config.json Sep 22, 2018
@bcomnes
Copy link
Contributor

bcomnes commented Sep 24, 2018

Use the NETLIFY_AUTH_TOKEN and NETLIFY_SITE_ID env vars. I am currently refreshing the docs to make this clearer.

Curious to know what your use cases are as well. CI deployments? Anything else?

jennybc added a commit to rstats-wtf/what-they-forgot that referenced this issue Sep 26, 2018
@bcomnes
Copy link
Contributor

bcomnes commented Sep 26, 2018

Closing this unless there are other open issues. Let me know!

@bcomnes bcomnes closed this as completed Sep 26, 2018
@bobinrinder
Copy link

Why is this not documented? We would like to deploy from a Third Party CI solution. What do we have to do? Can I call deploy if I have the NETLIFY_AUTH_TOKEN and NETLIFY_SITE_ID set? If so, where do I get that NETLIFY_AUTH_TOKEN? And what is my NETLIFY_SITE_ID , the API ID or the Site Name?

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

3 participants