Skip to content

Conversation

@dennisvang
Copy link
Contributor

@dennisvang dennisvang commented Oct 17, 2025

  • Moved db fixtures dir from src/main/resources into project root
  • Modified Dockerfile to copy the fixtures into the image
  • Added configuration option for the (relational) db fixtures path
  • Use bootstrap.enabled property to disable the populator by default, so ops person can decide when to load fixtures

This allows us to mount fixture files into the container at /fdp/fixtures/<filename> to override the defaults or extend them. For example, we can override the default users by mounting only that file:

services:
  fdp:
    ...
    volumes:
      - ./my_custom_user-accounts.json:/fdp/fixtures/0100_user-accounts.json:ro

@dennisvang dennisvang force-pushed the proposal/db-fixtures-path branch from 40fcbd6 to 9706c09 Compare October 17, 2025 14:48
@dennisvang dennisvang marked this pull request as ready for review October 17, 2025 16:00
and use @value injection instead of BootstrapProperties
this makes it slightly more difficult to see where the properties are defined in code, but easier to see the name of the actual property in the external config file
we want to rely on the default false, and only override by setting environment property BOOTSTRAP_ENABLED on the command line
@dennisvang dennisvang merged commit dda23fb into feature/634-boostrapping-fdp Oct 27, 2025
13 checks passed
@dennisvang dennisvang deleted the proposal/db-fixtures-path branch October 27, 2025 09:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants