feat: auto-create Hydra client on startup #628
Merged
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.
Impact: minor
Type: feature
Changes
For local development, there is a script that runs before the application, which creates a Hydra client for the storefront if one does not yet exist. However, this script isn't included in the production image and doesn't run in a production environment, leading to an additional task that a system admin has to do for every new environment.
This PR moves the auto-creation of the Hydra client to be part of the server startup code, such that it runs in all environments always.
Breaking changes
None
Testing
reaction-hydra
,docker-compose down -v
and thendocker-compose up -d
. This will ensure the Hydra database is empty and has no clients.Perform above steps both with and without the
docker-compose.dev
override.