Open danilowoz opened 3 years ago
tmikeschu
commented
3 years ago @danilowoz I don't know if you're still going for this, but I ended up copying the pattern in https://github.com/storyblok/storyblok/blob/master/src/tasks/pull-components.js and using a storyblok client initialized with an oauth token. So instead of using the CLI I just call my custom script with node scripts/pull-storyblok-components.js.
johnjenkins
commented
8 months ago @danilowoz I don't know if you're still going for this, but I ended up copying the pattern in https://github.com/storyblok/storyblok/blob/master/src/tasks/pull-components.js and using a storyblok client initialized with an oauth token. So instead of using the CLI I just call my custom script with node scripts/pull-storyblok-components.js.
Does anyone know where that script is now? (@lisilinhart sorry to ping you - but perhaps you know?)
tmikeschu
commented
8 months ago Looks like they have new repos: https://github.com/storyblok/storyblok-cli/blob/cce1fef04636c3538c1fd3135471ec6cf98a2832/src/tasks/pull-components.js
The feature would affect: (check one with "x")
Is your feature request related to a problem? Please describe. We're considering using Stoyblok CLI to sync the components in the build time, like a Github Action, where we could update the components in the production only when the UI-components has been ready to go live.
Describe the solution you'd like Someway to login in a CI environment without passing my email/password. One possible way is supporting an env var, for example
STORYBLOK_LOGIN_APIKEY, and once this variable is available the CLI is able to log in the execute its methods.