Skip to content

[ENG-36942] fix: update edge storage cache invalidation and bucket fallback#3487

Merged
robsongajunior merged 1 commit intodevfrom
ENG-36942-fix-object-storage-settings
Apr 20, 2026
Merged

[ENG-36942] fix: update edge storage cache invalidation and bucket fallback#3487
robsongajunior merged 1 commit intodevfrom
ENG-36942-fix-object-storage-settings

Conversation

@gdsantana
Copy link
Copy Markdown
Contributor

Bug fix

What was the problem?

After edge storage mutations, cached bucket and credential queries were removed instead of being invalidated, causing stale UI states and making bucket detail loading fragile when list data was still available only in cache.

Expected behavior

Edge storage lists and details should stay consistent after create/update/delete actions, with cache updates and proper refetch behavior without breaking UI rendering.

How was it solved

Replaced query removals with query invalidation for buckets and credentials, added optimistic cache update for bucket workloads access, introduced cache fallback in bucket detail loading (getBucketFromCache), and added null-safe handling in file list computed properties to avoid runtime failures.

How to test

  1. Open Edge Storage list and update a bucket workload access value.
  2. Confirm the updated value is reflected and list/detail remains consistent.
  3. Create and delete buckets/credentials and confirm data refreshes correctly.
  4. Open a bucket detail page after list navigation and confirm it loads correctly using cached data when applicable.
  5. Check file search/list rendering with empty or not-yet-loaded file data.

@robsongajunior robsongajunior merged commit 0da3bb8 into dev Apr 20, 2026
7 of 9 checks passed
@robsongajunior robsongajunior deleted the ENG-36942-fix-object-storage-settings branch April 20, 2026 14:01
@github-actions github-actions Bot locked and limited conversation to collaborators Apr 20, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

bug Something isn't working

Development

Successfully merging this pull request may close these issues.

2 participants