CLI production reads

Console

The Layout CLI 0.2 covers the rest of the build: any endpoint from your terminal, and production when you need to see what happened there. It still never changes production or moves money.

What changed

  • layout login --live asks to read production for 12 hours. The console marks the request as production and asks for a sign-in from the last 15 minutes before you can approve it.
  • --live works on listen, deliveries, keys list and webhooks list. Live keys, the live signing secret and every production setting stay in the console.
  • layout api get /v1/places?query=coffee calls any REST endpoint and prints the answer. It uses your sandbox key, a token you pass with --token, or LAYOUT_SECRET_KEY. In production it only reads, and only with your own live secret.
  • LAYOUT_SECRET_KEY=sk_test_... runs api and test-order without layout login, so they work in CI.
  • A new layout login revokes the session it replaces. A failed one leaves you signed in.
  • The CLI tells you once a day when a newer version is out.

Why it matters

You can debug a production webhook from your own machine the same way you built it in sandbox, and an agent can try any endpoint without writing a client first.

What to do

Update with npm i -g @layoutplatforms/cli. See Production and Call the API.

Breaking changes

None.

All changes