feat(github): migrate storybook deployment from Azure to Radix - #4869
Draft
Hjaf wants to merge 2 commits into
Draft
feat(github): migrate storybook deployment from Azure to Radix#4869Hjaf wants to merge 2 commits into
Hjaf wants to merge 2 commits into
Conversation
Replace Azure Blob Storage + Front Door deployment with Radix platform deployment, matching the pattern used by docs and color-palette-generator. - Add DockerfileStorybook (multi-stage: node build → nginx runtime) - Add storybook-nginx.conf for SPA serving on port 3000 - Add storybook component to radixconfig.yaml with DNS aliases - Remove publish_storybook.yaml workflow (Radix auto-deploys on push) - Remove storybook deploy/CDN purge jobs from publish_core_react.yaml - Remove storybook endpoint from _purge_cdn.yaml - Delete obsolete packages/eds-core-react/Dockerfile.storybook - Update documentation with new deployment model
emirgens
reviewed
Apr 29, 2026
| environment: prod | ||
| component: docs | ||
| useCertificateAutomation: true | ||
| - alias: storybook.eds.equinor.com |
Collaborator
There was a problem hiding this comment.
Suggested change
| - alias: storybook.eds.equinor.com | |
| remove |
Remove DNS for now.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace Azure Blob Storage + Front Door deployment with Radix platform deployment, matching the pattern used by docs and color-palette-generator.
Note
Radix only reads
radixconfig.yamlfrom the Config Branch (main), even fordevenvironment builds (Radix docs). New components on feature branches are ignored.To enable the storybook build, we need to push
radixconfig.yamltomainfirst. Components are only added to the config, no existing components are affected.This migration changes how dev storybook deployments work. Previously, storybook was deployed via a manually dispatched workflow, giving us control over when updates went live. With Radix, storybook rebuilds automatically on every push to
feat/*(dev) andmain(prod) branches. We need to merge the config and observe the impact before fully committing. If automatic rebuilds on every push prove too disruptive, we may need to explore alternative deployment patterns for dev (e.g. restricting the build trigger to specific branches or using manual promotion).