SERVERLESS_LICENSE_KEY, SERVERLESS_ACCESS_KEY -- github actions based CI/CD

Serverless Framework
,
1

We are small team od devs and migrating now to v4. We have already serverless subscription acquired from AWS marketplace. Our CI/CD is based on gh actions workflows. For start we plan to use serverless from CLI mainly, but also trying some basic stuff from dashboard.

Which auth flow should we use for out gh actions CI/CD - access keys or license keys? Namely:

  1. SERVERLESS_LICENSE_KEY - is it compatible with gh actions based CI/CD?
  2. SERVERLESS_LICENSE_KEY - does it have expiration time and if yes - whats the value?
  3. SERVERLESS_ACCESS_KEY - does it have expiration time and if yes - whats the value?
  4. which one can be recommended for our project?

many thanks for answers!

2

Neither of these access keys timeout. So no worry about any of that.

If you plan on using Serverless Dashboard features as a part of your Serverless Framework Services, you will need to use a SERVERLESS_ACCESS_KEY.