Forge hosted storage scheduled platform migration (no outage)
Scheduled Maintenance
Report for Atlassian Developer
Completed
The scheduled maintenance has been completed.
Update
The migration has been completed. All apps are now on the new platform backing Forge hosted storage.
Update
Migration has been resumed. This migration will be progressively rolled out per app and Forge environment. As remaining apps are progressively onboarded you will see the format of the cursor change, in line with the format for apps already on the new platform. We will provide updates as necessary.
In progress
Edit: This message was unintentionally posted. The migration has not started yet and a message will be posted here when it resumes.
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Scheduled
The migration to the new backing platform for Forge hosted storage is resuming. The majority of apps have already been migrated to the new platform.
Timeline
Starting on 2024-02-29 00:00 UTC, the remaining apps will be migrated to the new data store in a progressive way, by app and environment.
The progressive migration is expected expected to finish no later than 2024-03-22 00:00 UTC.
Cursor format change during the migration
Once an app is migrated to the new platform you will notice the query cursors format has changed. The query cursor is an opaque string generated by the underlying data store, which is used to fetch next pages in a paginated query when using the query API [https://developer.atlassian.com/platform/forge/runtime-reference/storage-api-query/]. When the migration is complete, the new data store will reject cursors created by the old data store. For a smooth transition and minimising the impact to the apps, the platform will accept both cursor formats for a short period of time (approximately 15 minutes after the cutover). You don’t need to take any action as this is managed by the Forge team. It is advised that these cursors are not persisted and only used within the context of a single paginated query.
Additional note for Forge developers
As part of our review for the two incidents mentioned in https://developer.status.atlassian.com/incidents/9q71ytpjhbtl and https://developer.status.atlassian.com/incidents/yzt262mxycm9, we have done an internal review of our migration process, rollout and risk management. We have taken measures to address the identified gaps in order to avoid impact to apps and developers during this transition, ensuring that hosted storage remains reliable and stable. We will be publishing the post incident review shortly with more information about what happened and the actions we took to prevent the issues from reoccurring. The post incident review will be posted on the two Statuspage incidents mentioned above (https://developer.status.atlassian.com/incidents/9q71ytpjhbtl and https://developer.status.atlassian.com/incidents/yzt262mxycm9).
Reporting issues
If you notice any unexpected issues during this platform migration, please report them via the Developer and Marketplace Support service desk [https://ecosystem.atlassian.net/servicedesk/customer/portal/34/group/96/create/571].
Timeline
Starting on 2024-02-29 00:00 UTC, the remaining apps will be migrated to the new data store in a progressive way, by app and environment.
The progressive migration is expected expected to finish no later than 2024-03-22 00:00 UTC.
Cursor format change during the migration
Once an app is migrated to the new platform you will notice the query cursors format has changed. The query cursor is an opaque string generated by the underlying data store, which is used to fetch next pages in a paginated query when using the query API [https://developer.atlassian.com/platform/forge/runtime-reference/storage-api-query/]. When the migration is complete, the new data store will reject cursors created by the old data store. For a smooth transition and minimising the impact to the apps, the platform will accept both cursor formats for a short period of time (approximately 15 minutes after the cutover). You don’t need to take any action as this is managed by the Forge team. It is advised that these cursors are not persisted and only used within the context of a single paginated query.
Additional note for Forge developers
As part of our review for the two incidents mentioned in https://developer.status.atlassian.com/incidents/9q71ytpjhbtl and https://developer.status.atlassian.com/incidents/yzt262mxycm9, we have done an internal review of our migration process, rollout and risk management. We have taken measures to address the identified gaps in order to avoid impact to apps and developers during this transition, ensuring that hosted storage remains reliable and stable. We will be publishing the post incident review shortly with more information about what happened and the actions we took to prevent the issues from reoccurring. The post incident review will be posted on the two Statuspage incidents mentioned above (https://developer.status.atlassian.com/incidents/9q71ytpjhbtl and https://developer.status.atlassian.com/incidents/yzt262mxycm9).
Reporting issues
If you notice any unexpected issues during this platform migration, please report them via the Developer and Marketplace Support service desk [https://ecosystem.atlassian.net/servicedesk/customer/portal/34/group/96/create/571].
This scheduled maintenance affected: Developer (Hosted storage).