Skip to content

fix(quick-start-local): rebuild my-profile's pyegeria layer with the others - #610

Merged
mandy-chessell merged 2 commits into
odpi:mainfrom
dwolfson:fix/quick-start-local-rebuild-my-profile-pyegeria
Oct 6, 2026
Merged

mandy-chessell merged 2 commits into
odpi:mainfrom
dwolfson:fix/quick-start-local-rebuild-my-profile-pyegeria

Conversation

@dwolfson

@dwolfson dwolfson commented Oct 5, 2026

Copy link
Copy Markdown
Member

The pyegeria rebuild step in quick-start-local built only pyegeria-web and jupyter-hub, so my-profile stayed on the pyegeria it was first built with (6.1.27, while the others track the latest release). Dockerfile-my-egeria already takes the same PYEGERIA_VERSION / PYEGERIA_BUST args, so my-profile is now built in the same step, honouring --pyegeria-version, --refresh-pyegeria and --no-refresh-pyegeria.

Quickstart only: fresh-start-local has no my-profile service.

Tested: bash -n only. The build itself has not been run end to end; the next quick-start-local run will exercise it.

🤖 Generated with Claude Code

…others

The pyegeria rebuild step named only pyegeria-web and jupyter-hub, so
my-profile stayed on whatever pyegeria it was first built with (6.1.27
while the others tracked 6.1.28/6.1.29). Dockerfile-my-egeria already takes
the same PYEGERIA_VERSION / PYEGERIA_BUST build args, so add it to the build.

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
@dwolfson dwolfson self-assigned this Oct 5, 2026
@mandy-chessell
mandy-chessell merged commit 99f8930 into odpi:main Oct 6, 2026
4 checks passed
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.

2 participants