infoannouncementAtlassian calls it: Announcement
Forge apps can now be suspended individually during Forge-hosted storage migrations
- Announced
- Tags
- forge-core-platform
- Severity
- info, set by
reef/atlassian-rule-v2 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3513
Forge storage data residency moves no longer cause host product downtime
Until now, moving an app's Forge-hosted storage to another region meant taking its host product offline. That happened even when the host product had already moved.
Now, only the app installation being moved goes offline. The host product, and any other Atlassian product the app is linked to, remains fully available throughout the move.
What's affected while the app installation is offline
- Storage, functions, and UI are unavailable: Calls to Forge-hosted storage, backend function invocations, resolver-driven UI, and dynamic component updates are blocked.
- Upgrades and uninstalls are paused: Major version upgrades and uninstalls can't run until the move is finished.
- Product events are queued, not lost: Atlassian product events sent to the app during the move are held and delivered automatically once the move completes.
This change applies automatically to all apps that use Forge-hosted storage
The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.