Add SLAS tenant APIs

[hnestmann]

No description provided.

[tobiaslohr]

Thanks @hnestmann ! This is awesome. I've left some comments. In general (for all commands) we should consider offering an option for the user of the CLI to persist the short code via other means, e.g. local CLI config, env vars, .env or dw.json (or similar).

Module secrets contains the general lookup logic already and we could use it to pull the shortcode to avoid having it being passed for every command.

[tobiaslohr]

Do we want to allow someone passing the full JSON with the tenant info in there as a short hand version in alternative to passing individual properties through parameters? E.g.

{
  "channels": [
    "SiteGenesis",
    "OtherSite"
  ],
  "clientId": "client-id1",
  "ecomSite": "SiteGenesis",
  "ecomTenant": "test_prd",
  "name": "ShopperClient1",
  "privateClient": true,
  "redirectUri": "http://localhost:9010/callback",
  "scopes": [
    "sfcc.products",
    "sfcc.catalogs",
    "sfcc.products.ro"
  ],
  "secret": "secret12345"
}

[hnestmann]

I agree, here I have the flat list, but on client:add I reference a file. I think we should allow both approaches on both APIS.

[tobiaslohr]

Minor description change needed

[tobiaslohr]

Minor description change needed

[hnestmann]

Add code comments

[hnestmann]

/home/circleci/project/cli.js
1961:1 error Line 1961 exceeds the maximum line length of 120 max-len

/home/circleci/project/lib/slas.js
8:1 error Line 8 exceeds the maximum line length of 120 max-len
42:1 error Line 42 exceeds the maximum line length of 120 max-len

[hnestmann]

Thanks @hnestmann ! This is awesome. I've left some comments. In general (for all commands) we should consider offering an option for the user of the CLI to persist the short code via other means, e.g. local CLI config, env vars, .env or dw.json (or similar).

Module secrets contains the general lookup logic already and we could use it to pull the shortcode to avoid having it being passed for every command.

This has been added