V4 how to login in a non-interactive way?

[skhaz]

V4 how to login in a non-interactive way?

[LorenzoRogai]

@skhaz https://www.serverless.com/framework/docs/guides/upgrading-v4

[Jimbolino]

Your shouldn't need to login before deploying when using an access key.

Thnx, this was the problem :)

First i read this:

You must sign in or use a license key with Serverless Framework V.4 and later versions. Please use "serverless login".

So i added the serverless login (because i dont have a license key)

Then i read:

You can authenticate via Access Key by signing in to Serverless Framework Dashboard when prompted by the CLI or running serverless login. [...] create a new Access Key for CI/CD use, and save it as the SERVERLESS_ACCESS_KEY environment variable in your CI/CD pipeline.

So i added the SERVERLESS_ACCESS_KEY, but didn't realize the serverless login is for interactive login ONLY, and either an access key OR license key can be used with the serverless deploy command

---

Now i'm stuck at the following:

Error: Resolver provider bref is not supported

For now i think its best for me to lock to v3: brefphp/bref#1815

[austencollins]

@Jimbolino It looks like the original issue was fixed, and now the second issue you reported here regarding the provider is also fixed as of this release

[austencollins]

This is documented in the upgrading guide.

[Jimbolino]

how to debug if it does not work?

deploy.sh:

env | grep SERVERLESS_ACCESS_KEY
npx serverless login
npx serverless deploy

log output:

SERVERLESS_ACCESS_KEY=***
✖ Unable to login in non-interactive mode. Please use a license key or access key, both of which you can get from the Serverless Framework Dashboard: https://app.serverless.com
Error: Unable to login in non-interactive mode. Please use a license key or access key, both of which you can get from the Serverless Framework Dashboard: https://app.serverless.com
    at authenticate (file:///home/runner/.serverless/releases/4.0.26/package/dist/sf-core.js:709:229[67](https://github.com/Jimbolino/www.troep.com/actions/runs/9227078770/job/25388255823#step:15:68))
    at commandLogin (file:///home/runner/.serverless/releases/4.0.26/package/dist/sf-core.js:947:8446)
    at file:///home/runner/.serverless/releases/4.0.26/package/dist/sf-core.js:1006:5782
    at CommandInstance.applyBuilderUpdateUsageAndParse (file:///home/runner/.serverless/releases/4.0.26/package/dist/sf-core.js:881:38830)
    at CommandInstance.runCommand (file:///home/runner/.serverless/releases/4.0.26/package/dist/sf-core.js:881:38064)
    at [runYargsParserAndExecuteCommands] (file:///home/runner/.serverless/releases/4.0.26/package/dist/sf-core.js:939:16037)
    at YargsInstance.parse (file:///home/runner/.serverless/releases/4.0.26/package/dist/sf-core.js:937:2537)
    at run3 (file:///home/runner/.serverless/releases/4.0.26/package/dist/sf-core.js:1006:7625)
    at file:///home/runner/.serverless/releases/4.0.26/package/dist/sf-core.js:1006:7892
    at ModuleJob.run (node:internal/modules/esm/module_job:222:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)
    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:123:5)
For help, try the following:
  • Run the command again with the "--debug" option
  • Run "serverless support"
  • Review the docs: https://www.serverless.com/framework/docs/

[austencollins]

@Jimbolino Can you try running again using the --debug flag?

[austencollins]

Your shouldn't need to login before deploying when using an access key.