Skip to content

Refresh OrchestrationImage info.json create#1119

Merged
donaldgray merged 1 commit intodevelopfrom
bugfix/refresh_for_infojson
Mar 2, 2026
Merged

Refresh OrchestrationImage info.json create#1119
donaldgray merged 1 commit intodevelopfrom
bugfix/refresh_for_infojson

Conversation

@donaldgray
Copy link
Copy Markdown
Member

Avoids issues where stale OrchestrationImage can be used to create info.json. We cache info.json for a long time, so created with stale data that can hang around. If info.json is missing it means the image new, or it has recently been updated and cleanup-handler has removed.

This looks like more changes than it actually is, summary:

  • Add new IOrchestratorAssetRepository : IAssetRepository, which adds a noCache overload of GetAsset()
  • DapperAssetRepository inherits from above, so had to move into Orchestrator (this should have been done a while ago).
  • Extend MemoryAssetTracker.RefreshCachedAsset to call new overload with true (ie get a fresh asset)
  • InfoJson* classes now take AssetId rather than OrchestrationAsset when building info.json.

Avoids issues where stale OrchestrationImage can be used to create
info.json. We cache info.json for a long time, so created with stale
data that can hang around. If info.json is missing it means the image
new, or it has recently been updated and cleanup-handler has removed.
@donaldgray donaldgray requested a review from a team as a code owner February 27, 2026 16:52
Copy link
Copy Markdown
Contributor

@griffri griffri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - would be good to have the others' eyes on it too

@donaldgray donaldgray merged commit 8252067 into develop Mar 2, 2026
8 checks passed
@donaldgray donaldgray deleted the bugfix/refresh_for_infojson branch March 2, 2026 10:27
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