agent_coder
6aecdfbe46
Make the container image-status badge actionable, matching native Portainer: - Clicking "Update available" opens the update confirm dialog and runs the existing update flow (standalone recreate-with-pull / stack redeploy), gated and disabled while in flight to avoid a double submit. The confirm+apply logic is extracted from UpdateNowButton into a shared useApplyContainerImageUpdate hook so the details button and the list badge share one implementation. - Clicking "Up to date" re-queries the registry. Because the server caches image status (statusCache 5m + remoteDigestCache 5s), a plain refetch was a no-op, so the endpoint gains an optional ?force=true that bypasses BOTH caches for a manual re-check while still repopulating them; the default (auto badges + the auto-update daemon) keeps using the caches unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
18 lines
613 B
TypeScript
18 lines
613 B
TypeScript
export { resolveContainerUpdatePath } from './resolveContainerUpdatePath';
|
|
export { groupContainersForUpdate } from './groupContainersForUpdate';
|
|
export {
|
|
applyContainerUpdate,
|
|
EXTERNAL_STACK_UPDATE_ERROR,
|
|
} from './applyContainerUpdate';
|
|
export {
|
|
useUpdateContainerImage,
|
|
invalidateContainerUpdateQueries,
|
|
} from './useUpdateContainerImage';
|
|
export { useApplyContainerImageUpdate } from './useApplyContainerImageUpdate';
|
|
export { useBulkUpdateContainerImages } from './useBulkUpdateContainerImages';
|
|
export type {
|
|
ContainerUpdateContext,
|
|
ContainerUpdateKind,
|
|
ContainerUpdatePath,
|
|
} from './types';
|