Restrict auth tokens to certain actions (create-deploy)

Features
, ,
#1

As far as I can tell personal access tokens allow any actions. We’d like to limit the allowed actions to only create a deploy in case a key leaks and a malicious actor e.g. deletes a site.

Context

We’d like to move from netlify’s CD platform to azure since Azure is twice as fast and has way more free minutes.
It seems like we can already do that with the netlify cli (build+deploy) but we need an access token. Since we’d also like to build pull requests from forks we would need to make that token available to these PRs. While there are certain measures in place to prevent leaking it’s never 100% safe. We’d be fine with potential leakage if that only results in deploys being created. But e.g. removing sites is to great of a risk.

#2

Great suggestion, @eps1lon! We don’t have it implemented yet, but I have added your voice to our existing feature request.

However, you don’t have to do this in the way you describe; we already have good support for building PR’s against your repo though, without your contributors doing anything, as long as you (not they) configure builds from git.

But yes, “limited scope” access tokens to allow CLI usage are not available today. We’ll follow up in this thread if we make them available! Not clear that we will, but we’ll see what time brings :slight_smile:

#4

However, you don’t have to do this in the way you describe; we already have good support for building PR’s against your repo though

This is not our observation. Building on netlify is slow due to limited resources and requires extra payment from our side. Azure has stronger and cheaper resources which is why we want to offload building onto azure.

#5

Thanks for that feedback!