How to use a service account for CI deployments
See original GitHub issueRunning clasp login
sets up a .clasprc
file with a token that seems to last about a week.
Is there any way to get some kind of authentication working that could work in a headless setup like CI (E.g. GitHub Travis or Bitbucket Pipelines) please?
I looked at https://script.google.com/home/usersettings which has a switch for the API, but nothing about service tokens.
Note from @grant, please upvote this bug! https://issuetracker.google.com/issues/36763096
Issue Analytics
- State:
- Created 5 years ago
- Reactions:48
- Comments:48 (14 by maintainers)
Top Results From Across the Web
Best practices for using service accounts in pipelines
Avoid attaching service accounts to VM instances used by CI/CD systems; Use dedicated service accounts per deployment pipeline; Use workload identity ...
Read more >Service Accounts: A Path to CI/CD Automation - Harness
We discuss Service Accounts, API Keys, and how DevOps teams can use them to build scalable and maintainable CI/CD infrastructure.
Read more >Setting up a Kubernetes CI/CD Service Account - Auroria
First steps first, let's create the plain service account, without any permissions or roles assigned to it, this is fairly straight forward.
Read more >Use service users for continuous deployment | Okta
Create a service user for continuous deployment · From the Advanced Server Access dashboard, click Users. · Select the Service Users tab. ·...
Read more >How to attach a Service Account with CI/CD Pipeline (Apigee ...
I am having difficulty in figuring out how to include a service account with a proxy deployment to ApigeeX with the Deploy Maven...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
+1 Looking to setup a CI pipeline that is able to do
clasp push
without sharing a (g suite) user’s.clasprc.json
with the CI pipeline, I find this pretty standard eg: AWS, and after 2 years this issue is still open…@marcosscriven It looks like this issue is being triaged by the Apps Script team. I’ve asked the team for an update on the issue. Unfortunately, it’s a lot easier to change features in
clasp
than modify anything with the Apps Script tool/product.