Skip to content

chore(release): bump version to 6.2.9 - #479

Merged
dwolfson merged 1 commit into
odpi:mainfrom
dwolfson:chore/release-6.2.9
Oct 22, 2026
Merged

dwolfson merged 1 commit into
odpi:mainfrom
dwolfson:chore/release-6.2.9

Conversation

@dwolfson

Copy link
Copy Markdown
Member

Bumps pyegeria to 6.2.9 (pyproject.toml, uv.lock).

6.2.9 ships:

  • Resolve Dr.Egeria credentials at run time with one precedence chain (ISSUE-161) #477 (ISSUE-161): Dr.Egeria's entry points (dr_egeria, dr_egeria_folder, md_processing) now all look up the Egeria user the same way, when the command runs: --userid, then EGERIA_USER, then config.json / .env, then the default. They use the new pyegeria.core.config.resolve_egeria_credentials(). Before, md_processing ignored config.json / .env, and the CLIs fixed their defaults at import time.
  • Dr.Egeria Postgres element commands take a secrets store (ISSUE-160 follow-up) #478 (ISSUE-160 follow-up): Dr.Egeria's "Postgres Server Element" and "Postgres Database Element" commands take Secrets Store Path Name and Secrets Collection Name, plus Version Identifier, and Resource Name on the server. Behaviour change: the Database User Id and Database Password attributes are removed; Egeria's templates take credentials from a secrets store instead.

🤖 Generated with Claude Code

Ships odpi#477 (ISSUE-161: Dr.Egeria entry points resolve the Egeria user
at run time with one precedence chain, via resolve_egeria_credentials)
and odpi#478 (Dr.Egeria Postgres Server/Database Element commands take
secrets-store attributes; Database User Id / Database Password removed).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
@dwolfson
dwolfson merged commit adfb8d0 into odpi:main Oct 22, 2026
5 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.

1 participant