You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the .dsmrc file is a standard JSON file, I'm unsure how to add the authentication token as an environment variable. I don't want to expose the token in the repository and would rather have the CD pipeline to push the changes to DSM.
I'm aware that I could try workarounds, for example, I could maybe replace <authentication token> for the auth token via a shell script on the CI before running the dsm-storybook publish, but that seems a bit hacky to me and I was hoping for proper support.
Also, would it be possible to set the -c flag to the dsm-storybook publish script in order to set the custom .storybook directory? That's the current behavior of storybook's CLI.
The text was updated successfully, but these errors were encountered:
As the
.dsmrc
file is a standard JSON file, I'm unsure how to add the authentication token as an environment variable. I don't want to expose the token in the repository and would rather have the CD pipeline to push the changes to DSM.I'm aware that I could try workarounds, for example, I could maybe replace
<authentication token>
for the auth token via a shell script on the CI before running thedsm-storybook publish
, but that seems a bit hacky to me and I was hoping for proper support.Also, would it be possible to set the
-c
flag to thedsm-storybook publish
script in order to set the custom.storybook
directory? That's the current behavior of storybook's CLI.The text was updated successfully, but these errors were encountered: