chore(#4165): rename llamastack to ogx across boost workspace - #4167
Conversation
The upstream llamastack project has been renamed to ogx. This commit renames all references across the boost workspace to reflect the new project name, including: - Plugin directories: boost-backend-module-llamastack → ogx, llamastack-entity-provider → ogx-entity-provider - npm package names under @Red-Hat-Developer-Hub scope - TypeScript identifiers: module exports, class names, interfaces, config paths, cache key prefixes, provider IDs, and entity names - Backend registration imports in packages/backend - app-config.yaml provider config key (boost.providers.ogx) - Dynamic plugin reference YAML files - AGENTS.md and README.md package tables - Test expectations for renamed provider IDs, cache keys, and entity name prefixes CHANGELOG.md files and openspec/specification docs are preserved as historical records and not renamed. Closes #4165
|
Important This PR includes changes that affect public-facing API. Please ensure you are adding/updating documentation for new features or behavior. Changed Packages
|
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #4167 +/- ##
=======================================
Coverage 54.96% 54.96%
=======================================
Files 2413 2413
Lines 96074 96074
Branches 26898 26898
=======================================
Hits 52809 52809
Misses 41770 41770
Partials 1495 1495
*This pull request uses carry forward flags. Click here to find out more. Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
|
/fs-fix add changesets via the process articulated in https://github.com/backstage/backstage/blob/master/CONTRIBUTING.md#creating-changesets for all affected packages and plugins; add a yarn directive into package.json if needed that replicates what is done in other workspaces |
|
🤖 Finished Fix · ✅ Success · Started 4:09 PM UTC · Completed 4:16 PM UTC |
Add changeset documenting the package rename from llamastack to ogx for all affected boost workspace packages: boost-backend-module-ogx (minor), ogx-entity-provider (minor), boost-backend (patch), and boost-common (patch). Addresses review feedback on #4167
🔧 Fix agent — iteration 1 (human-triggered)Added changeset for the llamastack-to-ogx rename covering all 4 affected public packages (2 minor for renamed packages, 2 patch for internal reference updates). No yarn directive needed — boost already has @changesets/cli configured identically to other workspaces. Fixed (1):
Disagreed (1):
Tests: passed Updated by fullsend fix agent |
|
/fs-review |
|
🤖 Finished Review · ✅ Success · Started 4:24 PM UTC · Completed 4:42 PM UTC |
ReviewFindingsHigh
Medium
Low
Labels: All changes are within the boost workspace (workspaces/boost/) Next steps:
|
![fullsend-ai-review[bot]](https://avatars.githubusercontent.com/in/3478501?s=60&v=4){kind=small}
There was a problem hiding this comment.
See the review comment for full details.
Note: The following inline comments could not be posted on the diff (GitHub returned 422) and are included here instead:
workspaces/boost/.changeset/rename-llamastack-to-ogx.md:1: [medium] npm-package-rename
Two previously published npm packages are renamed without deprecation of the old package names. Downstream consumers depending on the old names will see resolution failures. The changeset documents the rename, and v0.x packages allow breaking changes under semver conventions, but npm deprecate on the old names after publishing would ease the transition.
Suggested fix: After publishing, run npm deprecate on the old package names pointing to the new names.
workspaces/boost/dynamic-plugins-filesystem-reference.yaml:39: [low] grammar-error
Comment reads 'connects to a OGX Responses API endpoint' - should use 'an OGX' since OGX starts with a vowel sound.
Suggested fix: Change 'a OGX' to 'an OGX'.
workspaces/boost/dynamic-plugins-image-reference.yaml:38: [low] grammar-error
Same grammar issue: 'connects to a OGX' should be 'an OGX'.
Suggested fix: Change 'a OGX' to 'an OGX'.
workspaces/boost/plugins/boost-backend-module-ogx/src/provider/ResponsesApiProviderFactory.ts(file-level): Line 107 · [low] config-path-breaking-change
Config paths boost.providers.llamastack and boost.entityProviders.llamastack renamed to boost.providers.ogx and boost.entityProviders.ogx. Existing deployments will need config updates. Expected for v0.x rename.
workspaces/boost/plugins/ogx-entity-provider/src/providers/OgxModelEntityProvider.ts:40: [low] catalog-entity-identity-change
Entity name prefixes change from llamastack-model-/llamastack-agent- to ogx-model-/ogx-agent-. Old entities become catalog orphans. Expected for v0.x rename.
workspaces/boost/plugins/boost-backend-module-ogx/src/provider/SessionMap.ts:57: [low] cache-key-migration
Cache key prefixes change from llamastack: to ogx:. Existing cached data becomes inaccessible. Impact is transient - all caches have TTLs <= 24h.
workspaces/boost/dynamic-plugins-filesystem-reference.yaml:39: [low] dynamic-plugin-path-change
Dynamic plugin reference paths changed from llamastack to ogx. Deployed RHDH instances referencing the old path will fail to load the plugin.
fullsend-ai-review
Bot
added
the
workspace/boost
|
/fs-fix Rename BOOST_LLAMA_STACK_URL to BOOST_OGX_URL and _discover_llama_stack_route to _discover_ogx_route throughout scripts/load-secrets.sh |
|
🤖 Finished Fix · ✅ Success · Started 5:15 PM UTC · Completed 5:21 PM UTC |
|
From review #4167 (comment) only addressing wrt to the not wasting tokens on any of the low's ... in particular I want staged-issues.md to only reflect the state of things when those github issues were processed ; don't need to updates as the workspace progresses |
Rename BOOST_LLAMA_STACK_URL to BOOST_OGX_URL and _discover_llama_stack_route to _discover_ogx_route throughout scripts/load-secrets.sh to match the llamastack-to-ogx rename. Addresses review feedback on #4167
🔧 Fix agent — iteration 2 (human-triggered)Renamed BOOST_LLAMA_STACK_URL to BOOST_OGX_URL and _discover_llama_stack_route to _discover_ogx_route throughout scripts/load-secrets.sh per human instruction, completing the llamastack-to-ogx rename in this file. Fixed (2):
Tests: passed Updated by fullsend fix agent |
|
|
I checked out this PR's branch and the llamastack entity provider works as expected 
evidence of the rename in the backend logs: |
|
🤖 Finished Retro · ✅ Success · Started 6:24 PM UTC · Completed 6:44 PM UTC |
Retro: PR #4167 — rename llamastack → ogx across boost workspaceTimeline
What went well
What could go better
Existing issues this retro found evidence for
Proposals filed
|
Add the scripts/ directory and load-secrets.sh to the workspace directory tree and add a new "Scripts directory" section that documents the env-var synchronization requirement between load-secrets.sh and app-config.yaml. This ensures code agents discover load-secrets.sh during rename or refactor tasks that touch config keys under boost.providers.*. Root cause: PR #4167 renamed llamastack to ogx across 46 files but missed load-secrets.sh because AGENTS.md did not mention the scripts/ directory. The review agent caught the desync before merge, but a /fs-fix round-trip was needed to complete the rename. Closes #4168 Co-authored-by: fullsend-code <278716306+fullsend-ai-coder[bot]@users.noreply.github.com>
1 participant
The upstream llamastack project has been renamed to ogx. This commit renames all references across the boost workspace to reflect the new project name, including:
llamastack-entity-provider → ogx-entity-provider
config paths, cache key prefixes, provider IDs, and entity names
entity name prefixes
CHANGELOG.md files and openspec/specification docs are preserved as historical records and not renamed.
Closes #4165
Post-script verification
agent/4165-rename-llamastack-to-ogx)234bc786f89bca0dc16dd20f9568eeb0931f38e2..HEAD)